HomeIn use
What they look like together
A part on its own page is easy to like. Here are three whole screens made of them, running for real — and a switch that draws a line round every part and tells you which one it is.
Nothing here has been adjusted to fit. Every part is exactly what you would get by copying it out of the catalogue, with its own default content — which is also why the wording jumps about between them.
Screens built from the catalogue
A product page, seven parts deep
Hero, logo wall, split feature, feature grid, comparison, FAQ, sign-up. Every one of them is the part as it comes, with its own default content — nothing here has been restyled to fit.
Hero sectionLogo wallSplit featureFeature gridStat comparisonFAQNewsletter signup
Refit yard, Falmouth
Get your boat ready before the season starts
Rigging, engines, hulls and electronics under one roof. Tell us what it needs and we will send a written quote within two working days.
No deposit until the work is agreed.
Built with
- Next.js
- React
- Tailwind CSS
- TypeScript
- Playwright
- axe
Slide 1 of 6
These are the tools this page is built with, which is a claim about us. A “trusted by” wall is a claim about someone else — only put a name there with their permission.
Test the file you are going to ship
The preview runs the exported code, not a mock-up of it. Change an option and the thing you will copy changes with it.
- The same tests run on the React file and the plain HTML, CSS and JavaScript.
- Keyboard paths and axe checks, with the component open and closed.
- Chromium, WebKit and an emulated iPhone, every time.
What you get
Every part is tested the same way before it goes in the catalogue.
Two outputs
React with Tailwind, or plain HTML, CSS and JavaScript. Both tested, neither a wrapper around the other.
No dependency
You copy the files. There is no package to install and nothing to keep up to date.
Accessible first
Keyboard paths, screen-reader wording and colour contrast are part of the definition of done.
Read more about accessible firstConfigured visually
Set the options on the page, watch the real component change, then take the file.
Dark mode included
Light, dark or the visitor's own setting, in the exported file rather than a separate sheet.
Yours afterwards
Rename it, cut the options you do not need, fold it into your own components.
Slide 1 of 6
| Measure | React + Tailwind | HTML, CSS and JS |
|---|---|---|
| Files to copy | 1Better here | 2 or 3 |
| Runtime dependencies | 0 | 0 |
| Needs a build step | Yes | NoBetter here |
| Tailwind version required | v4 | NoneBetter here |
| Tests run against it | Every one | Every one |
Better depends on the project. This is what differs, not which one you should pick.
Questions
If yours is not here, write to us and we will add it.
Do I need to install anything?
No. You copy the files into your project, or install them by URL through the registry. There is no package to add and nothing to keep updated.
Which Tailwind version does the React output need?
Tailwind v4. The exported file uses v4-only syntax for custom properties, so v3 will not style it correctly.
Can I change the code afterwards?
That is the point. Once the files are in your project they are yours: rename things, delete the options you do not use, fold them into your own components.
What about dark mode?
Every part has a theme option: light, dark, or following the visitor's device. The dark colours are part of the exported file, not a separate stylesheet.
Notes from the yard
What we have been fixing, and what we learnt doing it. Once a month, no more.