Avoiding need for postCSS and npm bits for hugo server about docsy-example HOT 5 CLOSED

ping @LisaFC

from docsy-example.

So the post-processed bits don't really exist anywhere (they're not in the repo as they're generated on the fly every time the site is built), so you do need PostCSS to generate the site for the first time. Once you've done it once you can run hugo server as many times as you like, or even commit the generated files to a repo if you don't want to have to use PostCSS in your regular build.

If you're really stuck someone (me?) might be able to create a copy of the site repo and push the generated resources to it.

from docsy-example.

I think that I'm asking a simpler question, namely:

• which generated bits do I need to commit to avoid running PostCSS every time (but still rebuild the rest of the site)?

The README makes it sound as if one only needs PostCSS if one changes the SCCS bits but it seems like it's always needed.

Thanks!

from docsy-example.

Ah gotcha! Ok, yes, you need PostCSS the first time you build the site (because otherwise it has eg no CSS files), and then after that you can commit/use the generated /resources/ folder and you should have everything you need (unless you change the SCSS and need to regenerate the files).

We used to do that as a workaround for CICD with Netlify before they upgraded their servers to support "extended" Hugo, and the Hugo docs site does it:
https://github.com/gohugoio/hugoDocs/tree/master/resources

from docsy-example.

Looks like just removing resources/ from the .gitignore will do what I'm looking for.

Thanks!

from docsy-example.