DNSLink and custom domains: a safer publishing workflow
Connect a familiar domain to a versioned release while keeping DNS, gateway delivery, and rollback responsibilities separate.
Move reviewed content into an identifiable release. This reading path connects the editor’s content model, the exported artifact, and the controlled domain change that makes a new version public.
Use the cms publishing topic guide for the broader architecture, then follow the articles below into individual decisions and practical exercises. Each guide addresses a different part of the same operating picture.
3 articles tagged Publishing
Connect a familiar domain to a versioned release while keeping DNS, gateway delivery, and rollback responsibilities separate.
Prepare a portable build, identify the release, arrange retention, and test the gateway before changing your public entry point.
Turn editorial content into a complete, reviewed release with portable routes, local media, consistent metadata, and clear publishing authority.