I honestly prefer to use this approach: 1. Install Laravel composer create-project laravel/laravel example-app 2. Use in project folder npm i bootstrap 3. Copy the css and js folders from the following locations -node_modules/bootstrap/dist/css -node_modules/bootstrap/dist/js 4. Paste the css and js folders into the public folder 5. Insert the links into the layout file
@@CODINGISEASY Yeah, but this way i still prefer having clean component with just 1 class and the css logic separated ! But this is my own preference !
I use Bootstrap. I have looked at Tailwind, and for me, it is exceedingly verbose. I have no interest in having my site appear to be "unique". All I need is functionality. It does not solve any problem. Lastly Tailwind represents just more time learning. I can use that time more productively doing something else.
I still use Bootstrap. It is improving significantly, over the coming releases Bootstrap will be getting native Dark Mode support and ability to control themes which should help one of the major pain points of Bootstrap.
Thank you! I believe many people still use Bootstrap, including myself. Therefore, if you show on the project how you connect styles and js files from an already laid out site design, it will be great.
From the beginning, I started using Bootstrap, and even after years, I still use it. The difference now is that I compress or defragment the source code to only use the components that I need, instead of using everything. For example, the following video helped me do that: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-6onN1FC3__A.html.
I would argue the beginning part stating tailwind is NOT part of laravel. While technically correct it is a waste of time. I wonder how many people fast-forwarded through that. It's about perception and 100% pushing towards tailwind. Otherwise there would be options like when installing Breeze (for example). So saying it's not included by default is fine, but who really uses the default outside of an api?
Laravel UI is the official one. There was also unofficial one called Jetstrap: github.com/nascent-africa/jetstrap - but it seems to be abandoned, with last commit over a year ago
Just run 3 lines of code in your terminal. Install bootstrap auth 1) composer require laravel/ui 2) php artisan ui bootstrap --auth 3) npm install 4) npm run dev
I find tailwind better for apps where you create components. You build the components with the classes so then once you make a component you dont have to keep repeating all those classes. Like if you had a vue or blade component for a button you can build the button once with all the components then just include it and pass it the text and href each time. Then if you need to change the style you only need to edit your button component. If that makes sense?
I agree with anyone that states that it's a personal preference. Also tailwind css could be a project technical requirement. In this way learning it for you will be a necessity instead of just an option. Wich I've is better? That will always depend on who is implementing it
