From a good idea
to a considered release.

01 / Give the work a clear destination.

Write the audience, the main task, the required pages, and the material available. Assign ownership for copy, images, review, and technical release. Keep missing information visible rather than replacing it with claims that simply look at home in a template.

The browser design walkthrough is a useful starting point. Its emphasis is a small, coherent website rather than a collection of disconnected design experiments.

02 / Build the structure and test real content.

Choose purposeful content types and reusable components. Populate them with varied examples, including long titles and missing optional fields. Review the reading order and the way repeated items behave across pages.

Keep saving, previewing, and publishing distinct. An editor should know what is private, what is waiting for review, and what has actually been verified on the public site.

03 / Approve the exact change.

Review the content and the implementation together. Check claims, links, responsive behavior, and interactive controls. For an AI-assisted workflow, make the change proposal specific and keep production publication behind a separate approval decision.

Preserve a known-good release before significant changes. A short decision record and a recoverable version give the next reviewer useful context instead of a confusing collection of files named final.

04 / Verify the delivered files.

Serve the export over HTTP, test deep routes directly, and inspect metadata, images, sitemap, and feed. Check the deployment’s actual response to missing pages. The publishing guide covers the handoff; the SEO checklist covers the connected content signals.