Requiring Tailwind CSS in Hugo makes the build process very cumbersome. Using PostCSS, hugo_stats.json and the PostProcess transformation works, but is very complex and prone to errors.
The goal is to remove Tailwind altogether and use semantic CSS for the relatively simple style requirements. This also enables users to use the theme without Node.js, without strange config adjustments and such.
nicokaiser
commented
5 months ago
Requiring Tailwind CSS in Hugo makes the build process very cumbersome. Using PostCSS, hugo_stats.json and the PostProcess transformation works, but is very complex and prone to errors.
The goal is to remove Tailwind altogether and use semantic CSS for the relatively simple style requirements. This also enables users to use the theme without Node.js, without strange config adjustments and such.