Technology
CMS & PlatformsStrapi, Sanity, WordPress
The CMS stack we reach for, the trade-offs we name, and when we use something else — Strapi and Sanity for the headless with a custom front end, WordPress for the team that already runs it, with the choice made against the editorial workflow, the front end and the deploy.
What we use it for
Strapi for the open-source headless CMS with a self-hosted backend and a custom front end. Sanity for the hosted headless CMS with the real-time collaboration and the structured content. WordPress for the team that already runs it or the content-heavy site that does not need a headless architecture.
We extend the stack with the front end the product needs — Next.js for the static or SSR front end, a custom admin for the editorial workflow, the integrations the marketing team uses.
When we choose it over the alternative
Strapi is right when the team needs a self-hosted CMS with a custom data model and a custom front end. Sanity is right when the team needs a hosted CMS with the real-time collaboration and the structured content. WordPress is right when the team is already strong in it, the content is editorial, and the front end is a WordPress theme.
The right answer depends on the editorial workflow, the front end and the deploy. We will say so on the call, with a written rationale for the choice and the trade-offs named.
When we do not choose it
We do not choose a headless CMS when the editorial workflow does not need the structure and the front end is a WordPress theme. We do not choose WordPress when the front end is a Next.js SPA or a mobile app and the content needs to be served through an API. We do not choose the default when the deploy constraint (a managed platform, a specific region) makes the alternative the right answer.
Frequently asked
The questions the team asks
- WordPress or headless?
- WordPress is the right answer for an editorial-led team publishing articles, case studies and landing pages, with a WordPress front end. A headless CMS (Strapi, Sanity) is the right answer when the front end is a Next.js SPA or a mobile app, or when the content needs to be served through an API.
- Can the team update the site without a developer?
- That is the default. We hand over a CMS with the page sections modelled as editable blocks, plus a short walkthrough recording. The team runs the day-to-day, and the maintenance retainer covers the harder questions.
- How do you handle the multi-language?
- Locales, translations and content variants built into the content model. The CMS supports the multi-language workflow, the front end renders the right locale, and the SEO is set up for the multi-region ranking.
Have a project in mind?Let’s scope it together.
Tell us the outcome you need. You get an approach, a rough timeline and next steps within one business day.