Measured entry
tailark-mist-call-to-action-1
A centered Tailark call-to-action block with a heading and paired primary and outline links. It ships as a registry TSX component for Next.js, uses Tailwind utility classes, imports Next Link, and expects Tailark's Mist Button through a shadcn registry dependency.



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 | 49.8 KB (115.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
BARE BUILD
✗ Build failed in 1.25s error during build: [vite]: Rollup failed to resolve import "@radix-ui/react-slot" from "<sandbox>re-6ef4a8428c26/src/components/ui/button.tsx".
Verdict
Do not adopt it from the published registry in its current state: installation fails because the referenced Mist Button URL returns not found. It also needs a shadcn-style setup. The source is simple enough to adapt manually once you provide an equivalent Button component.
Use it if
- You already use Next.js, Tailwind, shadcn registry conventions, and can resolve the Tailark Mist Button dependency.
- You need a compact centered CTA with primary and secondary actions and are willing to replace the placeholder copy and links.
Skip it if
- You need an installable registry block today, because its Mist Button dependency resolves to a missing registry URL and the build cannot begin.
- Your app is not based on Next.js or does not use Tailwind utility classes.
- You want a CTA with supporting copy, imagery, forms, or more complex conversion content.
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 path aliases, Tailwind theme utilities, a Button supporting child composition, size and outline variants, and Next.js Link or a router-link replacement. Until the registry reference is repaired, copy the block and wire that local Button manually.
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 cta pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- meraki-cta-simpleminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 17.7KB
- Bare
- pass
- Prov
- NO
- hyperui-ctas-4editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.8KB
- Bare
- pass
- Prov
- NO
- meraki-cta-gridminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 17.8KB
- Bare
- pass
- Prov
- NO
- meraki-cta-formminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- hyperui-ctas-2editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 18.0KB
- Bare
- pass
- Prov
- NO
- meraki-cta-cardminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 18.0KB
- Bare
- pass
- Prov
- NO