Newsletter
Join the Community
Subscribe to our newsletter for the latest news and updates
A minimal Hugo boilerplate that integrates Tailwind CSS Just-in-Time compilation via npm scripts.
Hugo Tailwind JIT is an open-source boilerplate template that integrates Tailwind CSS's Just-in-Time compiler into Hugo's static site build pipeline. It provides a minimal starting point for developers who want to use Tailwind utility classes in Hugo without assembling the toolchain themselves.
Hugo Tailwind JIT is a template repo that wires Tailwind's JIT mode into a Hugo project through npm scripts. It takes a basic Hugo site as input and produces a static site with a Tailwind-generated CSS file as output. The template runs on Node.js for the Tailwind build and requires Hugo installed separately. The original repository is published on GitHub, though the exact author is not named in the README.
npm run dev starts the Tailwind watcher; hugo server runs Hugo's development server in a second terminal tab, giving live reload for both content and styles.npm run build && hugo --minify compiles Tailwind once and then builds a minified Hugo site for deployment.npm install, with the Tailwind CLI and Hugo invoked through npm scripts.npm install to install Tailwind and any npm dependencies.npm run dev to start the Tailwind watcher.hugo server to serve the site locally.npm run build && hugo --minify to generate a minified static site.The Tailwind watcher regenerates the CSS file whenever a template or content file changes, while the Hugo server handles live reload for the site itself.
The repo provides a minimal Hugo project layout rather than a specific theme, so Tailwind JIT can be layered onto your own Hugo templates and content structure.
JIT generates only the CSS for utility classes found in your source files, which typically produces a smaller stylesheet than a full Tailwind build and skips the step of scanning for unused styles.
It runs the Tailwind build once to generate the final CSS and then executes hugo --minify to produce a minified static site ready for deployment.
Yes — during development the Tailwind watcher regenerates CSS as you edit, while the Hugo server provides live reload for content; they run as two separate processes.
