Skip to content

Commit 75014c3

Browse files
committed
Adding required metadata for scenario guidance
1 parent 57d245e commit 75014c3

File tree

6 files changed

+61
-3
lines changed

6 files changed

+61
-3
lines changed

docs/scenario-guidance/Development-models.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,14 @@
1+
---
2+
title: Development models
3+
description: Development models
4+
ms.date: 12/12/2018
5+
ms.prod: sharepoint
6+
author: vesajuvonen
7+
ms.author: vesaj
8+
ms.topic: sharepoint
9+
localization_priority: normal
10+
---
11+
112
# Development models
213

314
## Summary
@@ -111,4 +122,4 @@ This however raises a security challenges as scripts can be deployed to SharePoi
111122
Moreover any custom code hosted within the Script Editor web part does not have any kind of maintenance capability, governance, or life-cycle management. That's why starting from 2017 Microsoft introduced the [SharePoint Framework](#SharePointFramework) model, which is similar to the Script Editor web part, but works in the "modern" UI, supports the no-script flag and provides centralized governance and control for the SharePoint administrators.
112123

113124
### Articles
114-
* [Migrate existing Script Editor web part customizations to the SharePoint Framework](https://docs.microsoft.com/sharepoint/dev/spfx/web-parts/guidance/migrate-script-editor-web-part-customizations)
125+
* [Migrate existing Script Editor web part customizations to the SharePoint Framework](https://docs.microsoft.com/sharepoint/dev/spfx/web-parts/guidance/migrate-script-editor-web-part-customizations)

docs/scenario-guidance/Enterprise-Content-Management.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,12 @@
11
---
2-
manager: arnek
2+
title: Enterprise Content Management
33
ms.date: 3/9/2015
44
ms.audience: ITPro
55
ms.topic: article
66
ms.prod: sharepoint
7+
author: vesajuvonen
8+
ms.author: vesaj
9+
ms.topic: sharepoint
710
localization_priority: Normal
811
ms.assetid: 6f2336fc-0cdd-6596-fdb7-45607006b2c8
912
description: "Last modified: March 09, 2015"

docs/scenario-guidance/Line-of-Business-integration.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,14 @@
1+
---
2+
title: Line of Business Integration
3+
description: Line of Business Integration
4+
ms.date: 12/12/2018
5+
ms.prod: sharepoint
6+
author: vesajuvonen
7+
ms.author: vesaj
8+
ms.topic: sharepoint
9+
localization_priority: normal
10+
---
11+
112
# Line of Business Integration
213

314
## Summary

docs/scenario-guidance/Responding-to-changes.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,14 @@
1+
---
2+
title: Responding to changes
3+
description: Responding to changes
4+
ms.date: 12/12/2018
5+
ms.prod: sharepoint
6+
author: vesajuvonen
7+
ms.author: vesaj
8+
ms.topic: sharepoint
9+
localization_priority: normal
10+
---
11+
112
# Responding to changes
213

314
## Summary

docs/scenario-guidance/Site-provisioning.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,14 @@
1+
---
2+
title: Site Provisioning
3+
description: Site Provisioning
4+
ms.date: 12/12/2018
5+
ms.prod: sharepoint
6+
author: vesajuvonen
7+
ms.author: vesaj
8+
ms.topic: sharepoint
9+
localization_priority: normal
10+
---
11+
112
# Site Provisioning
213

314
## Summary
@@ -147,4 +158,4 @@ Actually, very often the answer is "it depends". Nevertheless, here are some inf
147158
* Sub Sites of the same Site Collection, can share a common hierarchical navigation structure, which improves the overall User Experience.
148159
* From an on-premises perspective, every single Site Collection can be associated with a dedicate database file, which is not the case for a Sub Site, which can only stay in its parent Site Collection database. Thus, you can have more granular backup and maintenance policies at the Site Collection level, rather than at the Sub Site level, as long as you don't use third party management tools.
149160
* From an on-premises perspective, a Site Collection can be easily moved across different database files, while a Sub Site can just follow its parent Site Collection database.
150-
* Having multiple Sub Sites within a Site Collection allows you to leverage the Content Query web part (on-premises or in the classic UI of SharePoint Online) to achieve better data aggregation across sites.
161+
* Having multiple Sub Sites within a Site Collection allows you to leverage the Content Query web part (on-premises or in the classic UI of SharePoint Online) to achieve better data aggregation across sites.

docs/scenario-guidance/Solutions-deployment.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,14 @@
1+
---
2+
title: Solutions Deployment and Maintenance
3+
description: Solutions Deployment and Maintenance
4+
ms.date: 12/12/2018
5+
ms.prod: sharepoint
6+
author: vesajuvonen
7+
ms.author: vesaj
8+
ms.topic: sharepoint
9+
localization_priority: normal
10+
---
11+
112
# Solutions Deployment and Maintenance
213

314
## Summary

0 commit comments

Comments
 (0)