vibecodng.com

Free MCP betaIndex and tools live

Measured entry

tailark-dusk-hero-section-10

herodark-futuristic

A static Next.js hero block shipped through a shadcn registry. It combines a split headline and call to action with a layered image panel and logo cloud, and depends on Tailwind theme utilities, Next Image and Link, Lucide, a Tailark button, header, and logo-cloud block.

Specimen
Harness screenshot of tailark-dusk-hero-section-10 at 375 pixels wide
Harness screenshot at 375 pixels wide. This viewport scrolled sideways.
Harness screenshot of tailark-dusk-hero-section-10 at 768 pixels wide
Harness screenshot at 768 pixels wide. This viewport scrolled sideways.
Harness screenshot of tailark-dusk-hero-section-10 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-10
BuildOK
MountOK
Console errors4
Uncaught page errors0
Horizontal overflowflagged at 375, 768
Axe critical0
Axe serious2
Axe moderate2
Axe minor0
Gzip marginal115.2 KB (180.6 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)

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

A useful composition for teams already invested in the Tailark stack, but it is not currently consumable from the published registry: the button dependency returns a not-found response, so installation and build stop before rendering. It needs a shadcn-style setup and a repaired or locally supplied button entry.

Use it if

  • You need a dark SaaS landing hero with navigation, a direct call to action, product-style framing, and customer logos.
  • Your app already uses Next.js, Tailwind theme tokens, shadcn aliases, and compatible Tailark registry blocks.
  • You are comfortable replacing the supplied copy, links, remote image, and logo content before launch.

Skip it if

  • You need a framework-neutral section or do not want Next.js Image and Link in the component.
  • You need an installable registry block today, because its Tailark button dependency resolves to a missing registry endpoint and stops the build.
  • Your design system cannot absorb Tailwind theme classes, path aliases, and three related Tailark components.

Install

Installation record for tailark-dusk-hero-section-10
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

A non-shadcn project must add Tailwind with matching theme tokens, configure the component path alias, provide Button, HeroHeader, and LogoCloud equivalents, install Lucide, and adapt Next Image and Link or replace them. The missing Tailark button registry entry must be sourced locally or corrected before the block can build.

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.