Publishing & Domains
How to think about publishing, domains, and keeping Coherence Sites current after launch.
Publishing in Coherence Sites should feel lightweight enough for fast iteration and reliable enough for pages your team depends on.
Before you publish
Run a quick review pass on:
- page title and description
- primary CTA
- section order
- footer and navigation links
- brand consistency
- mobile readability
If the page came from an import, this is also the moment to clean up anything that feels too generic or out of place.
A simple publishing workflow
For most teams, a good workflow looks like this:
- Draft the page
- Review the copy and structure
- Publish
- Revisit later as the message evolves
The win is not just launch speed. It’s the ability to keep pages current after launch.
Custom domains
Custom domains matter when the site becomes part of your real public surface instead of a temporary preview.
Typical setups include:
- your main marketing site domain
- a blog subdomain
- a docs subdomain
- campaign-specific subdomains
As your Sites setup matures, a good domain workflow should make it easy to:
- connect a domain
- verify DNS
- choose the published destination
- keep environments predictable
Publishing strategy for mixed stacks
If your main marketing site contains highly custom application surfaces, you don’t need to move everything into Sites at once.
A practical rollout often looks like this:
- launch editable landing pages in Sites
- move docs and blog content into Sites or a Sites-backed CMS workflow
- keep heavily custom app pages in the product codebase
That lets you get the operational benefit without forcing a full migration before it makes sense.
Ongoing maintenance
The real value of Sites shows up after launch:
- new campaigns don’t start from zero
- docs don’t get stale as quickly
- blog and resource pages become easier to maintain
- non-engineers can keep the site current
That’s the difference between “a page builder” and a publishing system your team actually uses.