vibecodng.com

Free MCP betaIndex and tools live

Measured entry

tailark-dusk-hero-section-1

herodark-futuristic

A dark product hero shipped as a shadcn registry block, with an announcement link, paired calls to action, a framed app image, and a customer-logo strip. The source is built for React and Next.js, styled with Tailwind theme utilities, and imports a Tailark header and button, Lucide icons, several logo components, and a local mail2.png asset.

Specimen
Harness screenshot of tailark-dusk-hero-section-1 at 375 pixels wide
Harness screenshot at 375 pixels wide. This viewport scrolled sideways.
Harness screenshot of tailark-dusk-hero-section-1 at 768 pixels wide
Harness screenshot at 768 pixels wide. This viewport scrolled sideways.
Harness screenshot of tailark-dusk-hero-section-1 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-1
BuildOK
MountOK
Console errors1
Uncaught page errors0
Horizontal overflowflagged at 375, 768
Axe critical0
Axe serious2
Axe moderate3
Axe minor0
Gzip marginal76.3 KB (141.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 819ms
error during build:
[vite]: Rollup failed to resolve import "lucide-react" from "<sandbox>re-43db050b00ab/src/cut/components/hero-section-1.tsx".

Verdict

A polished composition for a dark SaaS landing page, but it is not usable from the published registry as-is: installation fails because the Tailark dusk button dependency resolves to a missing shadcn registry endpoint. It also needs a shadcn-style setup, and teams seeking a dependable drop-in block should avoid it until that dependency is repaired.

Use it if

  • You are already using Next.js, Tailwind theme tokens, and shadcn-style component aliases.
  • You want a centered SaaS hero with a product screenshot and an integration or customer-logo strip.
  • You are willing to vendor or replace the unavailable Tailark button dependency before installation.

Skip it if

  • You need a registry block that installs and builds without manual dependency repair.
  • Your project does not use Next.js Link and Image components and you do not want to adapt them.
  • Your page has no suitable product image or recognizable logo set for the lower sections.
  • You need a compact hero without a separate navigation header and substantial brand proof.

Install

Installation record for tailark-dusk-hero-section-1
Declared dependenciesclsx, 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

A non-shadcn project must add Tailwind and the referenced theme utilities, compatible component aliases, a Button with asChild behavior, the separate hero header and logo components, Lucide React, equivalents for Next.js Link and Image, and the mail2.png asset. The missing Tailark button must be recreated, vendored, or replaced because its registry endpoint 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.