Member-only story
Can Coda docs behave as databases?
The advantages of well defined and interlinked data containers
When I explain my Coda approach, I tend to present docs as databases. Why I do that, I try to explain in this blog using the concept of core docs and secondary docs. I conclude that you save money and time by showing results before expanding.
Before we dive into the matter, you should understand that Coda is as much about the tool as it is about a way of thinking. It is an approach to process data. Once you learn how to Coda, you learn how to review your processes. The formula language, the actions, the packs and all the rest is secondary to the question: “how to create process that work for me instead of me working for the processes.”. Time to get started!
The doc as a database
Docs blend structured and unstructured data. Tables represent mostly structured data, while the canvas is mainly used to store and show texts and images: unstructured data.
The essence of a database is to provide a structured and efficient way to store, manage, and access data.
Strictly speaking, docs cannot be databases. Not all data in a docs is structured and can be retrieved. Nevertheless how we deal with docs comes close to the core concepts of a database:
