I’m having similiar issue on a huge doc on coda
I have to deal with users that want to edit the coda app, but i have to tell them somewhere how the app works, how i designed and “coded” it (formulated? )
I should document my app, without wasting time in doing so and in a future-proof way (like dynamic)
What if i could use the Doc Map for doing so?
p.s. @Paul_Danyliuk what if the doc builder and the user werent the only “users”?
What if i need a third type of user that is not gonna build the entire doc, but that wants to be able to understand or modify formulas?
it’s the cool approach of coda, i built it, you play with it and then you modify it
But i have to create a safe zone in which this can happen, where my work cannot be copied or redistribuited, and what better space than coda doc itself? already protected, with version history for users and all kind of useful tool
This third type of user need to understand formulas (all your suggestion about formatting and organizing are already applied in my case ), doc design and doc map.
And i think that creating a static .rtf is not respectful of coda’s nature of being an intuitive and dynamic tool, why not take advantage of already existing doc map?
It could be a great tool for building dynamic documentation for explaining how the doc is builded and designed
My suggestion will be to display all the tables in the first view, so i can see the primary tables and also the subtables below the parents, having all the schema in one page (see doc map for live examples)
It’s easy to sketch a “mind map” of a doc if it have 3 section and 5 tables, is harder in situation like mine
Where all those tables are linked in someways to eachother, i would have a really hard time in explaining how that work to an experienced user, how could i explain that to every “more interested than average in tech aspect” users?
Do you have any ideas regarding those aspects?