With pages, collapsible content and related features, your options for organizing your doc are vast and varied. If the weight of options has you a little stuck when it comes to structuring your doc, here are some recommended ways to use pages to help you decide how to organize your information.
Use cases for pages:
Use a top-level page as the central hub for a project or team, with subpages for supporting details
Providing an intro or broadly helpful resources like a roster on your top-level page can help collaborators navigate both your project and your subpages. Your top-level page could have things like your main goals, guiding principles, or aggregated metrics, while your subpages have tables and information to help individuals or smaller teams contribute.
Top-level page more like a folderーa container with no content of its own
Sometimes you just need one place to aggregate relevant information. Maybe you have collections of meeting notes, or drafts of different assets that need their own space to come to life, but you don't have a need to roll-up a key insight or top-line view of them. That's okay! Top-level pages work just fine as containers for pages nested within them.
Structure your doc as a wiki, with as many levels of subpages as you need
Organizing an entire team or company in a doc is a powerful way to ensure everyone has access to vital information, and can contribute to keeping documentation, standards, processes and resources up-to-date. Because pages can nest for an infinite number of levels, teams or departments can break out information as granularly or broadly as needed.
🌟 Coda Tips 🌟
Highlight your comprehensive data in a table on a top-level page, and use subpages for custom views of that data
It can be helpful for teams to have access to a comprehensive set of data, whether that's the status of all project tasks, a detailed roster for an entire team or other specifics. However, teams might also want to easily access the most relevant details, such as the tasks belonging specifically to their team.
Consider using a top-level page to provide visibility into the complete data or information, and using subpages for each team to filter, group or view the data in the way that works best for them.
Limit the number of top-level sections and trust viewers to intuitively navigate and drill-down to find the desired content
Dividing subpages across a high number of top-level pages can result in an unintentional game of hide-and-seek. If it feels like you're "splitting hairs" to determine where to host a subpage, consider consolidating some top-level pages to avoid unnecessary complexity.
Nest everything under a single top-level page to facilitate doc navigation without using the left sidebar
With the subpages header and breadcrumbs at the top of your pages, nesting everything under a single top-level page gives viewers a "home" page to return to when they navigate.
🎶 You can go your own way! 🎶
There's no "wrong" way to use pages. Let your doc grow as your team, project or application does, and be sure to take advantage of tools like page outlines, drag-and-drop editing and collapsible content to reorganize your information as you desire.