Generated from cat-harness/skills/authoring/content-lifecycle/content-publish.md — do not edit here. Typed contract: schema reference.

✎ Edit this page’s source

Content Publication

Package, version, and publish approved content.

Responsibilities

• Update version numbers (semantic versioning: major.minor.patch)
• Create publication metadata (publication-request.json for FHIR IGs)
• Build final artifacts (IG Publisher build, LaTeX compilation)
• Create release branches and tags
• Create GitHub releases with release notes
• Deploy to publication platform (smart.who.int, arXiv, etc.) — the push is the general render-kg-to-cdn step with the release root as its publication root URL; the target’s Tool (gh-pages for GitHub Pages) carries the platform-specific steps
• Reset development branch to draft status for next cycle

Actors

• Publication Manager (lead)
• Programme Manager (release authorization)

Inputs

• Approved and tested content
• Version increment decision (major/minor/patch)
• Release notes

Outputs

• Published artifacts (IG, PDF, etc.)
• GitHub release with tags
• Publication URL
• Updated version in development branch

Processes that run this skill

process	step(s) that name it
Incremental IG build	Deploy the preview site; Deploy the site [content-publish]
L3 FHIR IG pipeline	Publish the IG site
Authoring a document	9 · Publish
Content Change and Review	Rebuild main site
Content lifecycle	Draft, review and publish (calls a sub-process)
Draft, review and publish	Build the draft publication; Authorise the release; Version, tag and publish
Authoring a paper	9 · Publish