< cd ../projects

~/projects/content-management-system

Content Management System

role
Developer
  • CMS
  • Web
  • Content modelling
  • Publishing workflow

The brief

Every content change depended on a developer, so simple edits sat in a queue behind real development work. The team needed to publish themselves — without being able to break the site doing it.

What I did

  • Modelled the content as structured types and fields rather than free-form pages, so the same content can be reused in several places and stays consistent.
  • Set up roles and a draft to review to publish flow, so nothing reaches the public site unreviewed.
  • Added media handling with automatic resizing and predictable naming, so editors are not uploading raw camera files.
  • Built previews, so an editor sees exactly how a change will look before it goes live.
  • Wrote short task-based guides and ran a hands-on session with the people who use it daily.

Outcome

  • Routine content changes no longer wait on a developer
  • Structure keeps the layout consistent no matter who edits
  • Every change is versioned and attributable to a person