Measured entry
ruixen-product-feature-hero
herogradient-glowmotion on file
A client-side React hero pairing product copy and a CTA with an animated command-palette mockup, followed by a feature grid. It ships as a shadcn registry component and relies on Motion, Lucide icons, Tailwind theme utilities, and the usual cn helper alias.



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.
| Build | OK |
|---|---|
| Mount | OK |
| Console errors | 0 |
| Uncaught page errors | 0 |
| Horizontal overflow | clean at 375, 768, 1440 |
| Axe critical | 0 |
| Axe serious | 1 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 69.4 KB (134.8 KB build, 65.4 KB baseline) |
| Bare mode | FAIL |
| Provider required | NO |
| Demo used | written from the component source API |
What the harness recorded
BARE BUILD
✗ Build failed in 35.76s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/product-feature-hero.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A polished, responsive starting point for developer-product pages, with useful content props and restrained motion. It needs a shadcn-style setup to build and mount, and teams should fix the muted-text contrast before shipping. The added runtime weight is hard to justify for a purely decorative hero.
Use it if
- You need a responsive launch-page hero for a developer tool or code-focused product.
- You want editable headline, description, CTA, supporting copy, and feature data without rebuilding the layout.
- Your app already uses shadcn-style Tailwind tokens and can absorb Motion for subtle entrance animation.
Skip it if
- Your accessibility bar requires the supplied muted text colors to pass contrast checks without revision.
- Your page has a strict JavaScript budget and the decorative animation does not justify the added runtime weight.
- Your product cannot plausibly use the fixed code-editor command palette as its hero visual.
Install
| Declared dependencies | motion |
|---|---|
| Missing on install | none |
| Bare install | fails once the shadcn-style helpers are removed, so it needs that setup |
| Provider | no provider required in the harness |
In a non-shadcn project, add Motion and Lucide React, configure the at-sign source alias, provide a cn class-merging helper, and define the Tailwind foreground, muted, card, and border theme utilities used by the component. Also ensure your Tailwind setup supports its mask utility, or replace that fade treatment with local CSS.
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.comAlternatives
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.
- ruixen-tabbed-hero-sectionunclassified
- Renders
- YES
- A11y
- 0
- Gzip
- 50.6KB
- Bare
- fail
- Prov
- NO
- 8bitcn-hero1skeuomorphism
- Renders
- YES
- A11y
- 0
- Gzip
- 51.5KB
- Bare
- fail
- Prov
- NO
- tailark-mist-hero-section-5minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 64.8KB
- Bare
- fail
- Prov
- NO
- tailark-mist-hero-section-6minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 64.8KB
- Bare
- fail
- Prov
- NO
- ruixen-arc-reveal-herounclassified
- Renders
- YES
- A11y
- 0
- Gzip
- 71.6KB
- Bare
- fail
- Prov
- NO
- tripled-cta-hero-block-shadcnuiminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 72.8KB
- Bare
- fail
- Prov
- NO