Plan a website that stays useful

Give each page a clear responsibility

A homepage introduces the subject and directs the visitor. An About page explains context and point of view. A service page addresses scope and suitability. A contact page helps someone take a realistic next step. These pages should work together without repeating the same introduction in different words.

Make a short inventory before deciding on navigation. For each proposed page, write down its audience, the question it answers and the action that follows. If two pages do the same job, consider whether they belong together. If one page tries to solve several unrelated problems, it may need a clearer structure.

Decide what the editor should control

Editable content is most useful when it reflects real maintenance work. A person who updates opening hours should not have to understand the entire layout system. Equally, adding a new service category may affect navigation, related pages and the overall structure.

List examples of ordinary changes: replacing an image, correcting a description, adding an answer or publishing a dated update. Then identify changes that deserve technical review. This makes the boundaries of the editing experience easier to discuss and test.

Prepare the materials before the layout

Gather the text, images and practical details that are actually available. Check whether each photograph can be used, whether the content is current and whether the person responsible for it is known. Avoid designing a page around evidence that does not exist, such as imagined testimonials or unverified results.

Content does not need to be polished at the first conversation. It does need to be specific enough to reveal the structure. A rough service explanation with genuine scope is more useful than a finished-sounding paragraph that could describe any business.

Keep the mobile reading experience deliberate

A page should retain its meaning when a wide layout becomes a narrow column. The important question is not simply whether the page shrinks. It is whether headings, images, navigation and next steps still appear in a sensible order.

Long comparison tables, dense menus and decorative text over photographs deserve particular attention. Review the page with realistic copy, not only short sample text. The visitor should not have to scroll sideways across the whole page to understand the main content.

Separate information from functionality

A service description is different from an online booking service. A contact page is different from a working enquiry form. An account link is different from a secure account system. Each interactive feature needs an actual destination, appropriate access and a way to check that it works.

Write those dependencies into the brief. State which systems already exist, who controls them and which parts of the journey happen outside the website. Do not assume a visual form is a complete operational process.

Plan the handover

The handover should explain where content lives, who has the necessary access and which changes can be made safely. It should distinguish publishing content from changing technical configuration. A short record of those responsibilities can save repeated guesswork later.

Keep credentials out of ordinary planning documents. A brief can list the accounts or services involved without containing passwords, recovery codes or private customer records. Access can be arranged through the relevant service when needed.

Review the website as a connected experience

Before considering the work finished, follow the main visitor journey. Read the page titles, use the navigation, check links and view important pages at narrow and wide widths. Look at what happens when someone reaches a missing address as well as the homepage.

After launch, repeat the checks when the organisation changes. A technically working page can still contain the wrong information. The content maintenance checklist gives a practical routine for reviewing that content without redesigning the entire website.