vibecodng.com

Free MCP betaIndex and tools live

Measured entry

tailark-dusk-testimonials-1

testimonialsdark-futuristic

A Tailark registry block for a responsive testimonial section with paired editorial cards, OpenAI and Gemini marks, a play control, and a looping remote background video. It ships as a TSX component and depends on Tailark registry items for the button and logos, plus lucide-react and Tailwind-style utilities.

Specimen
Harness screenshot of tailark-dusk-testimonials-1 at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-dusk-testimonials-1 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-dusk-testimonials-1 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 tailark-dusk-testimonials-1
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical1
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal34.9 KB (100.3 KB build, 65.4 KB baseline)
Bare modeFAIL
Provider requiredNO
Demo usedwritten from the component source API

What the harness recorded

BARE BUILD

✗ Build failed in 2.20s
error during build:
[vite]: Rollup failed to resolve import "lucide-react" from "<sandbox>re-8cd5eac9d766/src/cut/components/testimonials-1.tsx".

Verdict

Do not adopt it unchanged. The registry install fails because the Tailark button dependency resolves to a missing shadcn registry endpoint, so the component never builds or mounts. It needs a shadcn-style setup plus a repaired or locally substituted button dependency before evaluation.

Use it if

  • You want a dark, editorial testimonial section with asymmetric cards and prominent quotes.
  • Your app already uses a shadcn-style registry workflow and can provide or replace the Tailark button and logo components.
  • A remotely hosted autoplay video is acceptable for the page experience and privacy policy.

Skip it if

  • You need an installable registry block without repairing a missing Tailark button dependency.
  • Your project avoids remote autoplay media or requires all assets to be self-hosted.
  • You need a verified build or mount before adoption, since the harness never reached either stage.
  • Your design system cannot accommodate Tailwind-style utilities and shadcn component conventions.

Install

Installation record for tailark-dusk-testimonials-1
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

In a non-shadcn project, add React and lucide-react, configure Tailwind-style utility processing and theme tokens, create compatible Button, OpenAI, and Gemini components, replace the registry aliases, and decide whether to self-host the video. The missing Tailark button registry item must be supplied locally or replaced.

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/tailark/blocks
License
MIT
Record published
2026-08-15

Alternatives

Other published entries for the testimonials pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.