The way you structured the title would work. I would personally: 1. avoid using whitespaces in the title (for compatibility in various environments, Dendron defaults to `sweker-case`ing file names) 2. have less metadata exposed through the title (can use tag notes in body or frontmatter of note: https://wiki.dendron.so/notes/8bc9b3f1-8508-4d3a-a2de-be9f12ef1821/) 3. start with having the subdivision of pages under markdown headers in the book source note instead of a separate page. Later refactor the notes to have separate pages (or maybe chapters first) when the amount of content becomes unwieldy. (following the amoeba pattern of structuring notes: https://wiki.dendron.so/notes/e780000d-c784-4945-8e42-35218a3ecf10/) Unlike other tools, we put a lot of effort into making it easy to refactor notes. 1. commands like

Rename Note

,

Move Note

,

Refactor Hierarchy

,

Move Header

,

Rename Header

, all help you easily change the title / break down existing content of your note into smaller chunks: https://wiki.dendron.so/notes/srajljj10V2dl19nCSFiC/ 2. using modifiers in lookup will let you select some text and extract it into another note. Or use that selection as a note title to create a new note and convert your selection into a link at the same time: https://wiki.dendron.so/notes/ad270a7d-2aed-4273-8319-eb6536e38b29/#selectiontype This means you can iterate on the structure of the notes as you go forward and not worry too much about it at the beginning. I've spent a lot of time trying to make my note structure perfect and end up changing them half way through. But this is all my personal preference. If a note structure works for you I can tell you that it would be the right one. You mentioned that you haven't started using Dendron yet, so this may be a lot of information. These are briefly introduced during our initial user guide that you can go through when you first install Dendron as well, so I encourage you to try it out.