Drupal Rebuild Separates Data Objects From Editorial Pages

The rebuild of a data-driven Drupal site separates imported data objects from the nodes used as public pages. Ralf Baumbach describes the change in a blog post published 11 September 2026. In the Drupal 7 implementation, the same node served both as a local representation of externally owned data and as the editable page presented to visitors. That became difficult when source-controlled values such as names needed to change independently from titles, publication state, and other editorial decisions in Drupal.

The rebuilt site assigns those responsibilities to separate entities. A custom content entity stores the source object's stable identity, selected properties, and relationships without taking on a useful public URL, editorial publication state, or Layout Builder configuration. A referenced node remains responsible for the public page, including its URL, title, publication state, editorial metadata, and layout. Imports can update source-controlled information without overwriting editorial properties, while provisioning services create missing parent and child pages and shared context resolution supplies blocks with the data objects associated with the current page.

Ralf notes that the model adds code for entity references, context resolution, page provisioning, administration, access, and deletion. He says that complexity may not be justified where every imported object always maps to one page and both share the same lifecycle. In this rebuild, however, the Drupal 7 implementation already needed migration conditions, extra fields, and form alterations to separate source-owned data from Drupal-owned presentation, so distinct entities make that separation explicit.