Skip to content

Commit 6afbb9a

Browse files
committed
2 parents 50de621 + aa6956a commit 6afbb9a

26 files changed

+891
-693
lines changed

.openpublishing.publish.config.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,4 +80,4 @@
8080
"nuget_feed": "https://www.myget.org/F/op/api/v2"
8181
}
8282
]
83-
}
83+
}

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Feel free to use [Issues]((https://github.com/SharePoint/sp-dev-docs/issues)) li
1212

1313
We’ll also monitor [#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.
1414

15-
You can also tweet / follow [@officedev](https://twitter.com/officedev) or [@officedevpnp](https://twitter.com/officedevpnp).
15+
You can also tweet / follow [@Microsoft365Dev](https://twitter.com/Microsoft365Dev) or [@officedevpnp](https://twitter.com/officedevpnp).
1616

1717
## SharePoint Framework Releases
1818

@@ -94,7 +94,7 @@ You can also tweet / follow [@officedev](https://twitter.com/officedev) or [@off
9494

9595
To keep track of improvements to the Office 365 Framework, please take a look at:
9696

97-
* [@SharePoint](https://twitter.com/sharepoint), [@OfficeDev](https://twitter.com/officedev) and [@OfficeDevPnP](https://twitter.com/officedevpnp) on Twitter
97+
* [@SharePoint](https://twitter.com/sharepoint), [@Microsoft365Dev](https://twitter.com/Microsoft365Dev) and [@OfficeDevPnP](https://twitter.com/officedevpnp) on Twitter
9898
* [Office Developer Blog](https://developer.microsoft.com/en-us/office/blogs/)
9999

100100
Provide Feedback:
@@ -111,4 +111,4 @@ The SharePoint Framework is now generally available at Office 365.
111111

112112
## Have Fun
113113

114-
We look forward to seeing what you build! Please tweet us at @OfficeDev, @OfficeDevPnP or @SharePoint with the #SPFx tag!
114+
We look forward to seeing what you build! Please tweet us at @Microsoft365Dev, @OfficeDevPnP or @SharePoint with the #SPFx tag!

docs/community/community.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,8 @@
11
---
22
title: SharePoint Developer Community (SharePoint PnP) resources
33
description: The SharePoint Development Community (also known as the SharePoint PnP community) is an open-source initiative coordinated by SharePoint engineering.
4-
ms.date: 04/02/2019
4+
ms.date: 02/04/2020
55
ms.prod: sharepoint
6-
76
localization_priority: Priority
87
---
98

@@ -15,10 +14,10 @@ The SharePoint Development Community (also known as the SharePoint PnP community
1514

1615
- [SharePoint Developer Blog](https://developer.microsoft.com/en-us/office/blogs/) - Latest developer news around SharePoint and Office 365
1716
- [SharePoint Developer Videos](https://aka.ms/spdev-videos) - Latest guidance videos, training videos, and community call recordings
18-
- [OfficeDev Twitter](https://twitter.com/officedev) - Official communication channel for SharePoint and Office 365 developer topics
19-
- [OfficeDevPnP Twitter](https://twitter.com/officedevpnp) - Community account for SharePoint and Office 365 developer topics
20-
- [OfficeDev Facebook](https://www.facebook.com/OfficeDev/) - Official communication channel for SharePoint and Office 365 developer topics
21-
- [OfficeDevPnP Facebook](https://www.facebook.com/OfficeDevPnP/) - Community account for SharePoint and Office 365 developer topics
17+
- [Microsoft365Dev Twitter](https://twitter.com/Microsoft365Dev) - Official communication channel for SharePoint, Office 365, Windows 10 and Enterprise Mobility + Security developer topics
18+
- [Microsoft 365 PnP Twitter](https://twitter.com/officedevpnp) - Community account for Microsoft 365 and SharePoint topics
19+
- [Microsoft365Dev Facebook](https://www.facebook.com/Microsoft365Dev) - Official communication channel for SharePoint, Office 365, Windows 10 and Enterprise Mobility + Security developer topics
20+
- [Microsoft 365 PnP](https://www.facebook.com/OfficeDevPnP/) - Community account for SharePoint and Office 365 developer topics
2221

2322
## GitHub
2423

docs/community/contribute.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: SharePoint Developer Community contribution
33
description: Contribution options towards the SharePoint Developer Community.
4-
ms.date: 03/29/2018
4+
ms.date: 02/14/2020
55
ms.prod: sharepoint
66
localization_priority: Normal
77
---
@@ -46,4 +46,3 @@ Awesome! Here are a few suggestions:
4646
* Suggest a live demo in one of the community calls.
4747

4848
If you have other ideas on how you might contribute, don't hesitate to reach out and let us know.
49-

docs/community/open-source-projects.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: SharePoint Developer Community open source projects
33
description: Open-source projects coordinated by the SharePoint PnP initiative
4-
ms.date: 06/18/2018
4+
ms.date: 02/14/2020
55
ms.prod: sharepoint
66
localization_priority: Priority
77
---
@@ -10,13 +10,10 @@ localization_priority: Priority
1010

1111
There are numerous open-source projects that are coordinated by the SharePoint PnP initiative. These are open-source, community-driven initiatives that are still closely involved with SharePoint engineering, but are not part of the standard product or service offerings.
1212

13-
<br/>
14-
1513
| Repository | Description |
1614
|--------|--------|
1715
| [SharePoint Starter kit](https://github.com/SharePoint/sp-starter-kit) | A starter kit for showing how to extend modern experiences in SharePoint Online by extending them with modern extensibility options. |
1816
| [SharePoint Provisioning Service templates](https://github.com/SharePoint/sp-dev-provisioning-templates) | Tenant templates used by the [SharePoint Provisioning Service](https://provisioning.sharepointpnp.com) to easily provision sample content and structures demonstrating what's possible with modern SharePoint experiences. |
19-
| [GDPR Activity Hub](https://github.com/SharePoint/sp-dev-gdpr-activity-hub) | A starter kit for building a management hub for EU GDPR (European Global Data Protection Regulation). |
2017
| [Office 365 CLI](https://sharepoint.github.io/office365-cli/) | A cross-platform command-line interface (CLI) that allows users on any platform to manage various configuration settings of Office 365. |
2118
| [Office 365 Developer PnP Core Component](https://github.com/SharePoint/PnP-Sites-Core) | An extension component that encapsulates commonly used remote CSOM/REST operations as reusable extension methods on out-of-the box CSOM objects. |
2219
| [PnP PowerShell cmdlets](https://docs.microsoft.com/powershell/sharepoint/sharepoint-pnp/sharepoint-pnp-cmdlets?view=sharepoint-ps) | Allow you to perform complex provisioning and artifact management actions for SharePoint. The commands use CSOM and can work against both SharePoint Online as well as SharePoint on-premises. |

docs/community/social-media.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
title: Social Media
3+
author: andrewconnell
4+
ms.author: v-johnco
5+
ms.date: 2/5/2020
6+
ms.audience: Developer
7+
ms.prod: sharepoint
8+
localization_priority: Priority
9+
---
10+
11+
# SharePoint Development on Social Media
12+
13+
Please monitor and follow us on Twitter:
14+
15+
- [@Microsoft365Dev](https://twitter.com/Microsoft365Dev)
16+
- [@OfficeDev](https://twitter.com/officedev)
17+
- [@SharePoint](https://twitter.com/sharepoint)
18+
- [@m365pnp](https://twitter.com/m365pnp)

docs/design/semantic_slots.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ The current semantic slot list is defined by commonly used design patterns in Sh
6666

6767
Semantic slots should be assigned based on the function of a page element. The name of a semantic slot can quickly tell you how it’s meant to be used. You can find all existing semantic slots and their use case examples in the [Fabric semantic colors documentation](https://github.com/OfficeDev/office-ui-fabric-react/blob/master/packages/styling/src/interfaces/ISemanticColors.ts).
6868

69-
Fabric palette colors should be referenced from your site theme’s color ramp. If your site is using a SharePoint out of the box theme, you can reference [SharePoint theme color ramps](https://fluentfabric.azurewebsites.net/#/color/products). If your site is using a custom theme, you can generate a unique color ramp using the [Fabric theme generator](https://developer.microsoft.com/fabric#/styles/themegenerator).
69+
Fabric palette colors should be referenced from your site theme’s color ramp. If your site is using a SharePoint out of the box theme, you can reference [SharePoint theme color ramps](https://fluentfabric.azurewebsites.net/#/color/products). If your site is using a custom theme, you can generate a unique color ramp using the [Fabric theme generator](https://aka.ms/themedesigner).
7070

7171
![Example of redlines for a web part in the None section background](../images/doc-semantic-slot-1.png)
7272

docs/general-development/sharepoint-2019-development-platform.md

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -10,26 +10,26 @@ localization_priority: Priority
1010

1111
Article contains details around supported development capabilities in the SharePoint 2019.
1212

13-
**Supported capabilities**
14-
15-
* Modern and classic pages
16-
* Modern sites - modern team and communication site
17-
* Classic sites are also supported
18-
* Column formatting - Only supports "Basic Styled Syntax", "Excel Styled Syntax" is not supported.
19-
* SharePoint Framework client-side web parts with SharePoint Framework v1.4.x
20-
* SharePoint Framework extensions in modern experiences with SharePoint Framework v1.4.x
21-
* Webhooks for list items
22-
* Asset packaging and automatic JavaScript file hosting from app catalog
23-
* "Tenant" scoped deployment of SharePoint Framework solutions
24-
* ALM APIs for add-in and SharePoint Framework solution management
25-
26-
**Not supported capabilities**
27-
28-
* Site Designs and Site Scripts
29-
* Hub sites
30-
* Site collection app catalog
31-
* "Tenant" properties
32-
* Custom modern themes for communication site or modern team site
13+
## Supported capabilities
14+
15+
- Modern and classic pages
16+
- Modern sites - modern team and communication site
17+
- Classic sites are also supported
18+
- Column formatting - Only supports "Basic Styled Syntax", "Excel Styled Syntax" is not supported.
19+
- SharePoint Framework client-side web parts with SharePoint Framework v1.4.x
20+
- SharePoint Framework extensions in modern experiences with SharePoint Framework v1.4.x
21+
- Webhooks for list items
22+
- Asset packaging and automatic JavaScript file hosting from app catalog
23+
- "Tenant" scoped deployment of SharePoint Framework solutions
24+
- ALM APIs for add-in and SharePoint Framework solution management
25+
26+
## Not supported capabilities
27+
28+
- Site Designs and Site Scripts
29+
- Hub sites
30+
- Site collection app catalog
31+
- "Tenant" properties
32+
- Custom modern themes for communication site or modern team site
3333

3434
You should always have the latest SharePoint Framework version installed and choose the target environment for the newly created solution to be **SharePoint 2019**. This option will create you an optimal solution structure with the matching SharePoint Framework version for SharePoint 2019.
3535

docs/sp-add-ins/use-odata-query-operations-in-sharepoint-rest-requests.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -91,8 +91,8 @@ Accept: "application/json;odata=verbose"
9191
| **Supported** | **Not supported** |
9292
| :------------------------------------------------------------------------ | :--------------------------------------------------------------------------------------------------------------- |
9393
| **Numeric comparisons** (lt le gt ge eq ne) | **Arithmetic operators** (add, sub, mul, div, mod)<br/>**Basic math functions** (round, floor, ceiling) |
94-
| **String comparisons** startswith substringof eq ne | endswith replace substring tolower toupper trim concat |
95-
| **Date and time functions** day() month() year() hour() minute() second() | DateTimeRangesOverlap operator<br/>Querying as to whether a date time falls inside a recurrent date time pattern |
94+
| **String comparisons** startswith, substringof, eq, ne | endswith, replace, substring, tolower, toupper, trim, concat |
95+
| **Date and time functions** day(), month(), year(), hour(), minute(), second() | DateTimeRangesOverlap operator<br/>Querying as to whether a date time falls inside a recurrent date time pattern |
9696

9797
The following figure shows the supported OData query options.
9898

docs/spfx/extensions/get-started/serving-your-extension-from-sharepoint.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Deploy your extension to SharePoint (Hello World part 3)
33
description: Deploy your SharePoint Framework Application Customizer to SharePoint and see it working on modern SharePoint pages.
4-
ms.date: 01/28/2020
4+
ms.date: 02/11/2020
55
ms.prod: sharepoint
66
localization_priority: Priority
77
ms.custom: scenarios:getting-started
@@ -131,7 +131,7 @@ Your **package-solution.json** should look somewhat following after the needed e
131131

132132
```json
133133
{
134-
"$schema": "https://dev.office.com/json-schemas/spfx-build/package-solution.schema.json",
134+
"$schema": "https://developer.microsoft.com/json-schemas/spfx-build/package-solution.schema.json",
135135
"solution": {
136136
"name": "app-extension-client-side-solution",
137137
"id": "98a9fe4f-175c-48c1-adee-63fb927faa70",

0 commit comments

Comments
 (0)