Measured entry

tailark-mist-integrations-2

feature-gridminimal-flat

A compact integrations strip with a centered heading, a wrapped row of branded SVG tiles, and an outlined link button. It ships as a Tailark shadcn registry block and expects Next.js Link, Tailwind theme utilities, a local Button primitive, and several registry-provided logo components.

Specimen
Harness screenshot of tailark-mist-integrations-2 at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-mist-integrations-2 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-mist-integrations-2 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 tailark-mist-integrations-2
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal56.1 KB (121.5 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 865ms
error during build:
[vite]: Rollup failed to resolve import "@radix-ui/react-slot" from "<sandbox>re-15c350e26d14/src/components/ui/button.tsx".

Verdict

A tidy starting layout, but not usable from the registry as published: the Tailark button dependency returns a missing-item response, so installation stops before build or mount. It needs a shadcn-style setup plus manual dependency repair. Avoid it when dependable drop-in installation matters.

Use it if

  • You already use the Tailark registry and can repair or replace the unavailable button dependency.
  • You need a small, static integrations teaser that links to a fuller integrations page.
  • Your stack already provides Next.js routing, Tailwind theme tokens, and matching local SVG components.

Skip it if

  • You need a registry block that installs and builds without manual dependency repair.
  • Your project is not based on Next.js or does not use shadcn-style aliases and component conventions.
  • You need interactive integration states, descriptions, filtering, or accessible labels for each logo.
  • Your team cannot maintain local copies or substitutes for the Tailark button and logo assets.

Install

Installation record for tailark-mist-integrations-2
Declared dependenciesclsx, tailwind-merge
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 React and Next.js routing support or replace Link, configure Tailwind with the expected foreground theme token and utility syntax, map the component import alias, provide an outline-capable Button with slot behavior, and add local equivalents for every branded SVG. The missing Tailark button registry reference must be replaced or repaired 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/blocks
License
MIT
Record published
2026-08-15

Alternatives

Other published entries for the feature-grid pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.