An Editorial Release Checklist

Publishing begins before the button

An article is not only its paragraphs. Its title, URL, summary, language, dates, links, images, alternate version, and cache state all shape what readers and machines understand. A release checklist turns that invisible surface into deliberate editorial work.

Content pass

• The opening states the actual question or promise.
• Every heading describes the section below it.
• Important terms use consistent names.
• Claims are supported without pretending uncertainty has vanished.
• Code examples can be copied without hidden prerequisites.
• The ending gives the reader a conclusion or next action.
• Internal notes and placeholder copy have been removed. Read the body once without editing. If the central argument cannot be repeated in one or two sentences afterward, the structure may still be serving the writing process rather than the reader.

Metadata pass

Field	Check	Failure prevented
Slug	Stable, lowercase, and shared across translations	Broken canonical paths
Summary	Useful outside the article page	Empty listings and weak metadata
Language	Matches the actual body	Incorrect locale routing
Origin Language	Matches the author’s original draft	Confusing writing views
Published At	Set intentionally	Accidental ordering
Status	Changed only after the full pass	Partial public pages

Presentation pass

• Links have meaningful text and valid destinations.
• Images have useful alternative text.
• Tables remain understandable on a narrow screen.
• Heading order is logical.
• Light and dark themes are reviewed.
• The page can be navigated with a keyboard.
• Code blocks scroll without pushing the viewport wider.
• Details and callouts remain readable in both themes. The W3C Web Accessibility Initiative provides deeper guidance; this list is only a release gate.

Translation pass

1. Confirm the second page has exactly the same Slug.
2. Review title and summary as independent writing.
3. Check code, proper nouns, dates, and links for locale assumptions.
4. Connect reciprocal Other Version relations.
5. Verify that an unpublished translation returns a real 404.
6. Publish each language only when its own body is ready.

---

Rollback plan

If a published article has broken or unsupported content, return that locale page to Draft rather than replacing it with another language. Preserve the page and its relation so the correction can be reviewed before republishing. Record whether a cache purge is also required.

A good checklist makes publishing calmer. It does not guarantee perfection; it makes the next failure easier to locate and correct.