panas.reload VS girouette

Some of the bigger changes: - Code is now split up into a set of independent libraries. e.g. you can depend on the biff.crux lib if you want to use Biff's authorization rules or query subscriptions in an existing project. - Deployment is much simpler. Previously I was experimenting with a weird terraform setup where the config was managed by biff, but I decided it was more trouble than it was worth. Now there's just a bash script for provisioning an ubuntu server, including push-to-deploy. (Or you can stick the uberjar + env file wherever else you want). - Replaced Tailwind with Girouette! No more tooling needed outside the main clj process.

I seldom write CSS. I tried tailwindcss on one of my recent projects that required to closely follow a custom design (a portfolio for a graphic designer friend). I like it, with some caveats.

Main benefit for me is that I don't need to remember how to write css. 95% of what I need is a shortcut away from tailwind docs. The result is "prettier" than any other website-from-scratch I've done (that's purely on me, not much css practice). Now that I've memorised most common tailwind classes, I'm also moving faster than with pure css.

Main downside is that it's annoying having to modify tailwind's config file to add non-default variations (mostly different heights/widths than what it ships with).

Maybe something like Girouette[0] would be better.

[0] https://github.com/green-coder/girouette