Introduction

A Laravel-first component library for building polished interfaces with Blade.

April UI 1.x Blade · Alpine · Livewire

Build polished interfaces without leaving Laravel.

April UI brings the component quality of shadcn/ui to Blade, with Alpine for browser state, Livewire when the server should stay involved, and Tailwind for the final say.

A Laravel workflow, kept intact

April UI is designed to feel like part of your application. Write normal Blade components, keep interaction in Alpine or Livewire, and publish only the views you need to own.

resources/views/dashboard.blade.php
<april:card>
<slot:title>Revenue</slot:title>
<slot:content>
<p class="text-2xl font-bold">$45,231.89</p>
<p class="text-sm text-muted-foreground">+20.1% from last month</p>
</slot:content>
</april:card>

Blade first

Readable application markup

Your templates stay close to the HTML and Laravel patterns you already use.

State is yours

Alpine, Livewire, or both

April UI gives you the surface without deciding how your application should think.

Own the exception

Package views with safe overrides

Use the defaults, then publish a component when your product needs its own behavior or markup.

Explore the library

The component pages show the rendered result, the Blade source, available options, and the commands for publishing views when you need to customize them.