vibecodng.com

Free MCP betaIndex and tools live

Measured entry

tailark-dusk-hero-section-7

herodark-futuristic

A dark CRM hero block shipped as a Tailark shadcn registry item. Its source is a Next.js component using Tailwind utility classes, Next Image and Link, Lucide's ArrowRight, plus Tailark header, button, and logo-cloud registry components. It also expects a local mail screenshot and loads its background from Unsplash.

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

Do not adopt this as a drop-in block. The verified build fails because the dusk button dependency resolves to a missing shadcn registry route. It also needs a shadcn-style setup before it can build or mount. Use it only if you are prepared to repair that dependency and integrate the related Tailark pieces.

Use it if

  • You already use Next.js, Tailwind, and shadcn conventions and can repair the Tailark registry dependency path.
  • You want a CRM landing hero with announcement copy, paired calls to action, product imagery, and a logo cloud.
  • Your design can accommodate the bundled dark Tailark styling and its dependent header and logo-cloud blocks.

Skip it if

  • You need a registry block that installs and builds without intervention.
  • Your app is not based on Next.js or cannot support Next Image, Next Link, and remote image configuration.
  • You do not want to carry the related Tailark header, button, and logo-cloud components.
  • You need a self-contained hero without a local product screenshot or an externally hosted background image.

Install

Installation record for tailark-dusk-hero-section-7
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 utilities and matching theme tokens, configure the component alias, install Lucide React, provide equivalents for the button, header, and logo cloud, add the local mail image, and configure Next.js to allow the Unsplash image host. The broken Tailark button registry reference must be replaced or resolved manually.

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.