Mapping the impact of a major CMS change
Review editing, models, roles, APIs and deployment separately. Verify changes through representative tasks rather than release marketing alone.
Putting content management into practice
A content model defines independently maintained and reusable information. Authoring, preview, approval and publication form a workflow; an API response validates only one part.
Checking the result
Have real editors create, change and restore content using long headings, missing fields and multiple languages. Record development dependencies and release ownership.
