What are best practices for structuring your Cross-doc system?

So, what goes to a separate doc? What are the criteria you use?

Although Codans have hinted that this is something that is being worked on, one of my main criteria is permissions, since docs cannot have permissions set granularly to pages within a doc. For example we separate out Interviews into a separate doc from our main Hiring doc, which contains more sensitive or valuable information. Thus those that are conducting interviews only have access to the data they need.

The other main criteria is separating concepts or responsibilities. In general we try to keep each doc focused on a particular goal or area. Given the flexibility of Coda this can result in blurred lines, but for example we have separate docs for Hiring, Deals, Contracts and Management. Each project gets its own doc, however these are for relatively small projects (3-5 people).

Another final criteria is performance, but this is harder to reason about.

1 Like

Hey! This answer still holds:

Also check out this recording of my lecture about cross-doc best practices:

1 Like

Thanks, I wasn’t aware that any viewer can copy a doc. That means I have to split some stuff into separate docs.

Thanks! That makes it clearer!

You can actually disable copy now, which should stop most of the bad actors. But the principle remains: the whole doc gets loaded into one’s browser, and with some tenacity it’s possible to extract all the data out of that doc. It’s encoded but any half-decend dev would immediately figure out how to decode it.

E.g. I used this simple script a while ago to check on what was taking space in some critical docs of my clients. Now it’s more complicated than that because of doc sharding, but doable just like that.