Folders in the library

The library is no longer one long list. Documents live in folders, folders can nest, and an empty folder can exist before you put anything in it.

A tree, not a pile

The sidebar is a folder tree. Pick a folder and the list shows that folder and everything under it. Drag a document onto a folder to file it. Drag a folder onto another folder to nest it, or drop it at the root to pull it back out.

You can add a folder without publishing a dummy note into it, and you can delete a folder. Deleting asks what to do with the documents inside: move them up, or remove them with the folder.

Where a note sits

A document still has a title. The folder is just the place it lives. File “Meeting notes” in Work/Client A and the stored path is:

Work/Client A/Meeting notes

A slash in a title becomes -, because a slash is how nesting works. Two notes with the same title in the same folder become Meeting notes and Meeting notes 2. The title you see stays the same.

Leave the folder blank and the note sits at the library root. That is not a fake folder named Library. The path is just the title.

Collections are unchanged. A note can live in Work/Client A and also appear on a public collection. A folder is where you keep it. A collection is how you share a set of posts.

Picking a folder when you publish

The editor has a folder menu instead of a path you type by hand. Choose an existing folder, or add a new one. The note’s name in that folder comes from the title.

On the API, folders are their own records, so an app can list them and create Inbox without uploading a file first. Identity is the path string. Work/Client A creates Work on the way if it is missing.