Support for reusable content in MS365 SharePoint pages

Question

My team manages a knowledge base in SharePoint 365 that is a site pages library (in other words, we're not using a documents library of Word, PowerPoint, PDF, etc. files). Many of the pages we manage have overlapping content, ranging from definitions to entire webparts of identical text or images. When one thing changes, every page requires manual updating in our current structure. I'm heading up a project to rebuild our information architecture.

Unfortunately, I'm unaware of a native feature in SharePoint to apply a content reuse solution as allowed by other platforms (XML-based solutions like DITA, MadCap Flare, etc.). My goal is to allow us to invoke reusable content so that if we need to change 5-10 pages, we can simply update the text in one source location and automatically cascade it to every page that uses it.

For example, if we change a set of steps recur in 15 procedures, or a product title changes that appears on 100 pages, how can I update that in one place and make it automatically apply to every page in our library?

Answer 1

I have the same question and am surprised that Microsoft has not come up with a solution for this.

Answer 2

Hi @Joel Wilcox ,

SharePoint does not have a native feature to apply a content reuse solution as allowed by other platforms such as XML-based solutions like DITA, MadCap Flare, etc.

If the web parts such as library and list that need to reference data sources, changes to the data source will be synchronized to the web part. If it is other types or custom web parts, there is currently no available method. It is recommended that you go to the Partner Center to see if there is a better solution.Have a nice day!

---

If the answer is helpful, please click "Accept as Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.