Measured entry
ruixen-layouts-calendar
feature-gridunclassifiedmotion on file
A full-page React calendar with day and week views, draggable and resizable events, sidebars, event details, a command menu, and keyboard shortcuts. It ships as a shadcn registry block with a Next.js page, components, hooks, utilities, and mock event data, and relies on date-fns, Radix-based UI pieces, Lucide, Motion, cmdk, React DayPicker, and next-themes.



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 | flagged at 375, 768, 1440 |
| Axe critical | 1 |
| Axe serious | 5 |
| Axe moderate | 2 |
| Axe minor | 0 |
| Gzip marginal | 194.7 KB (260.1 KB build, 65.4 KB baseline) |
| Bare mode | FAIL |
| Provider required | NO |
| Demo used | written from the component source API |
What the harness recorded
BARE BUILD
✗ Build failed in 47.83s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/components/ui/tooltip.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
The configured build mounts, and the interaction set is unusually complete, but this is a substantial starting point rather than release-ready UI. It needs a shadcn-style setup, overflows across the tested layouts, and carries meaningful accessibility debt. Use it when its calendar behavior offsets the integration and remediation work.
Use it if
- You need a feature-rich calendar shell and expect to connect its mock event state to your own data layer.
- Your app already uses Next.js, Tailwind, shadcn conventions, path aliases, and the same UI primitives.
- You are prepared to refine responsive behavior and accessibility before release.
Skip it if
- You need a drop-in calendar for a plain React project with minimal setup.
- Your release requires clean responsive containment without layout remediation.
- You cannot budget time to fix unnamed controls, nested interactive elements, contrast, landmarks, and keyboard access to scrolling.
- You want a small date picker or a lightweight event list rather than an application-scale calendar surface.
Install
| Declared dependencies | date-fns, lucide-react, next-themes, react-day-picker, cmdk, motion, radix-ui, react-day-picker@latest |
|---|---|
| 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 the declared packages, the at-sign path alias, a cn class-merging utility, Tailwind and the expected theme tokens, plus compatible button, popover, tooltip, sidebar, command, calendar, menu, form, and avatar primitives. Provide next-themes context and either Next.js routing or replace the Next Link usage. Wire real event persistence in place of the bundled mock data.
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/ruixenui/ruixen.comAlternatives
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.
- hyperui-feature-grids-3editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.7KB
- Bare
- pass
- Prov
- NO
- hyperui-feature-grids-1editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- hyperui-feature-grids-4editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- hyperui-feature-grids-2editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 18.3KB
- Bare
- pass
- Prov
- NO
- meraki-feature-grid-list-with-imageminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 18.5KB
- Bare
- pass
- Prov
- NO
- meraki-feature-simpleminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 20.2KB
- Bare
- pass
- Prov
- NO