Coda Subfolders + Public Feature Roadmap

[June_Parent1]

Since 2020, many users, including myself, have requested and/or voted for a subfolder feature. This persistent limitation is frustrating to work around using non-ideal, time-consuming half-solutions. There have been several occasions where I’ve started new workspaces in Notion just to avoid this issue.

This limitation is particularly problematic for businesses considering Coda as their primary workspace. Despite my efforts to promote Coda to various organizations, many ultimately choose Notion due to its sidebar spaces/folder/subfolder organization.

Despite multiple requests from users over the years, it’s unclear if or when subfolders will be added to Coda. While the new Quick Nav is a nice quality of life addition, it is not functionally effective without subfolders.

I share a strong suggestion to implement subfolders, please. Next, I share a suggestion for public features roadmap.

[drussell]

wondering if this was ever implemented?

[Piet_Strydom]

You can use the Coda list pack to achieve a much more flexible solution.

[Melanie_Teh]

@drussell

if you could give us a little more context in what youre trying to achieve / end goal- maybe we can provide better insights as to how best to execute/overcome coda hierachy/folders in current form?
sometimes its a case of acclimatizing to new platform and getting your head around working in a slightly different way i.e. same outcome, but different road to get there

There’s locking on the folders - would that work for your needs?

looking forward to your thoughts

cheers!
Mel

[drussell]

Thanks Mel! We have folders for each Client we work on e.g. [Client Name], but then within that folder is just a loooooong list of docs. We would like to have subfolders within each [Client Name] Folder so we could organize by [Project A] [Project B] etc, just like folders on your computer

[Melanie_Teh]

@drussell

recently there’s been quite a few discussions concerning this topic…
While there are no sub folders currently in coda, workarounds include creating a Master Doc with links to each doc you would have in a folder.

All Docs in one (1) Doc? | Any issues?

Hello! I’d like to put all my docs, into one doc and make subpages instead of separate docs and folders. Then for permissions and view based pages, I would then create a separate Docs and cross doc the pertinent information. Are there any issues with this, tables, permissions, etc? Why would I do this? ) Current system of just added docs is too messy to me. 2.) Having one file system of sub pages is so much quicker to toggle through information. 3.) Docs are big clunky buttons to me so t…

Folders vs Documents

There are often some questions about Coda’s lack of a folder structure. Coda has several methods that are much better than a (hierarchical) structure. You can create a “King” document as Max from @Agile_Dynamics calls it, OR you can make use of the Coda Pack called Coda Doc List. This will create a table in a doc, which you can sort, filter, capture metadata, create views, each one gives you an order of magnitude better functionality than the older, static, hierarchical folder structure. B…

these threads delve in more detail.

hope this helps!
cheers!
Mel

[Piet_Strydom]

@drussell

Trying to better understand your situation: Why do you have a doc per project, and not all projects in a single doc?

P

[AJM]

I can’t speak for them, but not all projects can fit into a single doc. I have a doc that is fairly simple but contains 60K rows and is already close to maxing out. I’m having to look for a different platform that can contain more rows. So, not all projects can fit in a single doc.

[Piet_Strydom]

There are two packs that address row limitations, one for snowflake, the other for Xero if I remember correctly.

[AJM]

but then I may as well just use one of those instead of coda since I need access to all the rows.