vibecodng.com

Free MCP betaIndex and tools live

Measured entry

tripled-contact-form-section-shadcnui

contact-formminimal-flatmotion on file

A client-side React contact section shipped as a shadcn registry block. It combines animated introductory copy, contact details, and a controlled form using Tailwind theme classes, shadcn Button, Card, Input, Label, and Textarea primitives, plus Framer Motion, Lucide icons, and Radix-backed UI foundations.

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

Verdict

A credible starting point for a styled inquiry section: it builds, mounts, stays within its viewports, and showed no automated accessibility findings in the prepared harness. It needs a shadcn-style setup, and the logging-only submit path means real delivery, validation feedback, and consent behavior remain application work.

Use it if

  • You want a complete contact section with business details and a project inquiry form in one layout.
  • Your app already uses shadcn conventions, Tailwind theme tokens, and path aliases.
  • You are prepared to connect the submit handler to your own API, validation, and success states.
  • Entrance animation fits the interaction style of the surrounding page.

Skip it if

  • You need a form that sends data without adding backend submission logic.
  • You want to avoid shipping a motion dependency for a single content section.
  • Your project cannot accommodate shadcn primitives, Tailwind theme tokens, or the expected path alias.
  • You need production contact details and policy links to work without editing placeholders.

Install

Installation record for tripled-contact-form-section-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 Tailwind with the expected semantic color tokens and path alias, provide compatible Button, Card, Input, Label, and Textarea components plus the shared class-name utility, and install React, Framer Motion, Lucide React, and the Radix dependencies used by those primitives. Then replace the placeholder contact data, policy link, and submit logger.

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/moumen-soliman/uitripled
License
MIT
Record published
2026-08-14

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.