gtmesh publish

Moves one or more pages from review (or ready) to published.

gtmesh publish <slugs…>       # mark reviewed pages as live

What it does

gtmesh publish is the last deliberate human move in the authoring lifecycle. A page reaches review once it’s sealed (schema-valid and lint-clean); after the human PR review, publish flips its status to published.

It sets status only — it builds nothing and rewrites no body. A page with only image briefs (art-direction stubs, no real image files yet) publishes fine: the briefs are schema-valid and your site renders placeholders. Generate the real images whenever you’re ready.

Arguments & flags

There are no command-specific flags. The global options (--project, --json, --quiet) apply.

Reads & writes

• Consumes: the named rows’ current status in the registry.
• Produces: an updated status (published) on each named row.
• Commits: the registry change — this is a writer of state, and the result belongs in your next commit.

Examples

gtmesh publish /glossary/water-pump
gtmesh publish /apps/slack /apps/notion   # several at once

Related

• Writer & quality gate — how a page earns review.
• Lifecycle & reconcile — the full status path.
• Create walkthrough — seal, then publish.