vibecodng.com

Free MCP betaIndex and tools live

Measured entry

tailark-dusk-footer-1

footerdark-futuristic

A static Next.js footer with grouped navigation, a branded home link, a newsletter form shell, and copyright text. It ships as a shadcn registry block and depends on Next.js Link, Tailwind theme classes, path aliases, and Tailark registry items for the logo, button, input, and label.

Specimen
Harness screenshot of tailark-dusk-footer-1 at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-dusk-footer-1 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of tailark-dusk-footer-1 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-dusk-footer-1
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious1
Axe moderate0
Axe minor0
Gzip marginal51.7 KB (117.1 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 1.11s
error during build:
[vite]: Rollup failed to resolve import "@radix-ui/react-slot" from "<sandbox>re-72084c413dad/src/components/ui/button.tsx".

Verdict

Do not adopt it from the registry as-is. The build stops because the Tailark logo dependency resolves to a missing shadcn registry item. It needs a shadcn-style setup even after that is repaired, so teams needing a drop-in, build-green footer should avoid it.

Use it if

  • You already use Next.js with shadcn aliases and can repair or pin the Tailark registry dependencies.
  • You need grouped footer navigation alongside a branded home link and newsletter email form.
  • You plan to replace the placeholder links and connect the subscription form to your own handler.

Skip it if

  • You need registry installation to work without patching the missing Tailark logo item.
  • Your app is not on Next.js or lacks Tailwind and shadcn theme and alias conventions.
  • You need production-ready newsletter submission behavior instead of an unconnected form shell.
  • You require a component that has already passed build, mount, and runtime accessibility checks.

Install

Installation record for tailark-dusk-footer-1
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 Next.js routing or replace Link, configure Tailwind utilities and theme tokens, create the path alias, and provide local LogoIcon, Button, Label, and Input equivalents. Connect the form to a real submission handler and replace the missing logo 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/blocks
License
MIT
Record published
2026-08-15

Alternatives

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