2. SPC220

4. Web Template FundamentalsCreating Web Templates Using Web Templates Web Templates and App Webs Wrap Up

6. <= SharePoint 2007 >= SharePoint 2010 Site Definitions – Deployed to the SharePoint Server – ONET.xml in [SharePointRoot]\Template\SiteTemplates folder – WebTemp.xml in [SharePointRoot]\TEMPLATE\1033\XML folder – Can’t be changed after sites have been created based on it Site Templates – “Save Site as Template” creates.stp files

7. <= SharePoint 2007 >= SharePoint 2010 Web Templates – Deployed to the SharePoint Server or Solutions Gallery – Can be changed after sites have been created based on it Site Templates – “Save Site as Template” creates.wsp files – Uses Web Template improvements

11. Creates a sandboxed solution Stored in site collection solution gallery Can be imported into Visual Studio

12. “Based” on a site definition Do NOT inherit from their “base” site definition Can be changed or deleted after they have been used

14. Web Templates created in Visual Studio Saving sites as templates Can be based on publishing sites and can use the publishing feature That have the publishing feature activated is not supported

16. Create URL for the siteProvision GLOBAL onet.xml Site collection: Activate site collection scoped features in defined order Sub site: Verify that site collection scoped features are activated Activate site scoped features from onet.xml in defined orderCreate list instances from onet.xml

20. Copy ONET.xml from an out of the box site definition and strip it ONET.xml file can only contain one configuration Configuration needs to have ID=0

21. More features will make the site creation slower Not enough features makes upgrading very challenging Be careful with Site scoped features – can block sub site creation

22. Create a hidden web scoped feature Add it to the WebFeatures section of the onet.xml file Store the Web Template name, feature ID and version in site property bag

24. Farm SolutionSandboxed Solution Farm or Site scoped feature ONET.xml file is stored in the feature folder with elements.xml file Site scoped feature ONET.xml file and elements.xml file are stored in the content database

25. Web Templates that are built as sandboxed solutions can be deployed to Office 365 Sandboxed solutions are deprecated, but still fully functional in SharePoint 2013 Make sure the sandboxed solution can be removed after creating the site

26. Can be used from code Apply with [web template feature GUID]# [web template name]

27. Building Web Templates

30. You cannot deploy web templates to create other sites within an App You can only deploy a web template to create the App Web with

31. Browse http://teamsite.wingtip.com/sites/apptest/_layouts/15/start.aspx#/SitePages/Home.aspx Host Web http://app-fef8493a3feb20.wingtipapps.com/sites/apps/BambooWeather/Pages/Home.aspx App Web Add App

32. Either create the App Web using site definition App#0 (default) Or create the App Web using a custom web template

36. Use web templates to create templated sites No templated sites in Apps – use full trust or sandboxed solutions Build with deprecation of sandboxed solutions in mind Plan feature scope and amount

38. MySPC