Field guide

Design pages around reader questions

Plan useful homepages, service pages, and articles with clear questions, evidence, and next steps.

Content updated · Editorial standards

Give each page one primary task

Write a sentence that begins: after reading this page, a visitor can. Finish it with an observable action such as compare two service scopes, find a drawing, or prepare an inquiry. If the sentence needs several unrelated actions, split the material into separate pages and connect them with specific links.

Use a question map before writing

For a service page, collect the questions about fit, inputs, delivery, exclusions, evidence, and contact. Put the broad answer first, then explain the details needed to judge it. For an article, state the problem and prerequisites before the steps. A visitor should not need to reach the final paragraph to discover that the advice applies to a different situation.

Separate facts, examples, and unknowns

A documented capability needs a source, an owner, and enough context to interpret it. A hypothetical example needs a label. An unknown needs a question or a next step. Avoid replacing missing measurements with precise-looking sample results. A simple caption explaining what an image shows can be more useful than a decorative badge.

Make internal links explain the next decision

Link from a broad explanation to the page that answers the next likely question. Prefer a phrase such as compare packaging formats over click here. Keep a short list of genuinely related pages after the main content. Review the destination whenever you change the surrounding wording so the promise and the page still agree.

Review content after layout changes

A new theme can change heading levels, image crops, table widths, and menu labels. Revisit one long page and one short page after each layout change. Check a page without its images and ask whether the remaining text still communicates the main point. Keep important words in text rather than embedding them in a graphic.