Publishing Workflow

Start from the source of truth

The safest publish begins by editing the canonical content model, not by improvising ad hoc strings in a random route. This is important because the public page shell depends on structured blocks, not just loose paragraphs.

If you bypass the source model too often, the page may still render, but the system becomes less predictable with every change.

Know what is being published

A public page payload is more than a headline. It may include:

• hero copy

• structured story cards

• long-form chapters

• step-based roadmap content

• library or publication cards

• section blocks

• FAQ entries

• final CTA copy

Publishing a page means publishing that full shape, not just replacing a single sentence and hoping the surrounding structure still makes sense.

Use an explicit synchronization step

Once the source content is updated, synchronize it into the live page store. A synchronization step matters because the public routes read from persisted content, not only from default code values.

That separation is useful. It gives the product a stable live store, but it also means source edits and live edits are not automatically the same thing until the sync is performed.

Preserve route awareness

Whenever a publish affects documentation, cross-links, or route references, confirm that the page still points to valid destinations. A rich public page often depends on connected routes such as docs articles, AI surfaces, or contact flows.

Broken references make the page feel unfinished even when the copy itself is strong.

Verify after publish

A minimum verification pass should include:

• loading the public route on the live domain

• checking that the new narrative blocks render in the right order

• confirming key links resolve correctly

• reviewing any route-specific examples or code snippets for correctness

• spot-checking protected update paths if the change touched publishing logic

The habit matters more than the ceremony. The goal is to catch mismatch while the context is still fresh.

When to use admin route updates

There are times when a controlled admin route update is the right move, especially for targeted live edits. That path is valid, but it should still be treated as part of a governed publishing workflow rather than a shortcut that replaces the canonical source model.

When the edit affects the durable public narrative, updating the source model and running the sync path is usually the stronger pattern.

The real standard

A strong publishing workflow protects coherence. It keeps the live page, the source content, the documentation, and the team’s shared understanding pointed at the same truth.