MdWrk is a concrete example of treating publishing as an architectural system rather than a theme. The value is not only in page rendering. It is in keeping content contracts, route semantics, discovery output, and deployment surfaces aligned enough to review as one system.
Context
Publishing systems often separate content, rendering, discovery metadata, and deployment state into disconnected tools that are difficult to reason about as one surface.
Constraints
The system must support multiple sites with shared infrastructure.
Content needs typed structure instead of ad hoc blobs.
Discovery artifacts must remain reproducible from the repo.
Architecture
Typed content packs define site-level truth.
React and static generation provide the presentation layer.
Docker and provider-backed desired state keep publication inspectable.
Outcomes
A reusable site substrate for multiple public domains.
Clear separation between content contracts and presentation shells.
Better alignment between writing surfaces and deployment evidence.