Questions

A library of 157 WordPress block patterns, in 168157 finishes between them, written in core blocks only. You copy the markup and paste it into the block editor. There is nothing to install for a layout pattern: no theme, no page builder, no shortcode.

A pattern states no colour and no font of its own. Where it needs a colour it references your theme's own preset, with fallbacks behind it so it can never resolve to nothing. So the same pasted section is navy in one theme and cream in another, in that theme's typeface, at that theme's spacing, without you editing anything.

That is a testable claim rather than a slogan, and we test it: every pattern is rendered in real WordPress in Twenty Twenty-Five and Twenty Twenty-Four and its contrast is measured against the colour the browser actually resolved, not the one we authored.

Yes, and they are labelled Signature. A signature payload states its own palette and looks identical in every theme, which is the right answer for a band that has to be the same on every client site. It is a declared promise, not a slip: the same checkers run over it, they just branch on what it declared. Everything else is Adaptive and inherits.

A complete second markup file for the same pattern, in a different finish: a darker colourway, a tighter layout, a version with motion. You copy the variation instead of the base, never as well as it. Each one is a real file that goes through every check, which is why they can be trusted rather than generated on the fly.

Whatever block theme you like, or one you build here in a few minutes. The theme tool is free to use and needs no account: set 8 colour roles, pick two families out of 13, set one spacing step, and see a block theme WordPress installs. It runs the same contrast audit we run over the patterns, and it will not build the theme until every colour pair passes, so a theme it gives you is one every pattern in the library is legible in. Downloading the theme is part of the subscription, like copying a paid pattern.

Switching a theme on there also re-skins every preview on this site, so you can read the whole catalogue in your own design system before you buy anything. Your theme is kept in your browser; a free account keeps 1 in the cloud, a subscription keeps up to 50.

A whole page: 13 of them, each an ordered run of patterns that already ship. The page is the concatenation of those exact files, so lifting one section out of a template gives you byte for byte what that pattern's own page would give you.

Copy the markup from the pattern's page. In the WordPress editor, click into the content area and paste. The blocks appear as ordinary, fully editable core blocks: change the words, swap the images, delete a column. Nothing is locked.

6.7 to 7.0. Every pattern is parsed and rendered on both ends of that range before it ships, because block markup that is valid in one version can be marked invalid in another and WordPress says nothing about it until a buyer opens the editor.

With any block theme that defines the standard WordPress colour presets, which is what a block theme's theme.json is for. The patterns use fallback chains, so a theme missing a preset we hoped for lands on a core default rather than on nothing.

Requires a block theme on WordPress 6.7 to 7.0. Classic themes and page builders are not supported: a pattern takes its colours, spacing and type from the theme's theme.json, which is the file a classic theme does not have.

No, and that is deliberate. Image blocks arrive empty, exactly as the editor writes them before you pick a file, so you point them at your own media library. The photographs in the previews are ours to show the patterns with, not yours to ship.

It adds markup and nothing else. No pattern ships JavaScript, a stylesheet or a webfont, in any finish. There is no runtime to load and nothing to enqueue.

Yes, on unlimited sites, yours or clients'. What you cannot do is redistribute the patterns themselves inside a theme, template or kit you sell. The terms set the line out.

No pattern currently needs it.

Everything else is copy and paste. The plugin is not sold separately: it comes with catalogue access, and it is the same access that unlocks the patterns.

The section loses its wrapper and its motion. The content inside stays on the page as a plain stack: your headings, your text and your images, still readable, still in the right order. Nothing you typed lives inside a plugin attribute, which is why it survives.

We check that by rendering every such pattern with the plugin deleted from the filesystem and holding what is left to the same contrast and responsive floors as any other pattern.

A block's contract is frozen from the day it ships: its name, its settings, its slots. A fix to how it renders reaches every page you have published, which is the entire reason behaviour lives in a plugin instead of in pasted markup. A redesign that would change the contract ships as a new block, never as an edit to the one in your posts.

One subscription, £50 a year (save £94), or £12 a month, which is our launch pricing. It covers every pattern and variation, every page template and every theme download, plus whatever ships next. Cancel any time; access runs to the end of the period you have paid for, and there is no pro-rata refund. Expiry never changes a page you already built.

Nothing. A pattern you pasted is content in your own database; expiry never changes a rendered page and there is no term that lets us reach one. What you lose is this site: no new patterns, no copying the ones you have not taken yet.

Yes: 6 patterns, complete and unredacted, with the fallback chains left in so you can read how the portability is actually done. It is the worked example, not a teaser.

Every pattern page carries a live preview: not a screenshot, but the HTML WordPress itself rendered, in a frame you can resize to see it reflow at tablet and phone widths. The caption names the theme, its typeface and its background colour, so you can see whose design system you are looking at.

It is rendered in real WordPress on both supported versions and in Twenty Twenty-Five and Twenty Twenty-Four, and then measured: every colour pair for contrast against the resolved value, every width for overflow and tap targets, every block through WordPress's own parser for validity, and the whole page for silent notices.

Reading block markup cannot tell you whether it works. Every way this can fail in WordPress fails silently: no warning, no console message, nothing in the editor. So we render the page and read the computed style.

Because a custom block is a dependency you inherit. Core blocks are in every WordPress, they are maintained by the project, they survive our disappearance, and a client editing the page a year later sees controls they already know.

22: navigation, heroes, features, pricing, FAQs, footers and the rest. The library is browsed by section, and each pattern belongs to exactly one.

Tell us at [email protected] and include the pattern, your WordPress version and your theme. A pattern that does not render the way its own preview shows is our bug and we will fix it.

No. We support the patterns rendering correctly in a standards-following block theme. Adapting your site's design, debugging other plugins or building pages for you is not something we take on.