Hi, I could use some help with this.I tried to create a custom document library (with extra metadata) and exchanging the default document content type with the modern website pages one. I even removed the document content type. All good so far.But even though I click new > page and the modern authoring canvas opens, the page is not stored in my new custom library, but instead into the default one. I was kind of trying to avoid messing with the default libraries. Any possible pitfalls by adding additional columns to the default pages library? Anyone have some ideas?

Hi everyone. You're right that this isn't supported just yet. We have it on our backlog but don't have a concrete timeline right now. Feedback heard though. -Dave

will do. If it is not possible at the moment, I wouldn't my adding metadata columns to the default SitePages library, though I'm generally cautious of editing Microsofts default libraries.Any official guidance would be welcome here.

maybe Dave Cohen (US)or;Alina Skarbovsky could pitch in since they were actively involved in the "Modern Pages Rollout Thread".I've just tried to add additional metadata to the default SitePages library, and realized that the new columsn aren't added to the modern pages contenttype (only to the classic wiki page), additionaly the "customize content type" action is somehow disabled for this default library.So this isn't a workaround either. So the question remains, how do I create modern pages in a custom library, where I can enrich the pages with additional metadata?

Thanks for the update Dave, I hope you can tell us a concrete timeline soon

How to do a custom modern page library?

Christopher Johnson
Brass Contributor
Jul 28, 2017
I can confirm that adding additional metadata to the default Site Pages library doesn't work, either. Looks like the Site Page content type is locked, because I can't add site columns to it :(
- Christopher Johnson
  Brass Contributor
  Jul 28, 2017
  UPDATE:
  I was, however, able to create a custom content type that inherits from the modern Site Page and add my own metadata to that. I then added this content type to the Site Pages library, and can create instances of this content type.
  
  The caveat is that even if I create an instance of this content type, once I save the page, it's actually created as an instance of Site Page. I then can update the content type of the item to my custom content type. Definitely a bit buggy and not a great UX.
  - Max Goss
    Brass Contributor
    Oct 16, 2017
    Hi all,
    So using the approach outlined by Christopher I can create a page library with custom meta data. It's not too bad an experience to ask the site admin to edit the item, change the content type and apply my meta data. The question is, should we go down this route and build business logic based on extending the site page with a custom content type? My worry would be that this might get depreciated in a future ms release. Would be interested to hear thoughts on how people are trying to get around this modern page meta data limitation? Or are people resorting to no meta data / folders to group related pages?
    Thanks,
    -Max
Deleted
Mar 05, 2017
seems like it is a bug..
- Ivan54
  Bronze Contributor
  Mar 06, 2017
  My guess would be that the "+ Page" button is currently hardwired to the default SitePages Library and this may just be an unintended consequence of it.
  - jcgonzalezmartin
    MVP
    Mar 06, 2017
    If you find any guidance or documentation about how to achieve this, please share it here....but I tend to agree with you in regards of the no know consequences of customizing with new columns the Site Pages document libraries...my "classic" understanding of SharePoint tells me that you could do it with no problems...but we are in modern and Microsoft is re-using this document library on a per site basis

Forum Discussion

How to do a custom modern page library?

Share

Resources