# Would be great to have developer names (variable names) to components

**URL:** <https://community.glideapps.com/t/would-be-great-to-have-developer-names-variable-names-to-components/19477>\
**Category:** Feature Requests\
**Created:** [December 7, 2020, 5:54am UTC](https://community.glideapps.com/t/would-be-great-to-have-developer-names-variable-names-to-components/19477 "2020-12-07T05:54:05Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [January 30, 2021, 3:25am UTC](https://community.glideapps.com/t/would-be-great-to-have-developer-names-variable-names-to-components/19477/5 "2021-01-30T03:25:44Z")

</div>

Here is a hack you can use to create labels for Rich Text components.  
Every little bit helps… 🙂

> [@Tip: Custom Labels for Rich Text Components](https://community.glideapps.com/t/tip-custom-labels-for-rich-text-components/19105):
>
> I just discovered a neat little trick to help identify rich text components in the builder. There appears to have been a change made recently wrt to component labels that makes them easier to identify by eyeballing. It seems that most components will now use either the data source, title or description as the label. In the case of Rich Text components, whatever the content starts with is used as the label (or as much of it as fits in the component label box). Armed with this knowledge, you can…

---

_[View the full topic](https://community.glideapps.com/t/would-be-great-to-have-developer-names-variable-names-to-components/19477)._
