We rebuilt our website on the Jamstack (without changing CMS)
Separate retained models from changed frontend routes and test preview, release and caching. Retaining an API does not automatically preserve old URLs.
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.
