Website blueprints

Library reference

What a blueprint is made of, the page patterns inside them, and the kinds of site the library doesn’t cover yet.

How the library fits together

A website type is made of pages

  1. HomeServicesPricesAboutWebsite type a site patternThe structure of a whole kind of site: which pages, in what order, around which action.
  2. Page patternOne kind of page many sites need, top to bottom.
  3. What happens nextStepTime per stepCost per stepSection a moduleOne part of a page with one job, and the content it needs.

Your brief changes it, and the result is your plan

  1. HomeHomeVariantThe same pattern, changed by a different brief. Not a new pattern.
  2. ProofRegistration+ number, linked to the registerField rulesWhat a kind of business must show, whatever the site looks like. They will add requirements, never change the structure; still being worked out, so not applied here yet.
  3. pages:  home: 8 sections  boiler-repair: …open: 5 questionsYour site plan project IAOne project’s pages and sections, as a file Design and Build read.
What the badges mean
No badge
Built in code and tested. A pattern that also runs as code and has been tested. Two do so far; the rest are reasoned, not built. The line under the name says which part is built.
Untested
Reasoned, not built. Worked out from research and real briefs. No site has been built from it yet, so treat it as reasoning to check, not a tested template.
Not in the library
Came up in real briefs. No pattern yet, and no page.

I need one page that answers… 7

Seven kinds of page that turn up across many sites, drawn as they sit on a phone. Each opens with the question a visitor brings to it.

Not in the library yet 6

These came up in real briefs and aren’t covered. Each says what’s nearest and what research would have to exist first. The drawings show what a future pattern would have to do; none is ready.