Meridian

The library

Fifty starting points. Pick the shape, not the colour.

Each one is a real page, not a picture of a page. What you are choosing is the structure: which sections exist, in what order, and where the thing you want a visitor to do sits. The colours, the images and every word will be yours.

These are designs, not case studies

None of them is a site we built for a client. They are the starting points we build from, shown so you can choose one before you pay rather than after.
Designs
50
Families
8
Sections used
509
Colourways each
3

01

Single-page conversion launch

A single page built around one countable action. Right when a business has one offer, one campaign or one launch date, and wrong the moment it needs to explain more than one thing.

What every one of these shares

One route, no content management, no sign-in and nothing stored on a server we own. Navigation is anchor scrolling within the page. There is exactly one form, or one tracked outbound click, posting to the client's own mailing or CRM webhook. Analytics and conversion pixels are consent-gated. Hosted as static files on a CDN against a sub-one-second largest-contentful-paint budget. Every member ships the same component kit and differs only in copy, imagery and the type and colour tokens.

02

Local service brochure

The whole of a local business, explained across a handful of pages, for somebody comparing three names they found on a map and deciding which one to ring.

What every one of these shares

Five to eight static routes generated from one template set: home, about, services index, three to six service detail pages, service area, reviews and contact. Every member ships the same integrations - a quote form posting to email and to a CRM webhook, click-to-call and tap-to-map on mobile, an embedded map, a third-party review widget reading from Google or Trustpilot, LocalBusiness and Service structured data, and a per-town page generator for local search. No login, and the site itself stores no records.

03

Editorial and authority publication

For a business whose authority is its published work. The site exists to be added to every week, so the client edits it themselves, and the whole structure is built around one collection of articles that keeps growing after we have gone.

What every one of these shares

One long-lived content collection driven by a CMS the client edits, plus its taxonomy of categories, tags and author profiles, rendered statically and rebuilt on publish. Every member ships the same integrations: a client-side search index, newsletter capture handed to a mailing tool with double opt-in, RSS, sitemap and Article structured data, share and preview metadata, sponsor and partner slots, and at most one embedded third-party donation or subscribe widget that stores nothing here. No visitor accounts and no comment system owned by the site.

04

Visual portfolio and case study

For businesses whose work is the argument. The visitor is persuaded by looking, so the page is mostly pictures at full size, and everything else exists to get them from the last one into the enquiry form.

What every one of these shares

An owner-editable collection of media-heavy items - projects, shoots, builds, works - all rendered through one detail template, plus a responsive image pipeline with AVIF and WebP and blur-up placeholders, lightbox galleries, embedded video, a filterable category grid, and a single enquiry form. Optional host-level password protection on individual gallery routes. No visitor accounts, and nothing stored on behalf of a visitor. Members differ in grid density, type scale and motion character, not in code.

05

Booking and scheduling

Seven businesses whose website is the diary. A visitor picks a real slot against real availability, the slot is held, and the staff see it in the console they already watch. Everything else on the page exists to move somebody to that calendar with enough confidence to commit to a date.

What every one of these shares

The site owns the booking data. One schema across every member: resources (staff, chairs, rooms, tables, class slots), services carrying a duration and a price, availability rules with blackout dates, booking records and customer records. One integration set: card deposits and no-show fees, two-way Google and Outlook calendar sync, SMS and email reminders, self-serve cancel and reschedule links, a staff admin console, timezone and locale handling, and consent or intake capture attached to the booking.

06

Transactional e-commerce storefront

Six shops that sell very different things and are built on one commerce engine. Choosing between them is choosing what a visitor has to be told before they will buy: a size chart, a roast date, an ingredient list, a delivery lead time, a ring size, or a licence number.

What every one of these shares

Product catalogue with variants, stock levels and media; cart and checkout on Stripe or Shopify; tax and shipping rules by zone; customer accounts with order history; transactional order and fulfilment email; discount codes; a returns request route; a product feed for Google and Meta shopping; abandoned-basket recovery. Every member is that same engine at a different merchandising density, wearing different tokens.

07

Membership and gated access

Sites where paying changes what the page shows. The public pages sell entry, and everything past the door is stored, tracked and billed again next month, which is why this family is quoted rather than priced.

What every one of these shares

Email and social sign-in with roles; recurring subscription billing through Stripe Billing with an entitlement check on every gated route; a content library of video, lessons and files with per-user progress and bookmarks; a member profile; lifecycle email covering welcome, failed payment, renewal and win-back; an admin publishing console; and signed-URL video hosting through Mux or Vimeo. Whether a given item is free or paid is a configuration flag, not a rebuild.

08

Searchable listings directory

For businesses whose value is other people's records made findable. A visitor arrives to locate one listing among thousands, and the money is in the enquiry that reaches its owner.

What every one of these shares

Typed listing records with faceted search and a geographic query; listing owners who submit and edit through a moderation queue; featured and paid placement billed on Stripe; saved searches with email alerts; a lead routed from a listing page to whoever owns that listing; one indexable page per listing with a partitioned sitemap; and an import pipeline for third-party feeds.

The design library - Meridian