Skip to content

Commit c1d779e

Browse files
committed
Merge branch 'staging'
2 parents 080378c + 6393e2e commit c1d779e

File tree

42 files changed

+982
-21
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

42 files changed

+982
-21
lines changed

README.md

Lines changed: 25 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,41 +1,53 @@
11
# Welcome to the SharePoint Framework Developer Preview!
22

3-
The SharePoint Framework is a Page and Part model that enables client-side development for building SharePoint experiences. It facilitates easy integration with the SharePoint data, and provides support for open source tooling development.
3+
The SharePoint Framework (SPFx) is a page and part model that enables client-side development for building SharePoint experiences. It facilitates easy integration with the SharePoint data, and provides support for open source tooling development.
44

5-
The SharePoint Framework is still in initial Developer Preview, and it's still rough around the edges. As we work to improve the SharePoint Framework, we'd love your feedback! If you have feedback, please use [UserVoice](https://sharepoint.uservoice.com/forums/329220-sharepoint-dev-platform). If you have technical questions about the framework, we’ll be monitoring [#spfx](http://sharepoint.stackexchange.com/tags/spfx/), [#spfx-webparts](http://sharepoint.stackexchange.com/tags/spfx-webparts/), and [#spfx-tooling](http://sharepoint.stackexchange.com/tags/spfx-tooling/) on [SharePoint StackExchange](http://sharepoint.stackexchange.com/).
5+
The SharePoint Framework is still in initial Developer Preview, and it's still rough around the edges. As we work to improve the SharePoint Framework, we'd love your feedback! If you find issues or have new ideas and suggestions for SharePoint Framework, make sure you submit them [here](https://github.com/SharePoint/sp-dev-docs/issues). We’ll also be monitoring [#spfx](http://sharepoint.stackexchange.com/tags/spfx/), [#spfx-webparts](http://sharepoint.stackexchange.com/tags/spfx-webparts/), and [#spfx-tooling](http://sharepoint.stackexchange.com/tags/spfx-tooling/) at [SharePoint StackExchange](http://sharepoint.stackexchange.com/) as well.
66

7+
## Developer Preview Releases
8+
9+
* **Sep 14, 2016**
10+
* **Drop 3 is available**. [See the release notes here](https://github.com/SharePoint/sp-dev-docs/wiki/Release-Notes-Drop-3)
11+
12+
* **Sep 1, 2016**
13+
* **Drop 2 is available**. [See the release notes here](https://github.com/SharePoint/sp-dev-docs/wiki/Release-Notes-Drop-2)
14+
15+
* **Aug 17, 2016**
16+
* **Drop 1 is available**. [See the release notes here](https://github.com/SharePoint/sp-dev-docs/wiki/Drop-1)
17+
718
## Get Started
819

9-
* [Setup your Office 365 Developer Tenant](../../wiki/Setup-SharePoint-Tenant)
10-
* [Setup your Machine](../../wiki/Setup-your-machine)
11-
* [Go build Tutorial 1: HelloWorld WebPart](../../wiki/HelloWorld-WebPart)
12-
* [More Tutorials and Walkthroughs](../../wiki/Tutorials and Walkthroughs)
20+
* [Setup your Office 365 Developer Tenant](http://dev.office.com/sharepoint/docs/spfx/set-up-your-developer-tenant)
21+
* [Setup your Machine](http://dev.office.com/sharepoint/docs/spfx/set-up-your-development-environment)
22+
* [Go build your first web part](http://dev.office.com/sharepoint/docs/spfx/web-parts/get-started/build-a-hello-world-web-part)
1323

1424
## Learn More
1525

16-
* [Background and Philosophy](../../wiki/Why-SPFx)
17-
* [Design Great Web Parts](../../wiki/Design-Great-Webparts)
26+
* [Background and Philosophy](http://dev.office.com/sharepoint/docs/spfx/sharepoint-framework-overview)
27+
* [Design Great Web Parts](http://dev.office.com/sharepoint/docs/spfx/web-parts/basics/design-considerations-for-web-parts)
1828
* [API Docs](https://sharepoint.github.io/)
1929

2030
## Updates & Feedback
2131

2232
To keep track of improvements to the Office 365 Framework, please take a look at:
23-
* [@OfficeDev](https://twitter.com/officedev) on Twitter
33+
34+
* [@SharePoint](https://twitter.com/sharepoint) and [@OfficeDev](https://twitter.com/officedev) on Twitter
2435
* [Office Developer Blog](http://dev.office.com/blogs)
2536

2637
Provide Feedback:
2738

39+
* If you find issues or have new ideas and suggestions for SharePoint Framework, make sure you submit them [here](https://github.com/SharePoint/sp-dev-docs/issues).
40+
* [SharePoint StackExchange](http://sharepoint.stackexchange.com/) (please use [#spfx](http://sharepoint.stackexchange.com/tags/spfx/), [#spfx-webparts](http://sharepoint.stackexchange.com/tags/spfx-webparts/), and [#spfx-tooling](http://sharepoint.stackexchange.com/tags/spfx-tooling/) tags)
2841
* [SharePoint Developer UserVoice](https://sharepoint.uservoice.com/forums/329220-sharepoint-dev-platform)
29-
* [SharePoint StackExchange](http://sharepoint.stackexchange.com/) (please use #spfx, #spfx-webparts, and #spfx-tooling tags)
3042

3143
## Deployment Status
3244

33-
Note: SharePoint Framework web parts during preview are not supported for production use.
45+
Note: SharePoint Framework web parts are not supported for production use.
3446

3547
The SharePoint Framework is currently available for use in Classic Pages within Office 365 Developer Tenancies. We’ll be expanding coverage to more Office 365 Tenancies over the coming months.
3648

37-
(Of course, you can also get started with our SharePoint Workbench to create and test your web parts locally, on your machine.)
49+
Of course, you can also get started with our SharePoint Workbench to create and test your web parts locally, on your machine.
3850

3951
## Have Fun
4052

41-
We look forward to seeing what you build! Please tweet us at @OfficeDev.
53+
We look forward to seeing what you build! Please tweet us at @OfficeDev or @SharePoint with the #SPFx tag!

docs/apis/webhooks/lists/overview-sharepoint-list-webhooks.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,13 +22,13 @@ Notifications will be sent to your application for the following asynchronous li
2222
* ItemCheckedIn
2323
* ItemUncheckedOut
2424
* ItemAttachmentAdded
25-
* ItemAtttachmentDeleted
25+
* ItemAttachmentDeleted
2626
* ItemFileMoved
27-
* ItemVersonDeleted
27+
* ItemVersionDeleted
2828
* ItemFileConverted
2929

3030
Synchronous events are not supported in webhooks.
3131

3232
## Additional resources
3333

34-
* [Overview of SharePoint webhooks](../overview-sharepoint-webhooks)
34+
* [Overview of SharePoint webhooks](../overview-sharepoint-webhooks)

docs/apis/webhooks/webhooks-reference-implementation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -146,7 +146,7 @@ Create a web job that on a weekly basis reads all the subscription IDs from the
146146

147147
> **Note:** This web job is not part of this reference implementation.
148148
149-
The actual renewal of a SharePoint list webhook can be done using a [`PATCH /_api/web/lists('list-id')/subscriptions(‘subscriptionID’)`](./lists/update-subscription) REST call. In the reference implementation, updating of webhooks is implemented in the [WebHookManager](https://github.com/SharePoint/sp-dev-samples/blob/master/Samples/WebHooks.List/SharePoint.WebHooks.Common/WebHookManager.cs) class of the **SharePoint.WebHooks.Common** project. Updating a webhook is done using the **AddListWebHookAsync** method:
149+
The actual renewal of a SharePoint list webhook can be done using a [`PATCH /_api/web/lists('list-id')/subscriptions(‘subscriptionID’)`](./lists/update-subscription) REST call. In the reference implementation, updating of webhooks is implemented in the [WebHookManager](https://github.com/SharePoint/sp-dev-samples/blob/master/Samples/WebHooks.List/SharePoint.WebHooks.Common/WebHookManager.cs) class of the **SharePoint.WebHooks.Common** project. Updating a webhook is done using the **UpdateListWebHookAsync** method:
150150

151151
```csharp
152152
/// <summary>

docs/spfx/set-up-your-development-environment.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,10 +12,16 @@ Install [NodeJS](https://nodejs.org/en/) Long Term Support (LTS) version.
1212
* If you have NodeJS already installed please check you have the latest version using `node -v`. It should return the current [LTS version](https://nodejs.org/en/download/).
1313
* If you are using a Mac, it is recommended you use [homebrew](http://brew.sh/) to install and manage NodeJS.
1414

15-
After installing node, make sure you are running V3 or higher of npm by running the following command:
15+
After installing node, make sure you are running V3 of npm by running the following command:
1616

1717
```
18-
npm -g install npm@next
18+
npm -g install npm@3
19+
```
20+
21+
In case of Ubuntu Linux previous command might result in 'permission denied' message, so it should be instead executed as
22+
23+
```
24+
sudo npm -g install npm@3
1925
```
2026

2127
### Code Editors

docs/spfx/web-parts/basics/design-considerations-for-web-parts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
>**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 environnments.
44
>
55
6-
To get started designing web parts, you will need to be familiar with Office UI Fabric. You can use Fabric as a starting point for iconography, font ramp, color usage, animation, and the responsive grid. Building from this foundation is a good starting point even if your goal is to depart visually in order to match your own companys brand or look and feel.
6+
To get started designing web parts, you will want to be familiar with [Office UI Fabric](http://dev.office.com/fabric). All of the styles from [Fabric Core](https://github.com/OfficeDev/office-ui-fabric-core) – including icons, typography, color usage, animation, and the responsive grid – are loaded by default and available to your web part. Do not import a copy of Fabric for your web part, as this may conflict with the global copy. These classes provide a foundation to your web part's styling, which you can always depart from if you require different visuals to match your company's brand.
77

88
## Office UI Fabric React Components
99

0 commit comments

Comments
 (0)