Measured entry
tailark-dusk-hero-section-4
A dark Tailark hero block with a headline, primary and download actions, a mock assistant input, a remote Unsplash image, site header, and logo cloud. It ships as a Next.js component styled with Tailwind utilities and relies on Next Image, Lucide icons, path aliases, plus Tailark's Button, Kbd, header, and logo-cloud registry 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 | 4 |
| Uncaught page errors | 0 |
| Horizontal overflow | clean at 375, 768, 1440 |
| Axe critical | 0 |
| Axe serious | 1 |
| Axe moderate | 2 |
| Axe minor | 0 |
| Gzip marginal | 115.5 KB (180.9 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 this registry item as published. Its Button dependency resolves to a missing shadcn registry URL, so installation stops before build or mount. It needs a shadcn-style setup plus a repaired or local Button mapping. Teams seeking a drop-in block should avoid it.
Use it if
- You already use Next.js, Tailwind, and shadcn-style component aliases.
- You want a dark product hero with an AI prompt motif and supporting customer logos.
- You are prepared to repair or locally replace the unresolved Tailark Button registry item.
Skip it if
- You need a component that installs and builds from the published registry without intervention.
- Your app is not based on Next.js or cannot use the Next Image component.
- You do not want a remote Unsplash asset or several coupled header, logo-cloud, Button, and Kbd components.
- You need verified runtime or accessibility behavior from this harness run.
Install
| Declared dependencies | motion, 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 styling and theme tokens, configure the at-sign component alias, install Lucide and Next.js image support, then supply local Button and Kbd primitives plus the matching header and logo-cloud components. Replace the broken Tailark Button registry reference and allow or self-host the Unsplash image.
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 hero pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- ruixen-tabbed-hero-sectionunclassified
- Renders
- YES
- A11y
- 0
- Gzip
- 50.6KB
- Bare
- fail
- Prov
- NO
- 8bitcn-hero1skeuomorphism
- Renders
- YES
- A11y
- 0
- Gzip
- 51.5KB
- Bare
- fail
- Prov
- NO
- tailark-mist-hero-section-5minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 64.8KB
- Bare
- fail
- Prov
- NO
- tailark-mist-hero-section-6minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 64.8KB
- Bare
- fail
- Prov
- NO
- ruixen-arc-reveal-herounclassified
- Renders
- YES
- A11y
- 0
- Gzip
- 71.6KB
- Bare
- fail
- Prov
- NO
- tripled-cta-hero-block-shadcnuiminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 72.8KB
- Bare
- fail
- Prov
- NO