Measured entry
tailark-veil-team-2
A static founders-team section shipped as a shadcn registry block. It renders a heading, short introduction, and member cards from a local data array. The source uses Next.js Image, Tailwind theme tokens and container-query variants, plus remote GitHub avatar URLs; it has no interactive runtime or provider dependency.



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 | 3 |
| Uncaught page errors | 0 |
| Horizontal overflow | clean at 375, 768, 1440 |
| Axe critical | 0 |
| Axe serious | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 24.1 KB (89.5 KB build, 65.4 KB baseline) |
| Bare mode | OK |
| Provider required | NO |
| Demo used | written from the component source API |
What the harness recorded
CONSOLE
Failed to load resource: the server responded with a status of 404 (Not Found)
CONSOLE
Failed to load resource: the server responded with a status of 404 (Not Found)
CONSOLE
Failed to load resource: the server responded with a status of 404 (Not Found)
Verdict
It builds and mounts without a provider, but the verified render is not ready to ship: the section collapses into an excessively narrow column and the remote avatars fail to load. Use it as a small content scaffold only if you will repair the layout and own the image delivery.
Use it if
- You need a compact founders or leadership section whose names, roles, and portraits can be replaced directly in the component.
- Your app already uses Next.js and Tailwind with the theme tokens and container-query variants this block expects.
- You are prepared to restyle and verify the grid rather than treating the registry preview as production-ready.
Skip it if
- You need a team directory with bios, links, filters, or any other interaction.
- You cannot allowlist or self-host the remote avatar images.
- You need dependable responsive presentation without debugging the collapsed narrow-column layout seen in the verified render.
- You want a framework-neutral component rather than one coupled to Next.js Image and Tailwind conventions.
Install
| Declared dependencies | none declared |
|---|---|
| Missing on install | none |
| Bare install | builds and mounts without the shadcn-style helpers |
| Provider | no provider required in the harness |
In a non-shadcn project, add Tailwind CSS, define the background, foreground, muted-foreground, and font theme tokens, and enable the container-query variants used by the grid. Use Next.js Image with the remote GitHub host allowed, or replace it with your framework's image element and preferably host the portraits yourself.
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 team pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- hyperui-team-3editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.4KB
- Bare
- pass
- Prov
- NO
- meraki-team-side-by-sideminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- meraki-team-simpleminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- hyperui-team-1editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 18.1KB
- Bare
- pass
- Prov
- NO
- hyperui-team-2editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 18.2KB
- Bare
- pass
- Prov
- NO
- meraki-team-backgroundminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 20.5KB
- Bare
- pass
- Prov
- NO