Igor Couto

Thank you for the quick feedback, @bdkjones! I have separate input/output directories for css and js files: - files from '/stylesheets' get compiled into '/css' - files from '/scripts' get...

I think I'm overlooking something obvious: if I have separate directories just for the input and output of **CSS files**, shouldn't Tailwind be ok? Or does Tailwind have a requirement...

Just a follow up: I've reviewed the Tailwind docs, and there does not seem to be a requirement on their side for us to use a 'build' folder. Tailwind seems...

> [...] That’s why the build folder is necessary in this case—so CodeKit knows what’s an output file and what’s an input file. Can't CodeKit determine that the same way...

Thank you for the explanation, @bdkjones! > [...] What MIGHT be possible is to allow you to override CodeKit’s automatic behavior and configure your purge list manually. That should work....

Either 'Build Profiles' as described by @luxlogica, or 'Project Templates' - a 'scaffold' project - as described by @bdkjones would be immensely helpful. The main idea being, that you can...

@bdkjones it may not be as complicated to implement as it might seem at first glance. The way that Parcel does it is roughly like this: 1. check the file...

AFAIK, the [new module system](https://sass-lang.com/blog/the-module-system-is-launched) in SASS consists of some new language additions - e.g., `use` as an alternative to `import` - which are all **optional**. From their announcement post:...

..or try converting your stylesheets to **[LESS](http://lesscss.org)**, or **[Stylus](https://stylus-lang.com)**. There are some [online tools](https://csspre.com/convert/) that can automate (most of) the conversion for you already.

> I would not recommend Less and Stylus. They don’t receive updates and development attention like Sass does. I think Sass has won that war, really. I respectfully disagree, @bdkjones...