Homepage Quality Review

A homepage quality review is the pass between “the page works” and “this page is ready to stand for the site.”

Use it when the homepage has changed enough that build success is not the real question anymore. The review asks whether a reader can understand the site, choose a useful path, and trust that the page is intentional.

When To Use This

Use this workflow after a homepage copy, layout, navigation, or card-grid change.

Do not use it for a tiny typo fix unless the typo changes the page promise or a major route label.

The Review Path

1. Start with the page promise.

   • What should a first-time reader understand?
   • What should they be able to choose next?

2. Check the first screen.

   • The headline should say what this site is for.
   • The first actions should match the strongest reader paths.

3. Check the route map.

   • Primary paths should not compete with support paths.
   • Similar cards should not repeat the same promise in different words.

4. Check the lower page.

   • Generated sections should earn their space.
   • Article, project, tag, and explore blocks should not duplicate each other.

5. Capture proof.

   • Build preview.
   • Check the route.
   • Capture desktop and mobile screenshots.
   • Look at the screenshots, not just the command output.

What Good Looks Like

A good homepage does not explain every part of the site. It gives the reader enough confidence to take the next step.

The page should feel like a public work map: clear paths, real examples, and a reason each section belongs.

Where To Go Next

Use Starting a Quality Review when you need the smaller entry point before running the full workflow. Use Preview, Local Production, and Live Site when you need to keep the review surfaces straight.