vibecodng.com

Free MCP betaIndex and tools live

Measured entry

tailark-dusk-hero-section-2

herodark-futuristic

A dark product hero with a separate site header, a large headline and call to action, a framed application screenshot, and a logo cloud. It ships as a shadcn registry block for Next.js and expects Tailwind styling, Next Link and Image, Tailark's Dusk button, header, and logo-cloud registry components, plus a local mail screenshot asset.

Specimen
Harness screenshot of tailark-dusk-hero-section-2 at 375 pixels wide
Harness screenshot at 375 pixels wide. This viewport scrolled sideways.
Harness screenshot of tailark-dusk-hero-section-2 at 768 pixels wide
Harness screenshot at 768 pixels wide. This viewport scrolled sideways.
Harness screenshot of tailark-dusk-hero-section-2 at 1440 pixels wide
Harness screenshot at 1440 pixels wide. No horizontal overflow recorded.

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.

Harness measurements recorded for tailark-dusk-hero-section-2
BuildOK
MountOK
Console errors1
Uncaught page errors0
Horizontal overflowflagged at 375, 768
Axe critical0
Axe serious1
Axe moderate2
Axe minor0
Gzip marginal115.3 KB (180.7 KB build, 65.4 KB baseline)
Bare modeFAIL
Provider requiredNO
Demo usedwritten from the component source API

What the harness recorded

CONSOLE

Failed to load resource: the server responded with a status of 404 (Not Found)

BARE BUILD

✗ Build failed in 1.36s
error during build:
[vite]: Rollup failed to resolve import "@radix-ui/react-slot" from "<sandbox>re-ea0938796699/src/components/ui/button.tsx".

Verdict

A useful composition for an established Tailark and Next.js stack, but it does not currently build because the Dusk button dependency returns a missing registry resource. It needs a shadcn-style setup and manual dependency repair, so teams seeking a drop-in block should avoid it for now.

Use it if

  • You are building a Next.js product landing page with an application screenshot as the main proof point.
  • Your project already uses Tailwind and can adopt the related Tailark Dusk header, button, and logo-cloud components.
  • You want a static dark hero whose header and customer-logo row are composed as separate sections.

Skip it if

  • You need a dependency-free React section or cannot use Next Link and Image.
  • You need a registry install that works as published, because the referenced Dusk button currently resolves to a missing shadcn registry URL.
  • You do not have a suitable local product screenshot or do not want to maintain the bundled header and logo-cloud pieces.

Install

Installation record for tailark-dusk-hero-section-2
Declared dependenciesmotion, clsx, tailwind-merge
Missing on installnone
Bare installfails once the shadcn-style helpers are removed, so it needs that setup
Providerno provider required in the harness

In a non-shadcn project, add Tailwind, provide compatible Button, HeroHeader, and LogoCloud implementations, configure the component path alias, and supply the local mail screenshot. Use Next.js for Link and Image or replace those imports. The Dusk button must be sourced manually because its published registry reference is unavailable.

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/blocks
License
MIT
Record published
2026-08-15

Alternatives

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.