Skip to content

Commit 0e4a2b2

Browse files
Samuel LevesqueVesaJuvonen
authored andcommitted
Added SharePoint Server 2016 (SharePoint#1103)
Nothing changed in branding and site provisioning between 2013 and 2016 so this article also applies to SharePoint Server 2016
1 parent 71e289c commit 0e4a2b2

File tree

1 file changed

+14
-7
lines changed

1 file changed

+14
-7
lines changed

docs/solution-guidance/Branding-and-site-provisioning-solutions-for-SharePoint.md

Lines changed: 14 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
2-
title: Branding and site provisioning solutions for SharePoint 2013 and SharePoint Online
2+
title: Branding and site provisioning solutions for SharePoint Server 2013, SharePoint Server 2016 and SharePoint Online
33
ms.date: 11/03/2017
44
---
5-
# Branding and site provisioning solutions for SharePoint 2013 and SharePoint Online
5+
# Branding and site provisioning solutions for SharePoint Server 2013, SharePoint Server 2016 and SharePoint Online
66

77
The introduction of the Cloud Add-in Model and add-ins for SharePoint provides alternatives to existing, established ways of branding and provisioning SharePoint sites.
88

9-
_**Applies to:** Office 365 | SharePoint 2013 | SharePoint Online_
9+
_**Applies to:** Office 365 | SharePoint Server 2013 | SharePoint Server 2016 | SharePoint Online_
1010

1111
Up to now, you might have used the SharePoint feature framework, site templates, web templates, and site definitions to provision your sites and site collections. The remote provisioning pattern shows you how to create custom add-ins for SharePoint that provision site branding and perform other site provisioning tasks.
1212
The articles in this section provide information about using add-ins for SharePoint to provision and manage site branding, a pattern that is sometimes referred to as remote provisioning.
@@ -85,15 +85,22 @@ To understand your branding options and the implications that site customization
8585

8686
### File system
8787

88-
SharePoint stores files in the file system ("hive"). In SharePoint 2013, this ___location is called the "15-hive". The following is the path to the 15-hive.
88+
SharePoint stores files in the file system ("hive").
8989

90+
In SharePoint Server 2013 and SharePoint Server 2016, this ___location is called the "15-hive" or "16-hive".
91+
92+
The following is the path to this ___location :
93+
94+
SharePoint Server 2013 :
9095
`%program files%/Common Files/Microsoft Shared/Web Server Extensions/15/`
96+
SharePoint Server 2016 :
97+
`%program files%/Common Files/Microsoft Shared/Web Server Extensions/16/`
9198

92-
The 15-hive includes several subfolders that store files you'll use when branding and provisioning sites.
99+
The 15-hive and 16-hive includes several subfolders that store files you'll use when branding and provisioning sites.
93100

94101
### Content databases
95102

96-
Content databases store SharePoint content objects, such as site collections. A content database is automatically installed for every site collection when you deploy SharePoint 2013. All the content for a site collection is stored in one content database on one server. However, a content database can be associated with more than one site collection, and you can attach content databases to a SharePoint web application. You might need to move content from one content database to another, for example when the size of the content will soon exceed the size of the content database.
103+
Content databases store SharePoint content objects, such as site collections. A content database is automatically installed for every site collection when you deploy SharePoint Server 2013 or SharePoint Server 2016. All the content for a site collection is stored in one content database on one server. However, a content database can be associated with more than one site collection, and you can attach content databases to a SharePoint web application. You might need to move content from one content database to another, for example when the size of the content will soon exceed the size of the content database.
97104

98105
Some characteristics of a content database vary depending on how the site collection is used. For example, sites are often write-intensive, while other types of content, such as read-only documents, are read-intensive. How content is used affects aspects of the content database, such as size and performance.
99106

@@ -117,7 +124,7 @@ The state of SharePoint files and content affects how easy it is to apply update
117124
## Site branding and provisioning with the Cloud Add-in Model
118125
<a name="sectionSection6"> </a>
119126

120-
In SharePoint 2013, you can use custom CSOM code in add-ins for SharePoint to provision SharePoint site collections, sites, and subsites with branding elements. This site provisioning pattern is called remote provisioning. SharePoint is increasingly focused on cloud-based deployments, so this pattern was created to help you use SharePoint's out-of-the-box capabilities to provision site branding in a way that reduces complexity and long-term operational costs.
127+
In SharePoint Server 2013 or SharePoint Server 2016, you can use custom CSOM code in add-ins for SharePoint to provision SharePoint site collections, sites, and subsites with branding elements. This site provisioning pattern is called remote provisioning. SharePoint is increasingly focused on cloud-based deployments, so this pattern was created to help you use SharePoint's out-of-the-box capabilities to provision site branding in a way that reduces complexity and long-term operational costs.
121128

122129
### What can I do with the Cloud Add-in Model?
123130

0 commit comments

Comments
 (0)