An agency or studio website: a hero over an image, a grid of work, process steps, a featured quote and the team.
An agency or studio website: a hero over an image, a grid of work, process steps, a featured quote and the team.
An announcement bar at the top of the page that people can dismiss. It is a named landmark, and it is announced to screen readers only if you turn that on.
Feature tiles in mixed sizes. Tiles are placed in the order you give, so reading order matches what you see.
The bento grid, with tiles appearing one after another.
A grid of linked cards for blog posts, changelog entries or case studies. Dates are marked up so that software can read them.
The card list, with cards appearing one after another as you scroll to it.
A list of releases. Each has a version, a date and its changes, labelled Added, Changed, Fixed, Removed, Deprecated or Security. Every release is its own article with a heading and an anchor.
A complete changelog page built from Facade UI sections: a header, the releases with their changes, and an optional email sign-up. You supply one content object.
A contact form built from Input, Select and Textarea, with your contact details beside it. It checks required fields, shows errors from your server on the right field, and announces the result. It makes no network call itself.
A closing call to action band. Choose a muted, card, plain or primary-coloured background.
The CTA band, appearing as you scroll to it.
A documentation page built from Facade UI sections: top navigation, side navigation, the article, an 'On this page' list and previous and next links. You supply one content object and the article body.
A FAQ section: questions and answers built on Base UI's Accordion. Each question is a button inside a heading, browser search finds text in closed answers, and you can add FAQPage structured data.
The FAQ accordion, with rows appearing as you scroll to them. The open and close animation works without JavaScript.
A features section: a grid of feature cards, two to four per row. A whole card can be a link while its accessible name stays short.
The feature grid, with cards appearing one after another.
Rows of media and text that alternate sides. Only the layout alternates: in reading order, the text always comes first.
The feature rows, each appearing as you scroll to it.
Features shown in tabs, built on Base UI. A tab opens when you press Enter, not when you move to it with the arrow keys.
A site footer with link groups in columns, a brand area, social links and a legal line. Each link group is a separately named navigation landmark.
A centred landing page hero: eyebrow, headline, text and buttons, with optional media below.
The centred hero, with its parts appearing one after another when the page loads.
A landing page hero with text on one side and media on the other. The text comes first in reading order on every screen size.
The split hero, with its parts appearing one after another when the page loads.
Showing 1–24 of 47