Best practices for documenting programming in a glide app

I wondering what ya’ll have found to be the best way to add details to columns so future editors can read what the columns are doing? I’m already circling back to things on my app and struggling to remember which other tabs and columns are using the data from given column and why things are set up the way they are. I had a habit of adding notes to cells in Google Sheets but that doesn’t help me with relation, lookup, template columns and the like. I’m also seeing some columns that seem to be redundant or obsolete as we’ve evolved but I’m afraid things will break if I delete them.


I once put a feature request similar to this…

I am not sure if it got any votes

  • I try to make my column names as descriptive as possible.
  • I also use a consistent naming scheme, especially with calculated columns.
    So all my relations are named rel-xxx, all my lookups are named lk-xxx, all my math columns are named mth-xxx, etc.
  • I also spend a fair bit of time re-arranging columns, so that they follow some sort of logical order from left to right.

What I’d like to see is just a way to click on a column and see all of the other related columns and components that are affected by that column. It seems like they already track that because your can rename a column and it’s handled in every other affected column and component.

  • 1000 Votes
1 Like

Since I used Glide at first time I missed that feature, I know it as X-Ref and in many software it is a classic tool and almost a must.