1/5 β Why we're building #WireKit π οΈ
We've been building pretty much everything with #Laravel for years. We love #Livewire, and we genuinely love Flux UI.
But we kept running into the same situation: we needed components, interactions, or customization options that weren'tβ¦
Commit
82222b9
2/5 β Built around the stack we love β‘
WireKit is built with Blade, Livewire 4, Alpine.js, and #TailwindCSS 4.
We wanted something that feels completely natural in Laravel, without introducing another frontend framework or fighting against the tools we already enjoy using.
π¨β¦
3/5 β Documentation and something like agent-first π€
Let's be real: nobody wants to spend hours digging through documentation anymore. Most of us already use #AI coding assistants, so we're building WireKit's documentation with that in mind.
Detailed component references, live previews, structured schemas, CLI tooling, and #MCP integration.
Humans can explore everything visually, while agents get the exact information they need instead of guessing props or inventing components.
Good documentation should work for both.
commit 82222b9
4/5 β An ecosystem, not a dependency trap π§©
Something we're being very intentional about: every package we build works with plain #Blade. WireKit integration is included, but never required.
We want developers to be able to use our packages independently, without adopting anβ¦
5/5 β A lot more work than we expected β€οΈ π₯
Building a component library from scratch is a lot more work than it might seem.
It's not just about making components look good. It's accessibility, keyboard navigation, component states, edge cases, theming, testing, documentation,β¦
GitHubGitHub - pushery/wirekit: Open-Source TALL stack UI components for Laravel Livewire, built with Tailwind CSS v4 and Alpine.jsOpen-Source TALL stack UI components for Laravel Livewire, built with Tailwind CSS v4 and Alpine.js - pushery/wirekit
1 other commit about this link