Blade UI Kit is a set of renderless components to utilise in your Laravel Blade views. In all essence, it's a collection of useful utilities, connecting the dots between different parts of the TALL stack.

It was made for Blade, Laravel's powerful templating engine. Every Blade UI Kit component is a Blade component with a view and a class. Each component can be extended, modified and overwritten.

The components are renderless, meaning they ship without any styling applied to them. This puts you in full control of how they look and feel.

To give you a practical introduction example, let's look at the way how Blade UI Kit's alert component replaces Laravel's default alert snippet from its UI scaffolding:

@if (session('status'))
    <div class="alert alert-success" role="alert">
        {{ session('status') }}

This is turned into this:

<x-alert class="alert alert-success"/>

As you can see, all the implementation details about the behavior of the component are hidden away, making it up to you to decide how to style it.

All of Blade UI Kit's components were designed with this in mind, letting you worry less about implementation details and allowing you to focus on what truly matters: building your app... all while providing a great developer experience.

To give you a more proper demonstration of the library, we've built a demo Laravel project that makes use of some of the components from Blade UI Kit.


Blade UI Kit was designed with composition in mind. Meaning that we encourage to wrap Blade UI Kit's components within your own Blade view components when setting defaults like styling. Let's dive into a practical example built in Laravel 8.

Take our form input component for example. You probably want to apply some default styling to it so it can be re-used throughout your app. Let's style it by making use of Tailwind CSS. We're going to create an anonymous Blade component called input that resides in a resources/views/components/forms directory:

<x-input :name="$name" {{ $attributes->merge(['class' => 'p-4 text-gray-700']) }} />

As you can see we're referencing Blade UI Kit's component inside our own forms.input component. By doing so we retain all the power of the Blade UI Kit component while making sure the component has the look and feel which is right for our app.

Of course, sometimes when wrapping components in similar named components, naming collisions may occur. Luckily, we provide a way to prefix our components to prevent that from happening.

Note: required class arguments should be piped through to the base component. All other attributes can be piped through by using {{ $attributes }}.

Piping Attributes

It is important to know that the above example was written in Laravel 8. Laravel 8 allows for the ability to pipe attributes onto another component. Piping attributes means that if you applied something like an id attribute onto the place where the component is used in a view, it will get piped through onto the Blade UI Kit component by using the {{ $attributes }} syntax.

This isn't available in Laravel 7, unfortunately, as this was a breaking change - so it was decided to introduce it only in Laravel 8. If you're using Laravel 7 you'll have to manually pipe through all attributes that you want to pass on:

    :id="$id ?? null"
    :class="($class ?? '') . ' p-4 bg-white text-gray-700'"

Blade Icons

If you're interested in an easy solution for handling SVG icons in your Laravel Blade views, we can help you with that. We've built Blade Icons, a package to reference SVG icons via Blade components, Blade directives, or a helper function. You can also make use of the search on our website to find the icon you need amongst thousands of available icons.

On this page

© 2024 Dries Vints. Site built with the TALL Stack. Artwork by Caneco.