Forum Discussion
Ivan54
Mar 03, 2017Bronze Contributor
How to do a custom modern page library?
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 remo...
Christopher Johnson
Jul 28, 2017Brass Contributor
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 JohnsonJul 28, 2017Brass Contributor
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 GossOct 16, 2017Brass ContributorHi 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- Ivan54Mar 30, 2018Bronze ContributorNot a full solution, but getting there. New Roadmap Development: Feature ID: 27251
- Max GossOct 16, 2017Brass ContributorHi 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