Coda docs start small, but get larger as teams grow and they put more information into their doc. That's why Sections can be a handy way to organize your Coda doc.
We'll start by saying there's no hard-and-fast rules about organizing your Section list - like most things in Coda, use whatever system works best for you. However most of our Coda docs have a hierarchy of folders and sections that orient the user to how to use the doc, and there are a few best practices we can share:
This is the top section of the Coda doc, and orients anyone using it to what the doc is for. Often this section contains the purpose of the doc, who has access to it, and a Table of Contents of the remaining sections.
It's often a good idea to have a 'Data' folder. Here you can put multiple sections, each of which contains a table. These tables drive views throughout the document. Some people put the 'Data' Folder at the bottom of the document, others at the top.
To keep your doc compact and scannable, you might consider hiding your 'Data' folder.
Next you'll include a number of sections with unique views of the data table(s). If it's a big Coda doc with multiple teams using it, you'll likely have each team with their own folder, under which are sections for elements that team works on - for example, one for tasks, another for meeting notes, another few for personal views.
As Coda docs get bigger, users typically move sections and folders by theme - for example, if the Design team has a number of folders, their folders are organized together, and Engineering's are further down the section list, etc.
Tips and Tricks
As your section and folder list expands, it's helpful (and fun) to add emojis to the names of some of them, to make a section or folder stand out visually.