CE API: from route to HTML

A presentation API complementing data APIs and simplifying a recursive renderer.

Request a presentation

GET /ce-api/demo/digital-experience resolves the Drupal route and delivers a page with content and metadata. Elements describe which components to present, not the React code implementing them.

Requesting data serves another goal

JSON:API offers resources, attributes and relationships for consumers to decide how to use. It is useful for applications and other channels. It can coexist with CE; this is not a contest between APIs.

A small explicit renderer

Next.js validates title, content_format, content, metatags and optional blocks. The registry resolves known elements and recursively renders slots. Unknown elements cause explicit errors.

SSR and limits

The server generates HTML; SEO quality needs titles, canonical URLs, languages and indexing policies. The POC does not consume every stack metadata field, redirect or session. Cache and invalidation across Drupal, Next.js and CDN need a dedicated design.

Explore the explanation and real example