improve css tooling

[rossPatton]

we should consider adopting the tailwind/postcss/jekyll build system im using over in https://github.com/emergentworks/project-not-911/tree/master/docs which is also a jekyll site, but uses a more modern (and performant) css approach

[shushugah]

What’s the before/after benefits in terms of deployment speed, and pros/cons in terms of development/tooling? From my point, with Jekyll 4, the builds are incredibly fast themselves, though Netlify deploy is slow for new branch/PR due to initial sassc installation.

[rossPatton]

well we'd get a very easy to use css framework that is customizable to our needs, with automatic css purging built-in which would mean we'd only bundle the classes that are actually used by the site, keeping things performant

i also feel that writing css rules is a huge waste of time, tailwind would remove that as a thing we need to do

i haven't noticed any really noticeable change in build speeds for the not911 project after adding it