# Documenting your app in Glide - a method using a tab + hints **URL:** \ **Category:** Project Showcase\ **Created:** [January 28, 2022, 12:51pm UTC](https://community.glideapps.com/t/documenting-your-app-in-glide-a-method-using-a-tab-hints/37819 "2022-01-28T12:51:40Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Mark\_Turrell](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mark_turrell/32/26605_2.png) [@Mark\_Turrell](https://community.glideapps.com/u/Mark_Turrell)\ **Post date:** [January 28, 2022, 12:51pm UTC](https://community.glideapps.com/t/documenting-your-app-in-glide-a-method-using-a-tab-hints/37819/1 "2022-01-28T12:51:40Z")
I have a team of developers working on the apps for my telemedicine service, and about 6 apps in the system. Some features or bugs can be fixed in minutes, others are more complex. There is still no Notepad functionality in Glide - which makes documenting or directing work highly tricky. So we have started to use a tab in the apps to record which bigger things need to get done, plus some info on what needs to get done (when it makes the cut). The way of doing it? A tab and then hints, using the color to denote status. Work-in-progress for us now - I hope this gives you all some ideas! ![Screenshot 2022-01-28 at 13.48.01](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/9/9/99f50cee25fa629e57ca60f1d2d30e41e37fc00d.jpeg) ---
**Author:** ![Jim\_McIntosh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jim_mcintosh/32/19235_2.png) [@Jim\_McIntosh](https://community.glideapps.com/u/Jim_McIntosh)\ **Post date:** [January 28, 2022, 1:02pm UTC](https://community.glideapps.com/t/documenting-your-app-in-glide-a-method-using-a-tab-hints/37819/2 "2022-01-28T13:02:23Z")
I’m creating a customer-facing roadmap page in my application that will link to a notion board and cards for this same reason. The page will allow all users to see, rank, and comment. When new items have updated a hint will announce the update. I’m taking ideas from @Robert_Petitto to build it ;-). (thanks for inspiration Bob) I’ll share when I’m done. ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [January 28, 2022, 1:05pm UTC](https://community.glideapps.com/t/documenting-your-app-in-glide-a-method-using-a-tab-hints/37819/3 "2022-01-28T13:05:33Z")
Interesting one Jim! ---
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [January 28, 2022, 1:30pm UTC](https://community.glideapps.com/t/documenting-your-app-in-glide-a-method-using-a-tab-hints/37819/4 "2022-01-28T13:30:01Z")
I’ve done something similar, albeit, a lot simpler. I have an area of my app with a text entry component that has visibility set so only I can see it. It’s easy to access through the side menu in the app, so as I find bugs or feature requests, I can update my “notepad”. Pretty simple in my case. I do like your use of the hint components for color coded statuses. ---
**Author:** ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)\ **Post date:** [January 28, 2022, 3:03pm UTC](https://community.glideapps.com/t/documenting-your-app-in-glide-a-method-using-a-tab-hints/37819/5 "2022-01-28T15:03:01Z")
@Jim_McIntosh Great idea! Would love to see the finished product!