This message was deleted.

GitHub

Airtable Interface!

We need a no-code specific GitHub @sticky-night-20812 😅 (I think I've seen a few people working on this!) @jolly-king-50317 Do you have a specific app that you've built to track things across different tools?

GitHub isn’t complicated, it’s just files and folders, you just need a good UI tool to do the commit/pull/push stuff. With files/folders, I store over 1000 formulas/rollup fields, all indexed by their name. Automations, too. Airtable, some Stacker configuration (scripts, css, etc.), Zapier, Make, PipeDream, everything goes into the GitHub repository, and I can find where a field is used across all those tools in a single cmd+f search. Simply marvelous, no other tool give me this kind of overview. Having databases over 2.5k fields, I couldn’t rename any field I had not this system in place. I wouldn’t be confident not breaking something.

That's super impressive, I'll admit I'm not great at documentation and it sounds like you've nailed it. Must save a lot of time in the long run.

Within Stacker tables, how about we start by adding an “Info” field to define and add meta data to the field’s column name and then offer up a “Manage fields” layout where this descriptive data is displayed and can be modified. This could include permission and dependency data like Airtable does too. The more Stacker self-documents, the better IMHO.

Yes, I like that idea. I think the thing I struggle with (that Ambroise has figured out a system for) is mapping out processes across multiple apps, eg Stacker / Zapier / Airtable / etc.

@sticky-area-45739 We did previously, yes. But to be totally honest we found using the Airtable Interface to be faster from a user-standpoint, and also simpler--we just didn't need a full blown Stacker app for it.

That makes sense, I tend to use Notion for simplicity for the limited documentation I do. Making it easy to update and read is key!