Starter kits

April UI provides two starter kits. Both keep Laravel's normal application structure and use April UI for the presentation layer.

Blade starter kit

Use this kit when you want standard Laravel controllers, HTTP forms, redirects, and server-rendered Blade views:

laravel new my-app --using=yungifez/april-ui-blade-starter-kit

laravel new my-app --using=yungifez/april-ui-blade-starter-kit

The Blade kit includes Fortify authentication, Alpine for small browser interactions, a responsive application shell, account settings, and April UI components. It does not install Livewire.

Livewire starter kit

Use this kit when you want Livewire page components and server-side interactions:

laravel new my-app --using=yungifez/april-ui-starter-kit

laravel new my-app --using=yungifez/april-ui-starter-kit

The Livewire kit includes Livewire 4, Fortify authentication, the same application shell, and the same April UI component API.

Customize components

Both kits keep April UI as a Composer dependency. Publish only the components that your application owns:

php artisan april:list
    php artisan april:publish button

php artisan april:list
    php artisan april:publish button

Published files go to resources/views/vendor/april/components. Laravel's normal vendor view lookup rules then override the matching package view. This lets package upgrades remain safe while keeping application-specific markup in the application.

Local development

After the Laravel installer creates the project, start the application with:

composer dev

composer dev

Run the test suite and frontend build before committing changes:

composer test
    npm run build

composer test
    npm run build