Measured entry
ruixen-service-ledger
ctaunclassifiedmotion on file
A client-side service catalogue that pairs a sticky, horizontally scrollable tab strip with long-form service entries, optional media, and inline calls to action. It ships as a shadcn registry TSX component and depends on React, Next.js Link, lucide-react, Tailwind theme classes, and the usual cn utility.



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 | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 45.9 KB (111.3 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 30.48s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/service-ledger.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A solid fit for content-heavy service pages: the scroll spy, reduced-motion handling, responsive tab scroller, and optional media are thoughtfully covered. It needs a shadcn-style setup, so it is not a drop-in choice for a bare React project.
Use it if
- You need to present several detailed services without hiding their deliverables behind accordions.
- Your page benefits from scroll-aware navigation that keeps the current service visible and directly reachable.
- You want optional images or videos and per-service calls to action within one consistent section.
Skip it if
- Your offering is short enough for a simple card row or compact comparison table.
- Your page already has sticky navigation that could compete with this component's sticky tab strip.
- Your app is not based on Next.js and you do not want to replace the framework-specific Link component.
Install
| Declared dependencies | lucide-react |
|---|---|
| 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 lucide-react, a cn class-merging utility, the expected Tailwind theme tokens and utility classes, and the configured path alias. Use it as a client component, and either provide Next.js Link or replace it with your router's link component.
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 cta pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- meraki-cta-simpleminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 17.7KB
- Bare
- pass
- Prov
- NO
- hyperui-ctas-4editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.8KB
- Bare
- pass
- Prov
- NO
- meraki-cta-gridminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 17.8KB
- Bare
- pass
- Prov
- NO
- meraki-cta-formminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- hyperui-ctas-2editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 18.0KB
- Bare
- pass
- Prov
- NO
- meraki-cta-cardminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 18.0KB
- Bare
- pass
- Prov
- NO