![]() ![]() ![]() I remove the 'build' folder, and move all the files - php templates, css stylesheets, etc. I then turn off "this project uses a build folder" in 'Build Process' settings. I can make edits to my templates in the 'source' folder, and immediately preview the results in the outputted corresponding file in the 'build' folder. If I use the 'source' + 'build' folder approach, everything works fine, and I can use all of the JIT compiler features without a glitch. I have a Tailwind-based CodeKit project, where I use the JIT compiler. But this approach doesn't seems to work with Tailwind projects. This is not a problem when using "traditional" frameworks - like Bootstrap, Foundation or UIKit: I can just set CodeKit not to use a build folder, and then specify the output directory for all files in the project's settings, carefully, manually. So, using a 'build' folder in CodeKit is never an option. css stylesheets, have to be placed in very specific folders in order for me to not cause bugs or give unnecessary extra work to the Backend Developer. These templates/partials are often added to the CMS as a 'plugin', and along with their compiled. #Codekit tailwind codeI'm usually editing html code and editing css classes directly inside a. ![]() These projects require all my frontend 'theme'/'template' files, as well as my css/js files, to be placed in very specific folders. I'm working as a Frontend Developer on full-stack dynamic websites that use php-based CMSs. Without using 'source' and 'build' folders, however, CodeKit seems unable to recognise which classes are actually used in my php templates, and fails to compile Tailwind's CSS files appropriately. #Codekit tailwind softwareThe Laravel framework is open-sourced software licensed under the MIT license.I'm trying to use Tailwind and CodeKit with a PHP-based CMS site, and can't use a 'build' folder. If you discover a security vulnerability within Laravel, please send an e-mail to Taylor Otwell via All security vulnerabilities will be promptly addressed. In order to ensure that the Laravel community is welcoming to all, please review and abide by the Code of Conduct. ![]() Thank you for considering contributing to the Laravel framework! The contribution guide can be found in the Laravel documentation. If you are interested in becoming a sponsor, please visit the Laravel Patreon page. We would like to extend our thanks to the following sponsors for funding Laravel development. Boost your skills by digging into our comprehensive video library. Laracasts contains over 1500 video tutorials on a range of topics including Laravel, modern PHP, unit testing, and JavaScript. If you don't feel like reading, Laracasts can help. Laravel has the most extensive and thorough documentation and video tutorial library of all modern web application frameworks, making it a breeze to get started with the framework. Laravel is accessible, powerful, and provides tools required for large, robust applications.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |