Measured entry
tailark-dusk-team-1
A Tailark registry block for a dark team section, shipped as a Next.js TSX component. It renders a heading, hiring link, and responsive member grid with remote Unsplash portraits, using next/link, next/image, Tailwind theme utilities, and a shadcn-style Button 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 | 32 |
| Uncaught page errors | 0 |
| Horizontal overflow | clean at 375, 768, 1440 |
| Axe critical | 0 |
| Axe serious | 1 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 57.1 KB (122.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
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
Do not adopt this block as published. Its Tailark button dependency points to a missing shadcn registry endpoint, so installation stops before build or mount verification. It needs a shadcn-style setup plus a repaired or locally substituted Button before it can be evaluated.
Use it if
- You need a ready-made team roster for a Next.js site using Tailwind theme tokens.
- You can repair or replace the unavailable Tailark button registry dependency.
- You are comfortable configuring remote portraits or swapping them for owned assets.
Skip it if
- You need a component that installs and builds from the published registry without intervention.
- Your project is not based on Next.js or cannot use next/image and next/link.
- You need verified runtime or accessibility behavior before adoption.
- You do not want placeholder staff content and externally hosted portraits in the starting implementation.
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 |
A non-shadcn project must add Tailwind utilities and matching theme tokens, provide a compatible Button with asChild and outline behavior, support Next.js Link and Image or replace them, allow the remote image host, and repair or bypass the missing Tailark registry dependency.
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