7c272c561c
* c * we * working * work on searchable props * organize * workinng * accept siteUrl as parameter * qw * a * work on display * work on propertyBagDisplay * ZX * qwe * qwd * qdw * qdw * refactoring * qw * qw * qwd * awd * er * git popup on disoplay working * 123 * qw * asd * works * Working! * qweqwwe * asd * linting * tslint * enable edit all properties * edit all props * sort not quite working * sort working * sort working * now really! * fdg * Added MessageDisplay * separete messagedisplay for panel * added PropertyBagEditPanel * Implement fileters site list * new props * Filters working * add addn'l parameters * extracted User Filetrs * added dropdowns to coimmand bar * qw * filters * ads * qwe * sdf * work on user filters * dwq * qw * add global nab menu * filterstate * qwe * qwe * fixed filters on filtered site list * convert params in webparr * work on men us * fix nav webpart. Cleanup Descriptions * clean linting errors * qwe * added comments * fix href in menu * readme * fix render of bolean in list * add images * Update README.md * Update README.md * Update README.md * fix copy-assets.json * cleaned up webpart names and descriptions * fix issue with menu and blank props * fix readme |
||
|---|---|---|
| .github | ||
| .vscode | ||
| samples | ||
| tutorials | ||
| LICENSE | ||
| README.md | ||
| debug.log | ||
README.md
SharePoint Framework client-side web part samples & tutorial materials
This repo contains the samples that demonstrate different usage patterns for the SharePoint Framework client-side web parts.
Note: The SharePoint Framework is currently in preview and is subject to change. SharePoint Framework client-side web parts are not currently supported for use in production enviornments.
SharePoint client-side web parts are controls that appear inside a SharePoint page but run locally in the browser. They're the bulding 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 Developer 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
Additional resources
- Overview of the SharePoint Framework
- SharePoint Framework development tools and libraries
- SharePoint Framework Reference
Using the samples
To build and start using these projects, you'll need to clone and build the projects.
Clone this repo by executing the following command in your console:
git clone https://github.com/SharePoint/sp-dev-fx-webparts.git
Navigate to the cloned repo folder which should be the same as the repo 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
Contributions
These samples are direct from the feature teams, SharePoint PnP core team (http://aka.ms/SharePointPnP) 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 there's any questions around that, 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. Thx.
Sharing is caring!