CMS and domain content

← Back to concept

Content integration has an owner

infrastructure/c_cms owns reusable CMS adapters, transport and content registration. A domain-specific plugin belongs to its domain, together with its model, serializer and tests. An interface does not lose its domain owner by becoming editable in CMS.

The application composition root connects domain content to the CMS registry. Plugin identifiers and serializer fields are explicit frontend/backend contracts. Local media paths stay relative to the configured media origin.

Drafts and published content have separate access rules. Publishing is an explicit editorial action. Unique templates may declare no placeholders; other templates expose only the supported components.

Public page rendering preserves missing-page and infrastructure-error semantics. Static delivery requires an explicit rebuild after publishing; server rendering reads the published page at request time.