Still in the context of Consider using Hugo Pipes for the CSS and adding functionality for custom CSS overrides · Issue #379 · theNewDynamic/gohugo-theme-ananke · GitHub I’m trying to make sure users don’t need npm/postcss unless they want to customize the style.
For any given project, I know Hugo will look for the asset in the
resources directory if PostCSS is not installed. But it seems to
resources dir is not part of Hugo’s unison file system. So it has to live on the project level.
Before I dig into working a theme setting and logic to allow users to choose from preprocessed or “process yourself” asset, has anyone found a workaround for resources committed to the theme to be available to the project?