Measured entry
tailark-mist-features-11
A Next.js feature section pairing a large AI-assistant mockup card with three supporting benefit blurbs. It ships as a shadcn registry block and uses Tailwind utility and container-query classes, next/image, Lucide icons, an external Unsplash asset, and Tailark variants of the shared Card and Button components.



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 | 1 |
| Uncaught page errors | 0 |
| Horizontal overflow | clean at 375, 768, 1440 |
| Axe critical | 0 |
| Axe serious | 2 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 40.3 KB (105.7 KB build, 65.4 KB baseline) |
| Bare mode | FAIL |
| Provider required | NO |
| Demo used | written from the component source API |
What the harness recorded
CONSOLE
Failed to load resource: the server responded with a status of 404 (Not Found)
BARE BUILD
✗ Build failed in 670ms error during build: [vite]: Rollup failed to resolve import "lucide-react" from "<sandbox>re-dd9a172241a9/src/cut/components/features-11.tsx".
Verdict
A polished composition, but it currently fails because the Tailark Button dependency points to a missing registry resource. It needs a shadcn-style setup plus manual dependency repair. Teams seeking a drop-in or framework-neutral block should avoid it until the registry entry is fixed.
Use it if
- You want an editorial feature section with one dominant product illustration and a compact benefit grid.
- Your app already uses Next.js, Tailwind, Lucide, and compatible Tailark Card and Button primitives.
- You are comfortable replacing the supplied marketing copy, mock interface, and remote image.
Skip it if
- You need a registry block that installs and builds without repairing dependency resolution.
- Your project is not based on Next.js or cannot use next/image and remote Unsplash assets.
- Your design system lacks Card and Button variants compatible with the Tailark component API.
- You need a functioning interactive assistant rather than a decorative interface mockup.
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 container-query support, Lucide React, Next.js image handling with the remote image host allowed, and local Card and Button components that implement the soft and outline variants plus icon sizing. Replace the unresolved Tailark registry dependencies with those local primitives.
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