Measured entry
tailark-mist-features-7
A static Next.js feature grid with a wide product screenshot card and smaller meeting, code review, and assistant illustrations. It ships as a shadcn registry block and depends on Tailark Card and Button primitives, Lucide icons, next/image, Tailwind utility styles, local screenshot media, and remote avatar images.



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 | 5 |
| 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 | 41.8 KB (107.2 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)
CONSOLE
Failed to load resource: the server responded with a status of 404 (Not Found)
CONSOLE
Failed to load resource: the server responded with a status of 404 (Not Found)
Verdict
Do not adopt it from the registry as published. Installation fails because the Tailark Button dependency points to a missing registry item, so the block never builds or mounts. Even after repairing that reference, it needs a shadcn-style setup and project-specific image configuration.
Use it if
- You can repair or replace the unavailable Tailark Button registry dependency before installation.
- You need a compact feature section that mixes a product screenshot with decorative interface mockups.
- Your project already supports Next.js image handling and the Tailwind syntax used by the block.
Skip it if
- You need a registry block that installs and builds without repairing upstream references.
- Your stack is not Next.js and you do not want to replace its image component and asset configuration.
- You cannot allow remote avatar requests or provide approved local replacements.
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 |
A non-shadcn project must add compatible Card and Button components with the expected variants, Lucide React, Tailwind utilities and theme tokens, a replacement for Next.js Image or equivalent image handling, the screenshot asset, and remote-image approval or local avatar files. The broken Button registry reference must also be repaired or replaced.
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