Coda docs start small, but get larger as teams grow and they put more information into their doc. That's why Pages 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 page list - like most things in Coda, use whatever system works best for you. However most of our Coda docs have a hierarchy of pages and subpages that orient the user to how to use the doc, and there are a few best practices we can share:

This is the top page of the Coda doc, and orients anyone using it to what the doc is for. Often this page contains the purpose of the doc, who has access to it, and a Table of Contents of the remaining pages.

It's often a good idea to have a 'Data' page. Here you can put multiple subpages, each of which contains a table. Often, 'Data' pages will be raw tables, and prettified views of information will live elsewhere. Some people put the 'Data' page at the bottom of the document, others at the top.

To keep your doc compact and scannable, you might consider hiding your 'Data' page.

Team Views
Next you'll include a number of subpages 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 page, under which are subpages for elements that team works on — for example, one for tasks, another for meeting notes, another few for personal views.

Additional Views
As Coda docs get bigger, users typically move subpages and pages by theme - for example, if the Design team has a number of pages, their pages are organized together, and Engineering's are further down the subpage list, etc.

You can nest subpages as deeply as you like within top-level pages.Consider creating a hierarchy in this way to keep your doc easier to navigate.

Tips and Tricks
As your subpage and page list expands, it's helpful (and fun) to add emojis to the names of some of them, to make a subpage and page stand out visually.

Related Articles:

Using Pages and Subpages

How do I get the most from Pages?

Did this answer your question?