Skip to content

Content Studio

A way of working where content, design and code are produced in parallel, with tools that hold it together

At its core Content Studio is a way of working, today a written concept. Design Bridge starts from the code and creates the design. Content Studio starts at the other end, in structure and content, tied to a design system and to finished modules in a content management system.

  • Working in parallel. The people who write the texts, the people who design and the people who build should be able to work at the same time, because everyone works against the same modules.
  • Structure first, content when it suits. A page should be possible to lay out with modules before the texts exist, with the texts added later.
  • Modules that already exist. Each module should be either already built and checked, or simple to build. New ones are added when needed. The goal is that a client's own design system and modules can also be brought in.
  • Out to design when needed. Content and modules should be possible to export for design work in Figma or Claude Design.
  • Not tied to one system. The first target is Umbraco, but the idea is to extend it to systems like Contentful, WordPress or Drupal.

The idea comes from what I saw in agency projects, where content, design and development often waited for each other. So far it is a written concept, with a first pilot against Umbraco where Claude Code built the content types directly from a content specification. My own project, not client work.