vibecodng.com

Free MCP betaIndex and tools live

Measured entry

ruixen-structured-hero-section

herounclassified

A configurable Next.js client hero with an announcement pill, headline, calls to action, overlapping image cards, and an optional customer-logo strip. It ships as a shadcn registry component and relies on React, next/link, Tailwind theme utilities, and the local cn helper rather than declared packages.

Specimen
Harness screenshot of ruixen-structured-hero-section at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of ruixen-structured-hero-section at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of ruixen-structured-hero-section 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 ruixen-structured-hero-section
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor1
Gzip marginal44.2 KB (109.6 KB build, 65.4 KB baseline)
Bare modeFAIL
Provider requiredNO
Demo usedwritten from the component source API

What the harness recorded

BARE BUILD

✗ Build failed in 26.82s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/structured-hero-section.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A flexible, visually specific hero that builds and mounts in its intended environment, with clean responsive behavior. It needs a shadcn-style setup, and teams should always provide the required title to avoid the empty-heading accessibility issue.

Use it if

  • You need a product landing hero that can combine calls to action, interface previews, and customer logos.
  • Your app already uses Next.js, Tailwind theme tokens, and the usual shadcn utility alias.
  • You want content, links, cards, and logos supplied through props instead of editing fixed markup.

Skip it if

  • Your site is not built with Next.js or you do not want to replace next/link.
  • You need a small, dependency-light hero without a sizable set of generated utility styles.
  • You expect a meaningful no-props fallback, since omitting the required title leaves an empty heading.
  • Your design cannot accommodate tall, overlapping portrait cards and fade overlays.

Install

Installation record for ruixen-structured-hero-section
Declared dependenciesnone declared
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 a cn class-merging helper at the expected alias or change the import, configure that alias, provide Tailwind with shadcn-style color tokens and utility support, and replace next/link if the app is not using Next.js. Supply a non-empty title when rendering.

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/ruixenui/ruixen.com
License
MIT
Record published
2026-08-14

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.