I’m using TailwindCSS as a CSS framework. It generates CSS classes definitions from the CSS classes present in the HTML.
If I configure TailwindCSS to look after the templates folder, it works fine. I use tailwindcss --watch, which generated its CSS to the static folder, and zola serve, which put assets in the public folder.
But when the CSS class names are dynamically generated by Zola macros, they’re not present in the templates folder: only in the public folder, where generated HTML files live.
Problem is: only zola build actually write those files, zola serve store them in-memory, thus making them inaccessible to tailwindcss. It would be super useful to store to have an option like --store-html to the serve subcommand for those kinds of workflows.
It took some tinkering to figure out the tailwind.config.
The following examines/process .html files in templates and .md markdown files in content dir. And the transform section preprocess or prioritize markdown that might contain html or css with tailwind classes.
In response to that hellishly long class name italic text-lg flex items-center font-title font-black text-green-tone-2 before:ml-8 before:inline-block before:w-0 before:h-0 before:border-y-[70px] before:border-l-[70px] before:border-y-transparent before:border-l-[red]
Yeah it has been quite easy, the Rust’s strong type model makes it quite easy to understand the code imo, though I’m not an experienced Rust dev. And Zola’s codebase is very clean. You can see my patch at the beginning of this thread! Took me ~4h, and it was my first time patching Zola.