Best practice: A dedicated Playbook Communication Site with a metadata-driven catalogue
I found something important in Microsoft's documentation that changes the options.
A SharePoint Document Library can contain links to existing SharePoint Pages.
You create a library item using New → Link, pointing to an .aspx Playbook. That link appears as an item in the library and opens the original page.
That means we do not necessarily have to convert 200 Playbooks just to take advantage of Document Library filtering and presentation.
It also means we have a credible OOTB option that separates the catalogue from the content.
Three supported approaches worth considering
|
Architecture |
How the Playbook opens |
How the ToC works |
Principal obstacle |
|---|---|---|---|
|
1. Communication Site + Site Pages |
Native |
Highlighted Content, filtered through searchable metadata |
Search-property mapping, indexing, and display limitations |
|
2. Communication Site + Document Library of links |
Link opens the existing |
Native Category filtering, grouping, views and Document Library web part |
Separate catalogue entries must be created and maintained |
|
3. Communication Site + Document Library of actual files |
Browser opens a supported file or its viewer |
Native Category filtering, grouping, views and web part |
Existing Playbook content needs an appropriate file format |
Option 2 is the one I would test first. It preserves the existing pages while giving the ToC its own proper library interface.
But it's not a perfect solution. Each Playbook has a page and a library link entry, so the two records need maintenance. It is a genuine tradeoff, not something to hide.
Microsoft documents the underlying mechanisms for both the Document Library web part and the Highlighted Content web part.
Which site template?
Microsoft provides several starting points for Communication Sites. These are the choices I'd consider for your requirement.
