prebuiltui is a plain marketing set: hero, features, cards, gallery, breadcrumb. 24 components published here, none of them trying to be memorable, which is a reasonable thing for a component to not be.
The components
Image Gallery is the most-taken one and a straightforward grid, which the gallery guide argues is the layout that never looks broken and the one most projects should ship.
Hero Section, Feature Sections and Cards cover three of the nine landing-page blocks, and Breadcrumb and Cookies are the utility pieces.
The case for plain
Most writing about components is about the memorable ones, which distorts the decision. A landing page needs one section that is meant to be looked at and eight that are meant to be read, and a plain component is the correct choice for the eight.
The practical benefit is that a plain section adapts to your tokens in minutes rather than needing its personality stripped out first. A decorated component brings a point of view about colour, radius and motion, and taking it means either keeping that view or spending the time to remove it - which the customisation guide covers at four levels.
What plain still has to get right
Being unremarkable does not lower the bar, and the checks are the same ones the review checklist applies to anything borrowed.
Does it read your CSS variables, or does it hardcode a grey. Does the hero ship an h1 or an h2, which decides whether your page has a heading at all. Does the gallery set image dimensions, since that is half of a listing page's Core Web Vitals. And is anything marked as a client component that did not need to be, per the server components guide.
A plain component that fails those is worse than a decorated one that passes, because the decorated one at least gave you something in exchange.
Where else to look
The honest list, because the answer is not always us:
| Source | Best for | Trade-off |
|---|---|---|
| shadcn/ui | Primitives, which are the plainest thing there is | No sections |
| A blocks registry | Assembled plain sections in volume | You inherit its layout decisions |
| Tailwind Plus | Conventional sections with the breakpoints solved | Paid, and widely used |
| 21st | Plain sections beside the decorated ones, with previews | Quality varies by author, so preview before you take it |
Taking one
Every component page has a live preview and the code. Installing goes through the shadcn CLI against our registry:
That key comes from your 21st account, and installs require a membership. Set API_KEY_21ST once in your shell and the command works for anything in the catalogue.
Frequently asked
- Why choose a plain section over a decorated one?
- Because a landing page needs one section meant to be looked at and eight meant to be read. A plain section adapts to your tokens in minutes, while a decorated one brings a point of view about colour, radius and motion that you either keep or spend time removing.
- Does a plain component have a lower bar?
- No. Check whether it reads your CSS variables, whether the hero ships an h1 or an h2, whether the gallery sets image dimensions, and whether anything is marked as a client component unnecessarily. A plain component that fails those gave you nothing in exchange.
- What is prebuiltui good for?
- The unremarkable middle of a marketing page: a straightforward image gallery, a hero, feature sections, cards, plus utility pieces like a breadcrumb and a cookie notice. None of it is trying to be memorable, which is the right ambition for most of a page.
- Where do plain sections fit alongside animated registries?
- The layered setup: primitives at the base, plain sections for the parts meant to be read, and one or two decorated components for the section that carries the page's personality. The failure mode is decorating all nine.