Measured entry
tailark-mist-features-2
A static responsive feature section with a heading, supporting copy, and a compact grid of placeholder cards. It ships as a shadcn registry block, uses Tailwind utility and theme classes, imports Card through the usual component alias, and expects Tailark's Card variant with soft styling.



Measured
Every value below was written by the harness on the run that produced the frames above. None of it is derived from the prose.
| Build | OK |
|---|---|
| Mount | OK |
| Console errors | 0 |
| Uncaught page errors | 0 |
| Horizontal overflow | clean at 375, 768, 1440 |
| Axe critical | 0 |
| Axe serious | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 30.4 KB (95.8 KB build, 65.4 KB baseline) |
| Bare mode | FAIL |
| Provider required | NO |
| Demo used | written from the component source API |
What the harness recorded
BARE BUILD
✗ Build failed in 965ms error during build: [vite]: Rollup failed to resolve import "class-variance-authority" from "<sandbox>re-3d94ac6a90a0/src/components/ui/card.tsx".
Verdict
Do not adopt it unchanged: the registry dependency for Tailark's Card resolves to an HTTP not-found response, so installation stops before compilation. It needs a shadcn-style setup plus a repaired or locally supplied Card component. Teams seeking a drop-in block should avoid it for now.
Use it if
- You want a restrained feature grid whose placeholder panels can be replaced with product visuals.
- Your project already uses shadcn conventions and can provide Tailark's Card API.
- You are comfortable replacing the generic task-management copy before release.
Skip it if
- You need a registry item that installs and builds without repairing a dependency reference.
- Your design system has no Card variant equivalent to the expected soft treatment.
- You need interactive demos, links, or detailed feature illustrations out of the box.
- You cannot accommodate Tailwind theme tokens and path aliases.
Install
| Declared dependencies | clsx, tailwind-merge |
|---|---|
| Missing on install | none |
| Bare install | fails once the shadcn-style helpers are removed, so it needs that setup |
| Provider | no provider required in the harness |
In a non-shadcn project, add Tailwind with matching foreground, muted, and card theme tokens; configure the component path alias; and provide a Card component that accepts the expected soft variant. Because the referenced Tailark registry item is unavailable, supply that Card locally or correct the registry source before installing.
Source and credit
This page is a review, not a copy. The component source lives with its author and this site does not republish it. Read the license before you use anything.
Author repository
github.com/tailark/blocksAlternatives
Other published entries for the feature-grid pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- hyperui-feature-grids-3editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.7KB
- Bare
- pass
- Prov
- NO
- hyperui-feature-grids-1editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- hyperui-feature-grids-4editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- hyperui-feature-grids-2editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 18.3KB
- Bare
- pass
- Prov
- NO
- meraki-feature-grid-list-with-imageminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 18.5KB
- Bare
- pass
- Prov
- NO
- meraki-feature-simpleminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 20.2KB
- Bare
- pass
- Prov
- NO