Skip to content

A barebone Hugo starter with Tailwind 3.2.* - Build your own theme on top.

Notifications You must be signed in to change notification settings

4044ever/Hugo-Tailwind-3.2

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

67 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Hugo & Tailwind 3.2 (now 3.4.1!)

A barebone Hugo & Tailwind CSS 3.2.* starter kit

Install to VS Code with:
git clone https://github.com/4044ever/Hugo-Tailwind-3.2 optinal-foldername
npm install

To start developing:
npm run start

To generate the site HTML:
npm run build

npm run start will run two commands parallel:
npx tailwindcss -i ./assets/css/main.css -o ./assets/css/style.css --watch

and hugo server

Note: You do not have to install Hugo with Hugo new site hugofolder ! But you need to have the Hugo environment running!

Note: When you start first time npm run start a style.css must exist - or you get an error! Just do a Ctrl+c and run npm run start - even though you got an error but a style was written anyway and 2nd time round it should start fine.

To get out of developing mode you need to do Ctrl+c twice.

Disclaimer: This is my personal try with Hugo and Tailwind 3.2.* To me it looks like all functions work, classes get updated, a correct /public/ folder with purged, minified style*.css gets created. Seems production ready, you can build a theme around it. Leave a comment if you see errors or improvements.

Hugo Note: Tested up to/with Hugo 0.121 extended. So far all new Hugo version worked for me.

So what changed?

  • I updated to the latest TailwindCSS 3.4.1
  • I removed concurrently and changed to npm-run-all, does not really makes a difference though
  • Removed autoprefixer and postcss, seems they are no longer required

About

A barebone Hugo starter with Tailwind 3.2.* - Build your own theme on top.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published