I have never heard about files like .blade.css only .blade.php.
Usually all your assets (js,css,etc) should be in /public/assets.
Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
I'm new to Laravel, but have already made up my mind to shift my existing project to Laravel and need some suggestions/tips on planning the template hierarchy.
My main app will be a 'play store' for various web apps: like 'Events Listing', 'Job Board', 'Restaurant Finder' etc. While the overall look and feel will be consistent using bootstrap each app will require its own JS and custom CSS. My plan is this :-
Have master.blade.css : Will have the code for site wide bootstrap + navigation + footer.
Create subfolders for each set of templates viz. /events/ , /jobs/ , /restaurants/ etc. Each folder will have templates specific to the app, like /events/create.blade.php. These templates will extend the master layout.
This looks a very straightforward approach to me. Could you please let me know if there's any better way? Would welcome any comments, suggestions, tips et al. I'm still learning and hope to benefit from your comments.
Thank you for your time in advance.
Please or to participate in this conversation.