Organizing with Markdown Folders

Glyph stores your notes as plain Markdown files in folders. Use folders for structure, tags for cross-cutting labels, and properties for boards. Keep the tree simple so you can find files outside the app too.

A practical recipe

1. Folders for projects and areas

Create folders that match how you work:

Projects/
  Glyph/
  Website/
Areas/
  Health/
  Finance/
Journal/
Templates/

Put project notes under the project folder. Put ongoing life topics under Areas. Keep Journal for daily notes and Templates for template files.

2. Tags for topics that cross folders

A note in Projects/Website might also relate to design and hiring. Use tags (#design, #hiring) so Search and sidebar Tags can find it without moving the file.

Use / for light hierarchy (#project/website) when you want nested labels.

3. Properties for boards

When you need Status, Priority, or dates on a board, set those in the Properties panel. Collections read those fields for table columns and board cards.

4. One collection per project folder

For each active project folder, create one collection with that folder as the source (include subfolders if you nest notes). Add views inside the collection:

• Table for scanning titles and tags
• Board grouped by Tags or Status

Avoid duplicate collections for the same folder unless the sources differ.

5. Daily notes and templates folders

• Point Daily Notes at Journal (or your preferred folder).
• Point Templates at Templates.
• Optional: set a default daily note template.

See Daily Notes and Templates and Placeholders for the create flows.

What lives where

Plain Markdown is the source of truth for writing. The .glyph folder holds views and related metadata. You can back up or sync the Markdown tree and still open notes in another editor.

Keep structure simple

• Prefer a few top-level folders over deep nesting.
• Name folders for humans (Projects/Glyph), not for the database.
• Move a note by moving its file; update collection sources if a project folder changes.
• Delete a collection when you retire a view. The notes remain in the folder.

Example week

1. Capture the day in Open Daily Note under Journal/.
2. File project work under Projects/....
3. Tag cross-cutting topics.
4. Open the project collection board to update Status and Priority.
5. Create recurring docs with Create From Template.

That mix keeps folders honest, tags flexible, and collections as lenses over the same files.