![]() ![]() So, in summary: it seems there is no requirement from Tailwind for us to have a 'build' folder. We should see Tailwind generate the '/css/main.css' file as expected, now including our '.extratopmargin' class. Npx tailwindcss -i './stylesheets/main.css' -o './css/main.css' -watch Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread. 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. I'm trying to use Tailwind and CodeKit with a PHP-based CMS site, and can't use a 'build' folder. Is there a way to use CodeKit + Tailwind without using a 'build' folder? Have I overlooked something obvious? Although the stylesheet is still being compiled every time I save a change to my template - CodeKit recognises that there is a change, and recompiles the stylesheet at the expected location - it seems CodeKit fails to 'see' the Tailwind classes I'm using in the template, and none of them get added to the outputted stylesheet. ![]() Now, however, when I preview my document, the output is broken: none of the Tailwind styles are being compiled into the production stylesheet. I then change all the remaining preferences in CodeKit, to set the output paths to the appropriate directories for that CMS - eg., 'output all CSS files to /assets/css'. out of the 'source' folder, and into the "right" folder, where they are supposed to be, according to the dictates of whatever CMS I'm working with. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |