Customizing BladewindUI

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 by default from your project's vendor > mkocansey > bladewind directory. Per Laravel convention, this results in you having to type the <x-bladewind prefix everytime you want to use a BladewindUI component.

        
            <x-bladewind::button>Save User</x-bladewind::button>

Once you publish the BladewindUI components, the files get moved to your project's resources > views > components > bladewind directory. You can then use the dot, instead of the colon syntax to access a component.

        
            <x-bladewind.button>Save User</x-bladewind.button>

Getting rid of the bladewind prefix

It is possible to get rid of the bladewind prefix entirely. <x-bladewind.button>Save User</x-bladewind.button> becomes <x-button>Save User</x-button>. To achieve this, you should have already published the Bladewind components. Next you will 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 should technically be empty at this point.

Please note that any existing components in your resources > views > components directory with the same name as what you are moving from the resources > views > components > bladewind directory, will be overwritten.

You can change everything

Truly, 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.

Something to keep in mind though. Most Bladewind updates we roll out may affect the blade files, css and js files.

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

To prevent any changes you made earlier from being overwritten by updates, we advise you to make all changes that overwrite Bladewind css classes in your project's css file instead of editing the Bladewind css file directly. Your project's css file should always be included after the Bladewind css file.

Changing Datepicker Translations

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 contributed by the community are English, French, Italian, Arabic, German, Chinese, Spanish and Indonesian. 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. You can contribute a new language translation.

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.