Measured entry

tripled-contact-block-shadcnui

contact-formminimal-flatmotion on file

A client-side React contact section shipped as a shadcn registry block. It combines a responsive form, contact cards, working hours, and viewport-triggered motion. It relies on shadcn Button, Card, Input, Label, and Textarea primitives, the shadcn theme and utility conventions, plus Framer Motion, Lucide icons, React, and Radix UI.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of tripled-contact-block-shadcnui at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of tripled-contact-block-shadcnui at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of tripled-contact-block-shadcnui 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 tripled-contact-block-shadcnui
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious1
Axe moderate0
Axe minor0
Gzip marginal72.4 KB (137.8 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 2m 6s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/components/ui/textarea.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A polished, responsive shell for a conventional contact page, with useful information cards and sensible stacking. It needs a shadcn-style setup, and teams must add submission behavior, replace placeholder details, and correct muted-text contrast before shipping.

Use it if

  • You want a complete contact-section layout with form fields, contact details, and office hours in one block.
  • Your app already uses shadcn primitives, theme tokens, path aliases, and the standard class-name utility.
  • You want restrained entrance and hover animation and are comfortable wiring the form submission yourself.

Skip it if

  • You need a form that submits, validates, or reports success without additional implementation.
  • Your accessibility gate cannot accept the current muted-text contrast failures without retheming.
  • You want to avoid adding an animation runtime and the surrounding shadcn component stack.
  • You need production-ready contact data and links without replacing the included placeholders.

Install

Installation record for tripled-contact-block-shadcnui
Declared dependenciesframer-motion, react, radix-ui
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 compatible Button, Card, Input, Label, and Textarea components; the class-name helper under the expected source utility path; the configured source alias; Tailwind theme tokens for background, foreground, border, muted, and primary colors; and the React, Radix UI, Framer Motion, and Lucide packages. Then connect the form to your validation and submission flow.

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.

Alternatives

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