Followup Tailwind And Status

Not that anyone cares, I’m doing this as a kind of public journal and a way to keep myself honest, and continue to post, even when not much of note has happened.

tailwindcss

For some reason, I wasn’t able to find a super quick feedback cycle that I was happy with, with the node-based solutions to working with tailwind. I didn’t try the full bare-bones, tailwind cli, as I’m not sure how to integrate that into my jekyll setup.

The solution

One thing that I did find acceptable, was to use a rails 6 app, using both webpacker and asset pipeline. While changes to the base css files were non- instantaneous, fast feedback cycles are achievable by using sprokets/asset pipeline, and guard to auto reload (along with rack-livereload and guard-livereload) and then move or refactor to the css files once things look reasonable.

The goal is to hit save (CTRL-s) and have the browser automatically refresh. Saves time, saves wear and tear on your RSI-ridden limbs and keeps you in the zone.

Lets gooooooooooooo