The general rule of thumb is notes sitting at the top of my root doc are organized with definitive structure, but the notes down below are organized instead of the current day / time. Project logs all go in SPRINTS section.Files generally should be very descriptive in nature Child bulletpoints under the bulletpoints like #excel can be as long and descriptive as possible - I treat bulletpoints 1 level deep from root as “folders” and bulletpoints 2-3 levels deep from root as “files”.The phrase express macro for CTRL+F chrome navigation is heavily used this is the first post on the topic I made essentially about navigating documents.It keeps things simple implementing a rigid rule like this This makes each folder unique for searching and still lets you implement things like rawbytez tag index maker Tag Index bookmarklet. Foldernames are all named with #name, and only exist at the top level only (Bulletpoint), and no #folders are nested inside other #folders.Images are used very sparingly, I only have a total of 4 inlined images across my entire document Inline images are used sparingly to split large clusters of folder names - This lets me see where I am at my notes using only my periphreal vision, so I instantly know what part of the document I’m on.This promotes high readability and being able to distinguish structure in my notes at a moments glance Bulletpoints 2-3 levels down from root doc have customized CSS H2 and H3 header tags.Bulletpoints 1 level down from root doc are extremely specific, with the shortest name possible like “ #excel” This keeps things clean and uncluttered, reducing the amount of time it takes for my eyes to adjust and find folders even if there is very large spans of texts everywhere in my wikis area.Consequently, this applies to things like youtube notes, MOOC, etc All 2 to 10 hour course notes go in their own specially designated bulletpoint - This keeps things uncluttered since a lot of coursenotes are just me trying to understand a topic, meaning notes are really polluted in nature.This is how I generally organize notes, and a follow summary rules of thumbs I use:
There’s more than 1 method though, I will name them Method 1: Using a folder list of items to macro So I use a macro with chromes CTRL+F to move around my document faster.
I have the hotkeys binded as much in settings: However sometimes I don’t really remember what my folder names are off the top of my head, or am too lazy to figure it out I use the default CTRL+F chrome search instead of the built-in dynalist one to navigatee my document faster. Navigating through them is kind of a pain, since my primary list view is super long I like to keep all of my project notes almost open all the time. (Top Navigation - Traditional TOC example - would be the tag index cloud mentioned earlier) And then access that on as a right side preview pane It would be really cool to have something similar to, where when you specify a documents H1, H2, H3, H4, H5, H6 header tags, etc that you could pregenerate / automatically generate a Table of contents based on those. ✪ TABLE OF CONTENT NAV: Scroll Tag $variable Right Pane Nav H1 to H6 ?FeaturesĮDIT: Adding onto the Table of Contents Idea