# TailwindCSS v3 support for classes within WP Block Attributes

**URL:** <https://forum.pinegrow.com/t/tailwindcss-v3-support-for-classes-within-wp-block-attributes/7192>\
**Category:** Feature Request\
**Tags:** feature-request, wordpress, tailwind\
**Created:** [November 9, 2022, 10:17pm UTC](https://forum.pinegrow.com/t/tailwindcss-v3-support-for-classes-within-wp-block-attributes/7192 "2022-11-09T22:17:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ThatWebsiteIsMe](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/thatwebsiteisme/32/4635_2.png) [@ThatWebsiteIsMe](https://forum.pinegrow.com/u/ThatWebsiteIsMe)\
**Post date:** [November 9, 2022, 10:17pm UTC](https://forum.pinegrow.com/t/tailwindcss-v3-support-for-classes-within-wp-block-attributes/7192/1 "2022-11-09T22:17:18Z")

</div>

Currently (to my knowledge), Pinegrow does not look through WP Blocks for TailwindCSS classes to add to the tailwind.css theme file or the tailwind\_for\_wp\_editor.css theme file.

Requesting these feature to be added so that moving to a block based theme allows for class dropdown/toggle options to be included and displayed.

The temporary workarounds (thanks to Benjamin on Facebook) are:

1. Running own compiler - Safelist classes: [Content Configuration - Tailwind CSS](https://tailwindcss.com/docs/content-configuration#safelisting-classes)
2. Using Pinegrow’s build in JIT compiler - “add the classes to a page that you don’t export so that PG will find and include your classes in your tw-css file like it does for other classes.”

if anyone knows of another workaround please let me know.