As suggested in the title, when I deploy my site to Github (i.e. push to remote, triggering the github action to deploy) I’m seeing CSS that is different than what I have when I run hugo locally to develop my site.
I’m struggling to find out exactly what the differences are, but I think it’s that Tailwindcss from the theme is not being included in the CSS on the remote build. There’s an open Github issue in the Bento theme repo, but no resolution - I’m uncertain if there’s an issue with the theme or something else causing the problem.
I’ve seen some Hugo issues about no CSS at all, but that isn’t the issue here. It’s different, or incompletely generated CSS.
Your .gitignore file prevents the resources directory from being committed and subsequently pushed to GitHub.
If you change that, build locally, commit the changes and push, you do not need install Node.js as described above. It’s a matter of preference/performance.
The theme has a resources directory, and there is a resources directory in the root of your project.
But your .gitignore file ignores both due to the syntax you used. Lookup the effect of including/excluding leading and trailing slashes on .gitignore entries; it makes a difference.
If you don’t want to change the existing GitHub workflow to include npm build dependencies, you must commit the theme’s resources directory.