# Allow “CSS Class Name” Field to Be Bound to Data

**URL:** <https://community.glideapps.com/t/allow-css-class-name-field-to-be-bound-to-data/84977>\
**Category:** Feature Requests\
**Tags:** custom-css, custom-code\
**Created:** [October 19, 2025, 9:42am UTC](https://community.glideapps.com/t/allow-css-class-name-field-to-be-bound-to-data/84977 "2025-10-19T09:42:30Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Himaladin](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/himaladin/32/71023_2.png) [@Himaladin](https://community.glideapps.com/u/Himaladin)\
**Post date:** [October 19, 2025, 9:42am UTC](https://community.glideapps.com/t/allow-css-class-name-field-to-be-bound-to-data/84977/1 "2025-10-19T09:42:30Z")

</div>

I suggested this idea back when Glide.app switched to Glide.page, but I can’t seem to find that old thread anymore.

It would be awesome if the **“CSS Class”** field could be **bound to a column in the Glide Table** — this would unlock **dynamic CSS** , allowing components to automatically change styles based on data updates.

For those who often use custom CSS, imagine being able to make your UI respond directly to your app’s logic and data — a big step toward making Glide both visually and logically data-driven.

 ![b721d1f0ebf12b8d759827fbd03837dbde2f84c5_2_1035x399](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/f/6/f6645d0bb2a3e29dc9a02a7d1715e6a0edfdb1da.png)

If you think this would be useful, please give it a vote 👍  
I’m also working on a dynamic workaround for this — will share it soon. Stay tuned!

---

<div class="post-metadata">

**Author:** ![Mazen](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mazen/32/84042_2.png) [@Mazen](https://community.glideapps.com/u/Mazen)\
**Post date:** [October 19, 2025, 2:02pm UTC](https://community.glideapps.com/t/allow-css-class-name-field-to-be-bound-to-data/84977/2 "2025-10-19T14:02:46Z")

</div>

That’s a great Idea! Voted.

---

<div class="post-metadata">

**Author:** ![Laurence\_Schuberth](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/laurence_schuberth/32/65729_2.png) [@Laurence\_Schuberth](https://community.glideapps.com/u/Laurence_Schuberth)\
**Post date:** [December 23, 2025, 7:38pm UTC](https://community.glideapps.com/t/allow-css-class-name-field-to-be-bound-to-data/84977/3 "2025-12-23T19:38:31Z")

</div>

Totally agree, have always thought that would be an awesome idea, even if it’s just a boolean to start with, would be awesome to have “If yes” then green “If No” the red (as a simple example) I expect CSS wizards can do i,t but it does my head in 😂

---

<div class="post-metadata">

**Author:** ![Himaladin](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/himaladin/32/71023_2.png) [@Himaladin](https://community.glideapps.com/u/Himaladin)\
**Post date:** [December 24, 2025, 12:53am UTC](https://community.glideapps.com/t/allow-css-class-name-field-to-be-bound-to-data/84977/4 "2025-12-24T00:53:16Z")

</div>

Even beyond binding class names to data, having a way to inject custom attributes would open up more expressive CSS patterns, while still keeping the model simple. Custom CSS isn’t a workaround; it’s a necessary expressive layer that complements and refines Glide’s visual builder for complex, data-driven styling.