Measured entry
tailark-dusk-hero-section-6
A responsive Next.js hero block with an announcement link, split headline and call to action, framed product screenshot, photographic backdrop, site header, and logo cloud. It ships through a shadcn registry and depends on Tailwind theme utilities, Next Image and Link, Lucide icons, a themed Button, plus separate Tailark header and logo-cloud blocks.



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 | flagged at 375, 768 |
| Axe critical | 0 |
| Axe serious | 2 |
| Axe moderate | 2 |
| Axe minor | 0 |
| Gzip marginal | 115.8 KB (181.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 the published block as-is: its themed button dependency resolves to a missing registry resource, so installation stops before build or mount. It needs a shadcn-style setup, and teams unwilling to repair or vendor that dependency should avoid it.
Use it if
- You already use the Tailark Dusk registry and can resolve its shared themed components.
- You want a dark product hero built around a large application screenshot and customer logo strip.
- Your site runs on Next.js and already supports Tailwind theme tokens and path aliases.
Skip it if
- You need a registry block that installs and builds from its published dependency graph today.
- Your project is not based on Next.js or cannot accommodate Next Image and Link.
- You do not want to supply a local product screenshot or configure the remote backdrop image.
- You need a self-contained hero without separately maintained header and logo-cloud components.
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 and the expected color and radius theme tokens, configure the component path alias, install Lucide, and provide equivalents for Button, HeroHeader, and LogoCloud. Use Next.js or replace Image and Link, add the local mail screenshot, and allow or replace the remote image host. The missing Dusk button must be recreated or vendored because the published registry reference does not resolve.
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