R14Show the product working
Pro

Build to publish loop

Show create, revise, integrate and publish as one continuous loop that ends in something live.

Back to page recipes

Section sequence

6sections, in the order the visitor meets them. Bar height is the section's weight in the page.

  1. DemonstrateCreate state
  2. DemonstrateRevise state
  3. ProveIntegration bridge
  4. ProvePublished output
  5. NavigateShipped-work gallery
  6. ConvertStart the loop

How the page argues

  1. 1

    Start inside creation, at the moment something first exists.

  2. 2

    Show revision as a normal, repeated act rather than a rescue.

  3. 3

    Show the bridge out: repository, integration, existing stack.

  4. 4

    Show the published result at a real address, owned by the visitor.

  5. 5

    Close the loop by returning from published output to the next revision.

What each section has to be

DemonstrateCreate state
The first working version appearing, with its input visible next to it.
DemonstrateRevise state
The same artifact after a change, showing that iteration is cheap and non-destructive.
ProveIntegration bridge
Repository, framework or stack connection — the proof that output escapes the tool.
ProvePublished output
A live URL or shipped artifact, with ownership, domain and hosting stated.
NavigateShipped-work gallery
Other published results, proving the loop closes for people who are not the vendor.
ConvertStart the loop
Entry into creation, with the publish destination already named.

Is this the right sequence?

Who it is for

Builders who have been burned by tools that produce impressive drafts and no shippable output.

Products it suits

Developer and creative builders whose work is expected to end in a live, owned artifact.

Not for

Products that end at analysis or recommendation, where 'publish' would be a promise they cannot keep.

Evidence strategy

Which proof modes carry the page, in the order they land.

  1. Primary: a live published artifact, which is the only proof that matters here.
  2. Secondary: the revise state, which shows iteration does not mean starting over.
  3. Tertiary: the integration bridge, which shows the output is portable and owned.

CTA plan

What the page asks for, what it offers instead, and where.

Primary
Create and publish something
Secondary
Connect a repository, or browse shipped work
Placement
Primary action after the published output; the repository route sits beside the integration bridge.

Responsive behavior

What the sequence has to do when the viewport stops cooperating.

  • The loop diagram becomes a vertical sequence with the return arrow preserved, not dropped.
  • Create and revise states stack with the change highlighted rather than shown side by side.
  • The published output shows a real, tappable URL rather than a browser-chrome mockup.

Anti-patterns

The failure modes that make this sequence stop working.

  • A loop that ends at export, when the visitor's question was whether it goes live.
  • Published examples that are all first-party.
  • Iteration shown as a full regeneration, which tells builders their edits will be lost.
  • Hiding hosting, domain and ownership terms until after signup.

Build spec

Pro

What an agent needs in order to build Build to publish loop: what each section must contain, the copy rule that keeps it honest, the slots to resolve from your product, and the order to build in.

Checking access to the build spec

Agent tags

The vocabulary an agent matches this recipe on.

  • build-publish-loop
  • revise-state
  • repo-bridge
  • live-output
  • shipped-gallery