Modern Page Content Types

Reading Time: 2 minutes

The recent announcement from Microsoft on modern page properties allows for a much better page editing experience. It will even allow for multiple Site Page content types in the Pages library, each with different metadata.

The Site Pages page library on both a SharePoint Communication site and a Modern Team site comes with the default Site Page content type. You can have multiple custom Site Page content types in the page library, this is nothing new, however with the new Page Details feature, we can more easily work with multiple content types through the UI.


To demonstrate, let’s say you have 2 content types in the Pages library:

  • Site Page (the default)
  • Adoption Page (custom)

Here is the Content type definition for the Adoption Page custom content type. I’ve added 2 custom managed metadata columns to it: AdoptionRole and AdoptionService.

Modern Page Content Types

This is a content type I use when building an Office 365 Adoption Center and is a quick way of organizing your modern pages by role and Office 365 service. Please refer to my blog post series for more details: Setup Targeted Training on Office 365 Adoption Center

If you want to create a new Adoption Page, you have 2 choices. You can either click New… Adoption page from the ribbon on the Site Pages library (left image below) OR if you’ve already created an Adoption Page, while on the page you can click New…copy of this page from the ribbon on the page (right image below).

 

If you choose the second option above, the copy will retain the content type definition (including all custom columns and their values) from the page being copied. You can open up the Page Details to make modifications. Check it out in this quick video…

Note: you cannot change the content type from the Page Details pane.

For those of you building out sites using modern pages, this is great news. The ability to have multiple content types in the pages library allows for more robust solutions to be built and the new Page Details feature makes it easier for information workers building modern pages to work with them.

Thanks for reading.

-JCK


Credit: Photo by Artem Bali from Pexels

4 comments

  1. Thanks for the post; I’ve been setting up a procedure document library for a team of about 20 people the past week and am starting to wonder if a page library might be a better option, especially now with these nifty metadata features (I can’t seem to wrestle SP doc library metadata properties into the content type document template (at least non-single line text metadata) anyway). The page authoring experience is much more inspiring than a word doc, too – imagine having procedure reference material in-line…pdfs, excel workbooks, video, etc…Site page libraries also has Flow for automations (email procedure Owner on a recurrence w/ attached or linked site page)
    just doing some thinking out loud…
    appreciate your blog,
    – Kurt

    1. Thanks Kurt, it’s always a good idea to rethink the design. Sometimes documents are the right way to go, but not always. Best of luck!
      -JCK

    2. Hi Kurt, A few more thoughts… I’d say the choice between documents and pages comes down to the rigor you require around approving and publishing your procedures. Although some approval options are coming to pages, documents still have more capabilities (major/minor versions, content approval, etc.) That said, I love sharing procedures using modern pages. I’ve done it on resource-type centers with a lot of success. Good luck!
      -JCK

  2. Thanks for sharing your thoughts – I was hoping you could provide a boil-down for me 🙂 I think we can wait for the approval options coming to pages, and while it’s not crystal clear yet how important version functionality will be, my sense is that we will give site pages a whirl. Worse case scenario we go back to the doc library…

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.