Website planning

Shape a runable website from your first idea

A runable website starts with a clear purpose, an audience and one action you want visitors to take. Use this guide to turn those decisions into a useful brief, then evaluate whatever the next tool produces.

Review the destination before continuing
Runable landing-page visual

Three decisions behind a useful site concept

A brief-first approach defines the job of each page before styling it. A visual-first approach can reveal a direction quickly, but still needs the same content decisions.

1

Starting point

Brief-first planning

Write down the audience and their main task.

Visual-first planning

Collect visual references and identify the intended mood.

2

Page purpose

Brief-first planning

Give each page one primary job.

Visual-first planning

Check that an attractive layout still makes its job obvious.

3

Content

Brief-first planning

Draft the essential facts and calls to action.

Visual-first planning

Replace sample copy with specific, verified information.

4

Navigation

Brief-first planning

Group pages around what visitors need to find.

Visual-first planning

Test whether the proposed menu matches those needs.

5

Imagery

Brief-first planning

List the images the message requires.

Visual-first planning

Check whether chosen images accurately represent the subject.

6

Final check

Brief-first planning

Review the structure against the original goal.

Visual-first planning

Review the visual concept against real content and accessibility needs.

Make the message, structure and visuals work together

These three parts are easier to judge separately before deciding whether a complete concept is ready to use.

Illustrative Runable feature visual Message

1

Start with the visitor's question

Describe who is arriving, what they need to know and what they should do next. For a service business, that might mean stating the service area before asking for an inquiry. A polished opening section cannot compensate for an unclear offer.

  • Name the audience and the offer.
  • Choose one primary action for the page.
Illustrative Runable feature scene Structure

2

Give every page a distinct job

A runable website concept is easier to assess when its proposed pages have specific purposes. An overview can introduce the offer, a detail page can answer practical questions and a contact page can make the next step visible. Remove pages that repeat information without helping visitors decide.

  • Keep navigation labels familiar.
  • Put essential details where visitors expect them.
Illustrative Runable feature composition Visual review

3

Treat visuals as a draft, not proof

Imagery and layout can help communicate a direction, but they do not verify business facts or guarantee that a site will work on every device. Check contrast, readable text and whether any pictured product or location matches reality before adopting a design.

  • Replace misleading placeholder imagery.
  • Inspect the layout at narrow and wide widths.

Work through the site idea step by step

  1. 1

    Write a focused brief

    State the audience, the offer and the primary action. Add only the pages and facts needed to support that action; keep uncertain claims out of the brief.

  2. 2

    Explore a direction

    Use the brief to explore an approach, then compare any resulting concept with your stated goals. Note missing information rather than assuming a layout has supplied it.

  3. 3

    Review before publishing

    Verify copy, links and contact details. Test navigation, legibility and mobile layouts, and arrange any hosting or publishing steps separately.

Know the limits before relying on a concept

This page is a planning guide, not a guarantee that the linked destination will build or publish a finished site.

  • No verified publishing workflow

    The available information does not establish that following this route will provide a domain, hosting or a live website.

    WorkaroundConfirm the destination's current capabilities and arrange publishing separately if needed.

  • No automatic fact-checking

    A proposed page may contain generic wording, omissions or details that do not apply to your business.

    WorkaroundVerify every factual claim, address, image and contact method before use.

  • No substitute for device testing

    A visual direction alone cannot confirm keyboard access, readable contrast or responsive behavior.

    WorkaroundTest the finished implementation on relevant devices and with accessibility checks.

Take your brief to the next step

Explore your site idea with a clearer brief

Bring the audience, offer and primary action you identified here. Check what the destination supports, and review any result as a starting point rather than a finished publication.

Explore my site idea
  • Lead with a specific audience and goal
  • Verify details before using any draft
  • Confirm publishing options at the destination

Questions about the Runable website

Write down who the site is for, what it offers and the main action visitors should take. Gather accurate business details and any images you have permission to use. That gives you a concrete basis for judging a proposed concept.

No. This page offers planning guidance and a link to another destination; it does not host or publish a site. Check that destination for its current capabilities before relying on a publishing workflow.

Start with the visitor's task: can someone identify the offer, find essential details and see the next action? Then check the navigation, factual accuracy, legibility and behavior on a narrow screen. Attractive imagery is useful only when it supports those basics.

Do not assume so. Review its wording, images, links and contact information against your real requirements. A developer or site editor may still need to implement, test and publish the final version.

Start creating
Start creating