# ExampleSite and Tailwind

**URL:** <https://discourse.gohugo.io/t/examplesite-and-tailwind/57534>\
**Category:** support\
**Created:** [September 8, 2026, 5:05pm UTC](https://discourse.gohugo.io/t/examplesite-and-tailwind/57534 "2026-09-08T17:05:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mriambez](https://avatars.discourse-cdn.com/v4/letter/m/ea666f/32.png) [@mriambez](https://discourse.gohugo.io/u/mriambez)\
**Post date:** [September 8, 2026, 5:05pm UTC](https://discourse.gohugo.io/t/examplesite-and-tailwind/57534/1 "2026-09-08T17:05:00Z")

</div>

I am facing the same problem noted here [Tailwind CSS Failing when running ExampleSite](https://discourse.gohugo.io/t/tailwind-css-failing-when-running-examplesite/57211). What is the Hugo way to run example sites?

---

<div class="post-metadata">

**Author:** ![irkode](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/irkode/32/26135_2.png) [@irkode](https://discourse.gohugo.io/u/irkode)\
**Post date:** [September 8, 2026, 8:39pm UTC](https://discourse.gohugo.io/t/examplesite-and-tailwind/57534/2 "2026-09-08T20:39:41Z")

</div>

Dunno if that is the _Hugo way_ but this works for me or at least the log prints something.

Windows 11 - PowershellCore 0.165.0  
see below for comments on 160.0

> Add `c:\path\to\SITE\node_modules\.bin`to `$env:PATH`

steps:

- followed [css.TailwindCSS](https://gohugo.io/functions/css/tailwindcss/) docs  
! the build stuff goes in the example sites `hugo.toml` !

- i did not copy the content but used a mount

- added `c:\path\to\SITE\node_modules\.bin`to `$env:PATH`

- i did not add any tailwind classes

- exampleSite Structure:

- `hugo.toml`

**log**

```auto
INFO exec: resolve "tailwindcss" location PATH bin C:\_path\to\SITE\node_modules\.bin\tailwindcss.cmd script C:\_path\to\SITE\\node_modules\@tailwindcss\cli\dist\index.mjs
INFO tailwindcss: ≈ tailwindcss v4.3.3
INFO tailwindcss:
INFO tailwindcss: Done in 18ms

```

* * *

with **v0.160.0** it works without path addition, but it tries npx to find tailwind which is allowed in 160.

```auto
  [security]
    [security.exec]
      allow = ['^(dart-)?sass$', '^go$', '^git$', '^node$', '^postcss$', '^tailwindcss$', '^npx$']

```

**log**

```auto
INFO exec: resolve "tailwindcss" using npx
INFO tailwindcss: ≈ tailwindcss v4.3.3
INFO tailwindcss:
INFO tailwindcss: Done in 15ms

```

and no – adding npx won’t help with 0.161+