Measured entry
ruixen-trusted-clients-showcase
logo-wallunclassifiedmotion on file
A client logo wall that ships as a React client component with configurable labels, logo nodes, links, and title text. Its reveal and collective hover dimming use React state, effects, IntersectionObserver, and CSS transitions. It has no declared package dependencies, but expects Tailwind utilities, theme tokens, and the shadcn cn helper.



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 | 27.2 KB (92.6 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 33.59s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/trusted-clients-showcase.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A tidy, adaptable logo wall that builds and mounts in the configured harness, with no overflow observed. A bare project fails on the missing utility import, so it needs a shadcn-style setup or a small adaptation. Fix the low-contrast resting state before production use.
Use it if
- You want a compact customer or partner wall with a restrained entrance reveal.
- Your logo data may mix linked brands, plain labels, and custom React logo nodes.
- Your project already uses Tailwind and shadcn-style path aliases and theme tokens.
Skip it if
- You need the supplied muted logo treatment to pass contrast checks without color tuning.
- You require keyboard focus to trigger the same spotlight feedback as pointer hover.
- You do not want a client component or JavaScript-driven entrance state.
- Your project avoids Tailwind and shadcn conventions and you do not want to adapt the styling and utility import.
Install
| Declared dependencies | none declared |
|---|---|
| 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 |
For a non-shadcn project, add a cn class-merging helper at the expected path or rewrite that import. Configure Tailwind with the foreground and muted-foreground theme tokens used by the component, preserve client-side React execution, and adjust the muted logo colors or opacity to satisfy your contrast target.
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 logo-wall pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- hyperui-logo-wall-1editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 22.4KB
- Bare
- pass
- Prov
- NO
- hyperui-logo-wall-2editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 22.7KB
- Bare
- pass
- Prov
- NO
- hyperui-logo-wall-3editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 22.8KB
- Bare
- pass
- Prov
- NO
- meraki-logo-wall-trusted-byminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 25.1KB
- Bare
- pass
- Prov
- NO
- tailark-mist-logo-cloud-1minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 27.1KB
- Bare
- pass
- Prov
- NO
- tailark-mist-logo-cloud-2minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 27.1KB
- Bare
- pass
- Prov
- NO