Efferd is one of the most prolific authors in the catalogue: 115 public components, and several of them are the most-bookmarked example of their kind. If you have assembled a marketing page from community components in the last year, there is a fair chance one of these is in it.
The ones that get taken most
Testimonials Columns is the most-saved testimonial section in the whole catalogue: quotes arranged in columns that drift at different speeds. The testimonial guide covers why the wall shape works when you have volume rather than a famous name.
Zoom Parallax is the cinematic scroll effect where images zoom at different rates, and Wave Path and Dotted Surface are the two background pieces, the second being a field of points that reads as depth without a shader.
The marketing set
This is where the volume is, and it is the reason to know the author's name rather than any single component.
Footer Section and Sticky Footer are two of the shapes in the footer guide. Header 3, Header 2 and Header 1 cover the top of the page, and Banner covers the strip above it.
Logo Cloud 3 is the client-logo strip, Grid Feature Cards is the feature block, and Pricing Table is the plan comparison.
Between them that is most of the nine blocks a landing page is made of, from one author, which is the practical argument for looking at a prolific author's whole set rather than at one component: consistency for free.
The product pieces
Less well known and useful: Navigation Menu, Popover, Dialog, Contact Card, Avatar Uploader with cropping, and Gradient Dots.
The avatar uploader is worth singling out, because cropping is the part most upload components skip and the part that decides whether half your avatars are the corner of a landscape photo, as the avatar guide argues.
What to check, as with any single-author set
The same three things the long-tail guide applies to small registries. Whether the component reads your tokens rather than hardcoding colours. What it pulls in, since the scroll and parallax pieces here use an animation library. And whether the name will collide with a file you already have.
None of that is specific to this author; it is what taking any borrowed component involves, and the checklist is the full pass.
Where else to look
The honest list, because the answer is not always us:
| Source | Best for | Trade-off |
|---|---|---|
| The registry directory | Comparing whole registries rather than authors | Only registries that publish an index |
| One prolific author's set | Consistency across a page for free | One aesthetic, and one person's maintenance |
| shadcn/ui | The primitives underneath any of it | No marketing sections |
| 21st | This set with previews, beside everything nearby | 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 look at an author rather than a registry?
- Because a prolific author gives you consistency for free. Taking a header, a footer, a testimonial wall and a feature block from one person means they share spacing, timing and visual language, which is most of what makes an assembled page not look assembled.
- What are the best-known components in this set?
- Testimonials Columns, which is the most-saved testimonial section in the catalogue, and Zoom Parallax, the cinematic scroll effect where images zoom at different rates. The footer, header and logo-cloud pieces cover a large part of a marketing page on their own.
- What should you check before taking a component from one author?
- The same three things as any borrowed component: whether it reads your CSS variables rather than hardcoding colours, what it installs alongside itself, since the scroll and parallax pieces bring an animation library, and whether its file name will collide with something you already have.
- Is a single-author set a design system?
- No. The components share a sensibility rather than a token set, so mixing several into an existing product still needs a pass over radius, spacing and colour. What you get is a much smaller pass than assembling from four sources.