SharePoint Framework web part, Teams tab, personal app, app page samples
Go to file
Hugo Bernier 0e778a83b6
Update sample.json
2021-05-03 00:51:47 -04:00
.github Changed master to main 2021-05-02 15:04:59 -04:00
samples Update sample.json 2021-05-03 00:51:47 -04:00
tutorials Changed master to main 2021-05-02 15:04:59 -04:00
.gitignore sample added 2020-12-04 16:00:39 +01:00
CODE_OF_CONDUCT.md Update CODE_OF_CONDUCT.md 2021-04-24 14:14:25 -04:00
CONTRIBUTING.md Changed master to main 2021-05-02 15:04:59 -04:00
LICENSE Updated license accordingly. 2016-09-08 20:26:05 +03:00
README.md Update README.md 2021-04-26 01:01:41 -04:00
SECURITY.md Create SECURITY.md 2021-04-24 14:28:58 -04:00
SUPPORT.md Changed master to main 2021-05-02 15:04:59 -04:00
package-lock.json bug fix #1324 tree-orgchart 2020-06-12 19:15:01 +01:00

README.md

page_type products languages extensions
sample
office-sp
typescript
contentType technologies createdDate
samples
SharePoint Framework
8/30/2016 10:21:43 AM

SharePoint Framework Client-Side Web Part Samples & Tutorial Materials

This repository contains community samples that demonstrate different usage patterns for the SharePoint Framework client-side web parts.

We do welcome community contributions to the samples folder in this repository for demonstrating different use cases with SharePoint Framework. Notice that if you use 3rd party libraries, please make sure that library license allows distributions of it as part of your sample.

SharePoint client-side web parts are controls that appear inside a SharePoint page but run locally in the browser. They're the building blocks of pages that appear on a SharePoint site. You can build client-side web parts using modern script development tools and the SharePoint workbench (a development test surface), and you can deploy your client-side web parts to classic web part pages in Office 365 tenants. In addition to plain JavaScript projects, you can build web parts alongside common scripting frameworks, such as AngularJS and React. For example, you can use React along with components from Office UI Fabric React to quickly create experiences based on the same components used in Office 365.

Have issues or questions?

Please use following logic on submitting your questions or issues to right location to ensure that they are noticed and addressed as soon as possible.

Additional resources

Using the samples

To build and start using these projects, you'll need to clone and build the projects.

Clone this repository by executing the following command in your console:

git clone https://github.com/pnp/sp-dev-fx-webparts.git

Navigate to the cloned repository folder which should be the same as the repository name:

cd sp-dev-fx-webparts

To access the samples use the following command, where you replace sample-folder-name with the name of the sample you want to access.

cd samples
cd sample-folder-name

and for the tutorials, use the following command:

cd tutorials

Now run the following command to install the npm packages:

npm install

This will install the required npm packages and dependencies to build and run the client-side project.

Once the npm packages are installed, run the following command to preview your web parts in SharePoint Workbench:

gulp serve

Authors

This repository's contributors are all community members who volunteered their time to share code samples. Work is done as an open source community project, with each sample contained in their own solution.

Contributions

These samples are direct from the feature teams, SharePoint PnP core team (http://aka.ms/m365pnp) or shared by the community. We welcome your input on issues and suggestions for new samples. We do also welcome community contributions around the client-side web parts. If you have any questions, just let us know.

Please have a look on our Contribution Guidance before submitting your pull requests, so that we can get your contribution processed as fast as possible.

Code of Conduct

This repository has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Sharing is caring!