# Best practices for PostCSS generation

**URL:** https://discourse.gohugo.io/t/best-practices-for-postcss-generation/28840
**Category:** support
**Tags:** tailwind
**Created:** [October 16, 2020, 5:42am UTC](https://discourse.gohugo.io/t/best-practices-for-postcss-generation/28840 "2020-10-16T05:42:07Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![divinerites](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/divinerites/32/12625_2.png) [@divinerites](https://discourse.gohugo.io/u/divinerites)
#### Post date: [October 16, 2020, 11:12am UTC](https://discourse.gohugo.io/t/best-practices-for-postcss-generation/28840/8 "2020-10-16T11:12:16Z")

</div>

> [@divinerites](#):
>
> I think I remember vaguely Bep talking about using modules for providing CSS, but I never tried this.

As a side note, this is the post I was thinking about.

> [@Including javascript lib from node modules](https://discourse.gohugo.io/t/including-javascript-lib-from-node-modules/25427/2):
>
> To use load resources via resources.Get etc. from node\_modules you need to mount them into your project (typically /assets, but you may need to mount the fontawesome fonts below /static). Also note that if you’re not a big fan of NPM, you can mount GitHub projects directly, or use prepared Hugo Modules, e.g.

---

_[View the full topic](https://discourse.gohugo.io/t/best-practices-for-postcss-generation/28840)._