Headless CMS

In a headless architecture the editorial back-end is responsible only for storing and serving content — the presentation layer is decoupled entirely. Front-end teams choose any framework (Next.js, Nuxt, Astro, native mobile) and fetch content through APIs on their own schedule.

Ibexa DXP can operate in full headless mode via its REST API and GraphQL endpoint, or in hybrid mode where the Page Builder still renders pages server-side while other channels consume the same content headlessly.

Das könnte Sie auch interessieren

API-First Architecture
A design approach where all functionality is exposed via APIs from the start, enabling any front-end or integration to consume content independently of the back-end.
GraphQL
A query language for APIs that lets clients request exactly the data they need. Ibexa DXP ships a fully auto-generated GraphQL schema reflecting your content model.
CDN
A Content Delivery Network caches assets and responses on globally distributed edge nodes, reducing latency for end users regardless of their geographic location.