Keeping technical supplier relationships transparent
Explain platform, implementation and hosting responsibilities, costs and support routes. Make account ownership and data location clear.
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.
