Publication is
a change of responsibility.

Check titles, descriptions, image alternatives, and destination links using representative content. Confirm that demonstration entries and private review notes have been removed from material intended for publication.

Name an editor who can approve the content and a route for reporting an error after launch.

Follow the important routes with a keyboard and on a narrow screen. Examine expanded menus, empty views, unavailable content, and links that open another application.

Record the pages and states that were checked. Keep unresolved items visible rather than treating a homepage review as a complete site review.

Identify who controls the domain, hosting environment, content platform, and deployment process. Agree who can publish a change and how the last working version can be restored.

Do not place credentials in a public handover. Access arrangements belong in the appropriate authorized account and documentation.

Define how a new entry is added, how a correction is made, and how old material is retired. A collection needs a consistent relationship between its published content and the views that refer to it.

A change to a content type can affect browse lists, result pages, and linked entries. Review those surfaces together.

Use the original scope and decision record to assess a proposed change. Consider whether it introduces a new state, a new editorial field, or a new dependency.

Small changes still need context. A label adjustment can alter how a reader interprets a destination, even when the underlying route stays the same.