Measured entry
tailark-veil-contact-1
A minimal contact section with business details beside a labeled inquiry form. It ships as a shadcn registry block and imports Tailark variants of Button, Card, Input, Label, and Textarea through the usual component alias. It also relies on Next.js Link plus Tailwind theme and container-query utilities, and includes no form submission behavior.



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 | flagged at 375 |
| Axe critical | 0 |
| Axe serious | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 52.1 KB (117.5 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 1.08s error during build: [vite]: Rollup failed to resolve import "@radix-ui/react-slot" from "<sandbox>re-9a1f805daf49/src/components/ui/button.tsx".
Verdict
A sensible, restrained contact layout, but the published package currently fails before build because its Veil Button registry dependency returns an HTTP not-found response. It also needs a shadcn-style setup, so teams seeking a drop-in or verified production component should avoid it until the registry reference is repaired.
Use it if
- You already use the Tailark Veil registry and want a compact contact section that matches its primitives.
- You need a presentational inquiry form and will connect its action, validation, and delivery yourself.
- Your Next.js app already supports the component alias, theme tokens, and container-query utilities used here.
Skip it if
- You need a working submission flow, spam protection, success feedback, or server-side handling out of the box.
- Your project cannot resolve Tailark registry dependencies, since the current Veil Button dependency returns an HTTP not-found response.
- You are not using Next.js and do not want to replace its Link import or recreate the expected UI primitives.
- You need a component that installs and builds successfully from the published registry today.
Install
| Declared dependencies | clsx, tailwind-merge |
|---|---|
| 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 |
In a non-shadcn project, add equivalent Button, Card, Input, Label, and Textarea components, configure the component import alias, provide the referenced Tailwind theme and container-query utilities, and either install Next.js Link support or replace it with ordinary anchors. You must also repair or bypass the unavailable Veil Button registry dependency before installation can complete.
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/blocksAlternatives
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.
- hyperui-contact-forms-1editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.4KB
- Bare
- pass
- Prov
- NO
- hyperui-contact-forms-2editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.5KB
- Bare
- pass
- Prov
- NO
- hyperui-contact-forms-4editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.5KB
- Bare
- pass
- Prov
- NO
- hyperui-contact-forms-3editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.6KB
- Bare
- pass
- Prov
- NO
- hyperui-contact-forms-5editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 18.4KB
- Bare
- pass
- Prov
- NO
- efferd-contact-2minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 30.4KB
- Bare
- fail
- Prov
- NO