Measured entry

efferd-cta-4

contact-formminimal-flat

A static call-to-action card shipped as a shadcn registry block, despite its contact-form label. It combines a short trial pitch with sales and signup buttons. The source relies on the shadcn Button primitive, its Radix-backed setup, Lucide icons, Tailwind utilities, and theme color tokens.

Specimen
Harness screenshot of efferd-cta-4 at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of efferd-cta-4 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of efferd-cta-4 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 efferd-cta-4
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal32.3 KB (97.7 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 1m 43s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/components/ui/button.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A clean, reliable two-action CTA with sound responsive behavior and no observed accessibility issues. The queue label is misleading because this is not a form, and it needs a shadcn-style setup to mount. Best for teams already using that stack and willing to replace the placeholder copy and actions.

Use it if

  • You need a restrained trial or sales CTA with two clear next actions.
  • Your app already uses shadcn components, Tailwind theme tokens, and Lucide icons.
  • You want a responsive card that can drop into a landing page without a provider.

Skip it if

  • You need an actual contact form with fields, validation, or submission handling.
  • Your design system does not use shadcn primitives or Tailwind utility classes.
  • You need richer proof, pricing context, or product imagery inside the CTA.
  • You want working navigation before adding destinations and click behavior yourself.

Install

Installation record for efferd-cta-4
Declared dependenciesradix-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 a compatible Button component, the class-name utility it imports, the expected path aliases, Tailwind processing, card and muted theme tokens, and Lucide React icons. Then wire both buttons to real destinations or handlers.

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.