Measured entry
tailark-dusk-call-to-action-1
A centered React call-to-action section with a headline and paired primary and outline links. It ships as a shadcn registry block for Next.js, uses Tailwind utility classes and next/link, and expects Tailark's dusk Button component through the usual component alias.



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 | 50.0 KB (115.4 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 764ms error during build: [vite]: Rollup failed to resolve import "@radix-ui/react-slot" from "<sandbox>re-380553ee100d/src/components/ui/button.tsx".
Verdict
The structure is useful and easy to adapt, but the build fails because the referenced dusk Button registry endpoint is not found. It needs a shadcn-style setup plus a locally supplied or corrected Button dependency. Teams needing a drop-in install should avoid it for now.
Use it if
- You want a compact closing call to action with two clearly ranked destinations.
- Your app already uses Next.js, Tailwind CSS, and shadcn-style component aliases.
- You can supply or repair the matching dusk Button component locally.
Skip it if
- You need a registry block that installs and builds without intervention today.
- Your project does not use Next.js and you do not want to replace its Link component.
- Your design system lacks a Button API with asChild, size, and outline variant support.
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 |
Add Tailwind CSS, configure the component import alias, provide a compatible Button with asChild and variant support, and use Next.js Link or replace it with your router's link component. The missing Tailark Button registry reference must also be corrected or implemented locally.
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