# Tailwind's arbitrary variant syntax not working with Hugo

**URL:** <https://discourse.gohugo.io/t/tailwinds-arbitrary-variant-syntax-not-working-with-hugo/45437>\
**Category:** support\
**Created:** [July 24, 2023, 10:25pm UTC](https://discourse.gohugo.io/t/tailwinds-arbitrary-variant-syntax-not-working-with-hugo/45437 "2023-07-24T22:25:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![AlanBreck](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/alanbreck/32/11694_2.png) [@AlanBreck](https://discourse.gohugo.io/u/AlanBreck)\
**Post date:** [July 24, 2023, 10:25pm UTC](https://discourse.gohugo.io/t/tailwinds-arbitrary-variant-syntax-not-working-with-hugo/45437/1 "2023-07-24T22:25:22Z")

</div>

When attempting to utilize Tailwind’s [arbitrary variants](https://tailwindcss.com/docs/adding-custom-styles#arbitrary-variants) syntax, `hugo_stats.json` seems to encode the `&` and `>`, and breaks Tailwind’s ability to recognize these classes in and build the rules.

E.g. a class of `[&:nth-child(2)>figcaption]:bg-black` results in `"[\u0026:nth-child(2)\u003efigcaption]:bg-black",` in `huto_stats.json`.