Version: 0.1 development
If you don't need to be choosy or configure anything, just grab the following two folders from the repo and drop them into your project
Put this /bl in /resources/views/components
Put this /scss in /resources/
Don't forget to update your vite.config.js file to point to the scss folder instead of the default css.
All projects should be normalized. This can be done by including the _normalize.scss file
All components require colors. That is included in the _bl-colors.css file
Most components require typography. That is included in the _bl-typography.css file
All components are meant to be dropped into a project with the following structure:
/resources/scss/app.scss
and
/resources/views/components/bl/
Where /resources/scss/app.scss has the following:
@import 'normalize';
@import 'bl-colors';
@import 'bl-typography';
@import '<what-you-add>';
These components have two files each.
The components are namespaced by folder. This means, as long as the component is in the /resources/views/components/bl/ folder, it doesn't need a special name. However, class names and scss files are specially named:
<name>.blade.php and stored in /resources/views/components/bl/
bl-component-<name>
_bl-<category-or-name>.scss
e.g. /bl/h1.blade.php has a class of .bl-component-h1 located in the scss file called _bl-headers.scss
All h* tags are styled in that one scss file. They are in the category of header.
A table component would have 'table' for its name and category:
e.g. /bl/table.blade.php, .bl-component-table, and _bl-table.scss
/resources/views/components/bl/<x-bl.h1>Text for component</x-bl.h1>classNamesclassNames has some specific classes it accepts. Otherwise, developers can create their own classes and add them to their implementations. Just remember to separate by spaces. e.g. classNames="m0 p1" _normalize.scss and _bl-colors.scss files_bl-typography.css file should be used as wellIf any changes to a component's style need to be made, the changes should be made in its .scss file
The design components can be viewed on one place in a figma file.
The repo can be found on github.
Light grey links means demo incomplete