vibecodng.com

Free MCP betaIndex and tools live

Measured entry

ruixen-tabbed-hero-section

herounclassified

A client-side React hero distributed through a shadcn registry. It combines a headline, Next.js CTA links, selectable tab buttons, an empty showcase frame, optional light and dark background images, and a trust-logo strip. It depends on Next.js, Tailwind theme utilities, React state, and a cn helper built with clsx and tailwind-merge.

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

What the harness recorded

BARE BUILD

✗ Build failed in 118ms
error during build:
[vite]: Rollup failed to resolve import "lucide-react" from "<sandbox>re-bd5e00f25f1e/src/cut/demo.jsx".

Verdict

A solid landing-page scaffold that builds, mounts, and adapts across the tested layouts, but its tab interaction is mostly cosmetic and the showcase is intentionally empty. It needs a shadcn-style setup in a bare project, plus real panel content and stronger tab behavior before production use.

Use it if

  • You want a SaaS hero shell that groups calls to action, product-category selectors, and customer proof.
  • Your Next.js app already has shadcn-style Tailwind tokens, path aliases, and a cn utility.
  • You plan to supply your own product preview or other content for the showcase area.

Skip it if

  • You need tabs that switch actual panels, because the buttons only change their selected styling.
  • You need complete tab semantics and keyboard behavior without extending the component.
  • Your app is framework-neutral or does not use Next.js and you do not want to replace its Link usage.
  • You need a controlled tab selection that follows later activeTab prop changes.

Install

Installation record for ruixen-tabbed-hero-section
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

For a non-shadcn project, add Tailwind with the semantic theme classes used here, configure the path alias, and create a cn helper using clsx and tailwind-merge. Install and configure Next.js for Link, or replace Link with your router or anchors. The demo icons also require lucide-react, though the component accepts any React nodes.

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-18

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.