Lumen UI: One system, three frameworks
How I built 123 accessible primitives for Astro, React, and Web Components while sharing tokens and behavior without forcing one runtime model.
- Design systems
- Astro
9 posts
Component structure, shared UI, linting, testing, and delivery practices for React projects.
Latest first
Back to blogPosts 1–9 of 9
How I built 123 accessible primitives for Astro, React, and Web Components while sharing tokens and behavior without forcing one runtime model.
Reusable ESLint library for React, Next.js, and TypeScript projects. Enforces code quality with flat config support and simplifies the move from ESLint 8 to 9.
Migrate ESLint 8 to 9 by converting .eslintrc to eslint.config.js, moving ignore patterns, and checking the rules used by your files.
Build a practical Next.js CI/CD pipeline with GitHub Actions that installs cleanly, runs linting and tests, verifies builds, and deploys trusted code.
A practical setup for testing React components with Vitest and React Testing Library, focused on behavior, confidence, and maintainable frontend code.
Set up Storybook in a Next.js project with Tailwind and TypeScript. Build isolated UI components, write stories, and improve design system collaboration.
A practical Husky setup for Next.js projects so linting, testing, and pre-push checks become part of the team workflow instead of a last-minute cleanup step.
Configure ESLint for Next.js with TypeScript and Vitest integration. Covers code quality rules, import conventions, and a scalable setup for React projects.
Structure React projects using Atomic Module Components — covering file layout, naming conventions, and scalability patterns for growing TypeScript codebases.
Related topics
All 112 topicsBeyond this topic
Follow another topic or return to the full writing archive.