Service
Headless & decoupled Drupal
Drupal as the back end with React or Next.js on the front, over JSON:API or GraphQL. We build this when the front end has a real reason to be separate, and editor preview keeps working when we do.
Headless buys you a free front-end runtime and charges you a moving part between content and page. We recommend it when the front end earns that trade: a real application, several consumers off one content model, a team that owns the UI. When we do build it, editor parity comes first, so live preview works, URLs resolve, and draft content renders exactly as it will publish.
Scope
How the work is delivered
-
Fit assessment
Before any decoupling we check whether you actually need it: a front-end team, multiple consumers, a UI that out-paces Drupal's theme layer. If a fast, well-built Drupal front end wins that comparison, we say so and build that instead.
-
Content API
JSON:API or GraphQL, modeled deliberately rather than dumping the whole entity graph over HTTP. Versioned response shapes, sane includes, and pagination and filtering the front end can actually cache.
-
Editor parity & preview
Live preview from the front end against unpublished revisions, real path aliases resolved through the API, and media and embeds that render the same in the CMS and on the page. Editors never guess what they are publishing.
-
Front-end build (Next.js / Gatsby)
We build the consuming app too, SSR/ISR or static depending on traffic and how fresh the content has to be, with the Drupal client, routing and revalidation wired in. One team on both sides of the API.
-
Caching & delivery
CDN strategy for both the API and the rendered front end, on-demand revalidation when content changes, an image pipeline, and Core Web Vitals tuned to pass on the page types that matter.
Talk through the build
Send the platform, constraints, and timeline. We'll reply with the engineering questions that decide scope.
- Reply within one business day, weekday hours UA / EU.
- 30-minute discovery call when it is useful.
- Scope written around deliverables, risks, and ownership.