The evolution of Software as a Service (SaaS) and rapid, continuous release of software updates drive us to ever more quickly develop and publish content to help customers understand the differences among software versions. As soon as an update is released, customers expect to find the information that they need to understand how specific changes and additions to the software might impact their businesses and solutions. Consequently, content models have to evolve to accommodate an “evergreen” design to present information that supports multiple software versions in a single place, and content development and management processes have to become truly agile to publish at speed for discoverability and relevance.
To keep pace with the evolving Microsoft Office 365, the Office Content Publishing Team designed, tested, and implemented an evergreen content model for Office 365 developer content on MSDN. We’ll walk through the primary components of our model’s design and implementation, including key elements of the content and reflection and other practices for monitoring changes to the software. We’ll also share our hypotheses, experiments, KPIs for measuring the model’s success with customers, and the data that we’ve collected so far. Our goal is to provide you with practical guidance that can help you think about or implement evergreen content models for your projects.