BladewindUI has been designed to not interfere with the existing components in your project.
Probably you just want to take this for a spin before deciding if BladewindUI components will be the only components you use in your project.
Once installed, all BladewindUI components are invoked from the
vendor > mkocansey > bladewind directory unless published.
Per Laravel convention, this results in you having to type the
<x-bladewind prefix everytime you want to use a BladewindUI component.
Once you publish the BladewindUI components, the files get moved to the
resources > views > components > bladewind directory.
You can then use the dot, instead of colon syntax to access a component.
Using any of the BladewindUI components can be without the bladewind prefix. This
<x-bladewind.button>Save User</x-bladewind.button> becomes
Achieving this is quite easy. This requires that you have run the command to publish Bladewind components .
Simply move all the blade files in
resources > views > components > bladewind into
resources > views > components.
You can then delete the bladewind folder from your
resources > views > components folder since it's technically empty at this point.
resources > views > componentsdirectory with the same names as what you are copying over from
resources > views > components > bladewind
The primary precompiled colour theme used for the BladewindUI components is blue. If your primary theme is not blue, you can change this in a few steps. This assumes you have some knowledge of Tailwind CSS
and how to compile changes made to Laravel's
From your command line, while at the root of your Laravel project, type the following command to publish the uncompiled css files for the BladewindUI components.
php artisan vendor:publish --provider="Mkocansey\Bladewind\BladewindServiceProvider" --tag=bladewind-assets --force
You should now have in your
public directory, a
vendor > bladewind > assets folder containing all the uncompiled tailwind css files.
You can modify these files to suit your theme specification.
Refer to this article if you are not familiar with compiling assets in Laravel.
Truely, you can! These components are in essence just Laravel blade templates that sit right in your project. If there are any implementations you are unhappy with, simply locate the particular blade template and dissect it at will. At the end of every component documentation page, you will find the name of the blade file that defines that component.
Updates that touch the css and js files require the library's assets to be republished. Run the command below to republish the library's css and js files.
php artisan vendor:publish --provider="Mkocansey\Bladewind\BladewindServiceProvider" --tag=bladewind-public --force
The Datepicker component is wired to speak a couple of languages. The language files are served from BladewindUI's vendor directory,
vendor > mkocansey > bladewind > lang
. Currently, the available languages are English, French, Italian and German. You can add more languages as you see fit or even modify the existing translations. If you want to do this for just your project you will first need to publish the language files by running the command below from the root of your project.
php artisan vendor:publish --provider="Mkocansey\Bladewind\BladewindServiceProvider" --tag=bladewind-lang --force
The language files will now be available in your project's
lang > vendor > bladewind directory. You can now add more languages or edit the language files that were published.