# Page label linked to columns

**URL:** <https://community.glideapps.com/t/page-label-linked-to-columns/86225>\
**Category:** Feature Requests\
**Created:** [February 2, 2026, 3:18am UTC](https://community.glideapps.com/t/page-label-linked-to-columns/86225 "2026-02-02T03:18:39Z")\
**Posts on this page:** 1\
**Showing post:** 5

<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:** [February 4, 2026, 6:50am UTC](https://community.glideapps.com/t/page-label-linked-to-columns/86225/5 "2026-02-04T06:50:52Z")

</div>

I think a simpler approach would be to use a **Rich Text component** rather than relying on URL fragments:

> [@brain CSS Hack: Dynamic CSS in Glide](https://community.glideapps.com/t/css-hack-dynamic-css-in-glide/85080):
>
> If you’ve been waiting for this feature request [“CSS Class Name” Field bound to data](https://community.glideapps.com/t/allow-css-class-name-field-to-be-bound-to-data/84977), it’s still unclear when it will arrive. In the meantime, here’s a workaround that turns the Rich Text component into a CSS-controlled state bridge — a way to make your app’s CSS respond directly to data, without JavaScript or visibility logic. This isn’t just a hack — it’s a new architectural concept born from Glide’s limitations. Here, CSS serves not only as a styling layer but as a logical layer that inter…

---

_[View the full topic](https://community.glideapps.com/t/page-label-linked-to-columns/86225)._