Free landing page blocks and sections for marketing sites: heroes, pricing, features, FAQs, testimonials and CTAs for React 19 and Tailwind 4 on one design system, plus page templates, app screens, a design skill and an MCP server for agents.
A modal dialog with title, description, scrolling body and pinned footer buttons; alert mode for destructive choices. Built on Radix Dialog.
A heading and a grid of link cards with thumbnail, title, caption, meta and an optional tag or actions. Catalogue cards, groups with "View all", category and template grids.
Title and description of a catalogue page, with optional breadcrumbs, search field, select labels and filter chips. Presentation only: the site wires search and sort.
Full-width preview of one block or screen: breadcrumbs, title, status badge, viewport toggle, Preview and Code tabs, actions and a framed stage that renders a registered demo by id.
What a template contains: the pages it includes (name and path), the blocks it uses as chips, and a paragraph on how to customise it.
The doc-host primitive.
The doc-page primitive.
A diagram or live demo beside the part tree and part list of a compound component.
A grid of colour swatches with name, hex value and token. The colour foundation specimen. Only hex values paint a swatch.
The component-page customise panel: a stage and its code beside a list of controls (select, toggle, text). The layout is static; the site wires the controls to the code.
Side-by-side do and don't pairs, each with a short rule and an example image.
Named example groups (Variants, Sizes, States, With icon, Composition), each a stage (live demo or image) with optional code beneath.
An install panel: tabs of copyable code (CLI, Manual, Download), an optional "Uses" chip row, short labelled facts and actions. A tab with no code is left out.
Breadcrumbs, title and description, with an optional status badge, install command and result preview (demo or image). Opens a documentation page.
Previous and next cards that close a documentation page, with optional actions (Copy for AI, Edit on GitHub) and a last-updated line. A card with no title is left out.
A framed live stage and its code, with Preview and Code tabs when both are present. The stage is a live demo (demo id) or an image; either part may be left out (code-only SKILL.md, preview-only expected result).
A prompt to copy, with {variables} highlighted. The first action copies the prompt; the others are links (Open in Claude, ChatGPT, v0). An optional result image shows what it produced.
A table of a component API: name, type, default and description. Scrolls sideways in narrow containers.
A titled row of link chips: the blocks a page uses, related components.
A titled table with free columns (tokens, keyboard keys, variables, changelog). A column renders as text, code or badge; the first cell of each row is its header.
One page for a small dog grooming salon (Hartley Dog Grooming, Manchester). It leads with prices by size and coat and how long each takes, then the day from drop-off to pick-up, before and after photos, the groomers, first visit answers and a booking form.
One page for a solo dog walker (Saltbush Dog Walks, Melbourne): suburbs, walks and prices up front, then the free meet and greet, keys, bad weather, sick days and an enquiry form.
Desktop builds side by side: one card per platform with version, what it runs on, size and a download link that names its platform, then the system requirements for each platform as definition lists. Nothing is detected, so every build is always offered.
Get the mobile app: a headline, one to three store buttons (each a link with the store named in text), a QR code with a caption for people on a desktop, and an optional line about requirements. The QR image is a Media slot; the buttons never depend on it.
One page for a small driving school (Kestrel Driving School, Halifax): book a first lesson, lesson and block prices, a road test day package, the path to the test, instructors and pickup areas.
One page for a family dry cleaner (Ferrante Cleaners, East Passyunk, Philadelphia): same-day cut-off up front. Then prices with alterations, ready times, pickup days, answers on stains and damage, and a pickup request form.
Text and Media slots every block renders copy and images through. Outside an editor they render plain elements.
One page for a domestic electrician (Tillotson Electrical, Leeds). The jobs covered and fixed prices come first, then the day rate, registration, landlord safety reports, short answers and a quote form.
A centred icon, heading, text and one action for lists, searches and inboxes with nothing in them yet.
The error-boundary primitive.
A planned-downtime page: a status pill, headline, when we are back, and a short log of timed updates. Centred, calm, no error code. Empty updates hide the log.
A 404, 500 or maintenance page: status code, headline, explanation and two ways out.
A 500-style page for when it is our fault: plain apology, retry and status actions, and a side panel with a copyable reference id for support plus up to three things to try.
A not-found or error page that does not leave people stranded: code, plain explanation, one primary action, and a short list of described places to go next. Left-aligned, two columns when wide.
One page for an independent escape room venue (Tinderlock Escape Rooms, Manchester): three rooms, prices by group size and the booking times. It also covers what happens on arrival, access in plain words and the rules for age, lateness and parties.
One page for a small independent estate agent (Carron Property, Stonehaven, Aberdeenshire). It leads with a free valuation, then the selling fee in plain figures, the steps from valuation to keys, a few current listings, the local team, and how to reach the office.
A page for a one-day conference (Småstad Summit 2027): date and tickets up front, last year in numbers, speakers, the programme, three ticket types, the venue and the practical questions. Bold violet, rounded.
A centred heading over a narrow column of questions, each in its own rounded card that opens on click, and one link at the bottom. Gentler than the ruled list and good for short sets of three to six.
Up to eight questions with their answers always open, laid out in two columns.
Questions organised under named topics (billing, setup, privacy). Each topic is a labelled row with its own accordion beside it. Use when you have more than eight questions.
A heading with a ruled list of questions that open to show the answer: beside the list, stacked above it, or stacked and centred over a narrower list.
A left-aligned header over a hairline, then every question and answer open in its own numbered, bordered card, three to a row on wide containers and one on a phone, and an action row under a second hairline.
Every answer open, set as a table of rows: the question is a heading on the left, the answer beside it on the right, hairlines between. Nothing to click, so it prints and scans well; stacks on narrow containers.
An accordion of questions beside a raised "still stuck?" card with up to three ways to reach a person and one action. For products where the real answer is often a conversation.
Feature rows with copy beside an image, alternating sides. Each row has a title, description and up to four points.
A mixed-size tile grid of up to seven features. Medium and large tiles carry an image, small tiles stay text-only. Pair a large tile with a small one.
A centred heading and line over a bento grid of bordered cards in three rows: a tall picture card beside two icon cards, a wide picture card with a full-width button, then two icon cards beside a tall picture card. Every row stacks on a phone.
A heading with a lead and two actions beside it, then a bento of picture cards: a large card beside a medium card and a solid number tile, and a small card beside a wide card with its picture at the side. On a phone the cards stack in one column.