No-code platforms rarely document well, and their rapid changes make technical docs obsolete fast. Instead of documenting the tool itself, capture the business logic behind your decisions using low-tech methods like mind maps and photos.
Documentation and no-code. The vast majority of no-code systems are way behind on documentation front. And part of this is because they are encouraging you to hack and make changes rapidly. Right? So it's only in much more recent iterations that we started seeing anything like version control or commit messages or encouraging people to create better labels for the, you know, steps they're building, say, we're in a Zapier workflow. These things are new and all these tools are also changing underneath our feet. That means any documentation artifact is going to be fairly transient. What you're looking for is your best understanding of what is the domain business logic that is used in decision-making in that tool. Because it's not about just what the technology is doing, it's about how it links to the business. I like to use mind maps. I will use whiteboards and take pictures. Whatever helps you record the state of your business.
