I’m not versed in SharePoint Online, so this might be different for the on-premise version of SharePoint 2013 that is my current focus. As I was preparing instructions for adding Script Editor Web parts, I instinctively directed the user to the Site Pages library. This got me to thinking about why. As I started to look in library settings, especially, the Advanced Settings, I noticed that you don’t even have an option to select to use Content Types and the library automatically uses them with Wiki Pages and Web Part Pages.
So I created a new document library allowing Content Types and added “Web Part Pages”. I couldn’t find “Wiki Pages” in the content types to be added. I was able to the Script Web Part Editor and my code worked as expected.
I just wanted to see if I’m missing some major point about the use of Document Libraries vs Site Page Document Libraries.
Thanks Nick,
This facility doesn’t conform to the Publishing Infrastructure. I got here too late to help in that model.
I agree with your assessment of the functionality: documents are for documents basically and Site Page and Pages handle page layout and web part zones–however, you can add web part zones as a content type to document libraries.
thanks,
Stephan
Hey Stephan,
Those things are meant to be used in two very different ways. The Site Pages library is meant only to hold your regular wiki/modern SharePoint type pages. You aren’t really supposed to be keeping documents in it. Document libraries are where you want to keep your documents.
However, the way you describe this question, it sounds to me like you want publishing pages, that have page layouts and web part zones. If that’s the case, you need to have publishing turned on, which will create a “Pages” library, where those pages would live.
