Measured entry
meraki-team-grid-list
A static team directory section with a heading, intro copy, portrait cards, roles, and social links. It ships as a complete HTML document that loads Tailwind from its CDN, uses remote Unsplash portraits, and embeds the social icons as inline SVG. It has no JavaScript or component-library 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 | 0 |
| 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 | 21.1 KB (86.5 KB build, 65.4 KB baseline) |
| Bare mode | OK |
| Provider required | NO |
| Demo used | none |
Verdict
A dependable static starting point for a conventional team page, with clean responsive behavior and no runtime machinery. Adopt it when Tailwind is already part of the site, but budget time to componentize the repeated cards, replace remote assets, fix placeholder links, and clarify card interaction.
Use it if
- You need a straightforward team roster that adapts from a single column to a wider card grid.
- Your site already uses Tailwind utilities and you can replace the sample people, portraits, and profile links.
- You want hover styling and dark-mode classes without adding runtime logic.
Skip it if
- Your team data comes from a CMS and you need a reusable mapped component rather than repeated static markup.
- Your content policy forbids remote portrait hosting or a runtime styling CDN.
- You need each card itself to navigate or expose actions, since the supplied card only looks clickable and its social links are placeholders.
- You need meaningful portrait alternative text without revising the supplied image markup.
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 and configure Tailwind CSS, include the source paths in Tailwind's content scan, and copy the section markup into your page or template. Replace the CDN script for production, provide approved portrait assets, add descriptive image text where appropriate, and wire every social link to a real destination.
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/merakiui/merakiuiAlternatives
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