Start with the content model
List the information the team publishes: services, people, projects and articles. Define which fields repeat and which relationships matter. A service page and a practitioner profile may share a design language while needing different editing controls.
Test the editing workflow
Ask an editor to create a page, replace an image and update a shared section. Note where the task needs developer support. Use reusable patterns for consistency and agree which layout choices remain editable.
Plan the handover
Document ownership, publishing roles, backups and the update process. Include a short editorial guide with image guidance and a review checklist. Treat the CMS as an ongoing working environment rather than a one-time visual installation.
Map a real publishing task
Describe one update from request to publication: changing a service, replacing a project image or publishing an article in two languages. Identify who writes, who checks and who publishes. The CMS should make this routine understandable without asking an editor to rebuild a layout. Separate reusable content from page-specific composition so the same service name does not need to be corrected in several places.
Define fields before templates
For a case study, agree on the project name, summary, services, evidence, delivery metrics and related projects. Give images alternative text and captions where context matters. Make video optional, with a poster and a written explanation. A missing video should not produce an empty panel. For translations, decide which fields are translated and which references are shared; review both versions before publication.
Run an editorial acceptance test
Ask the future editor to create a draft, replace an image, change a related link and preview the mobile layout. Check permissions using the actual editor role. Then test an unusually long title and an entry without optional media. The handover should include field guidance, image dimensions, translation steps and a recovery procedure. Record the tasks that still require developer help instead of hiding them behind a promise that everything is editable.