Choose how pages are built and delivered.
A headless CMS separates content editing from the interface visitors use. Pages can be generated in advance, rendered on request or delivered through a combination of approaches.
When pages are generated in advance and served through a content network, visitors can receive them without a CMS database query for each page view. Publishing time depends on the build process and the size of the site.
Where the existing CMS is suitable, we can retain it and connect a new frontend. Changes to editing workflows and previews are planned with your team.
The decisions behind it.
Structured content
Content types and fields reflect what the organization publishes, with templates controlling how it is displayed.
Caching and delivery
Caching is configured across the CMS, application and content network where appropriate to the architecture.
Dependencies and licensing
Plugins and services are selected for the project, with licensing and maintenance requirements documented.
Publishing tools
Previews, search metadata, analytics and consent tools are integrated where specified in the scope.
An editing workflow your team can use.
Editors work with named fields for text, images and other content. Templates help keep pages consistent, while permissions define who can edit, review and publish.
We plan previews, media handling and publishing steps with the team that will use them. New content types and layouts can be added as requirements develop, with design and development work scoped where needed.
Accessibility checks and content review remain part of publishing. Templates support consistency but cannot guarantee that every entry is accessible.
