Digital experiences: from content to channel

A portal keeping content, queries and blocks in Drupal while presenting a Next.js experience through shared CE delivery.

One portal, different editorial needs

A campaign needs composition freedom. An insight needs clear structure. A listing needs to select published content. Each need keeps its tool and shares the same frontend.

An editorial decision, not a visual dependency

This page has no Canvas tree or template. Title, body and summary use the classic editing form. Drupal CE displays define the full-page and teaser output; React implements both presentations.

What Drupal keeps

Drupal keeps fields, formatters, permissions, translations and view modes. Lupus CE Renderer delivers routed content with metadata; CE API exposes it under /ce-api. Next.js validates the contract and renders known elements.

What you can try

Open this insight and its teaser in Insights. Inspect both responses. React does not rebuild field selection or the View query, although components and interactions remain frontend work.

Explore the explanation and real example