Measured entry
ruixen-scroll-over-hero
herounclassifiedmotion on file
A client-side React hero that pins a centered title while a framed media panel rises over it during scroll. It ships as a shadcn registry component, uses Motion for transforms and reduced-motion detection, and expects Tailwind theme classes plus the usual cn utility 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 | 1 |
| Gzip marginal | 68.3 KB (133.7 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 25.80s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/scroll-over-hero.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A credible fit for product-led landing pages, with responsive behavior and a considerate reduced-motion path. It needs a shadcn-style setup to build because the bare project cannot resolve its cn utility import. Fix the contrast and heading semantics before shipping.
Use it if
- You want a product screenshot or video to take over the opening message as visitors scroll.
- Your React site already uses shadcn conventions, Tailwind theme tokens, and Motion.
- You need a reduced-motion fallback that presents the title and media in a conventional stack.
Skip it if
- Your hero must remain compact and avoid a long pinned scrolling sequence.
- You cannot review and fix the supplied text contrast and empty-heading accessibility issues.
- Your project does not use Tailwind or shadcn-style aliases and you do not want to adapt the styling and imports.
- You want a lightweight static hero without an animation dependency.
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, configure Tailwind with background, foreground, muted, card, and border theme tokens, provide a cn class-merging utility at the expected alias, and preserve the client-component boundary. Replace the alias import if your project uses another module layout.
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