Hi @Muzikman777 , fellow user here.
I know what you mean – it’s hard to get started on building your notes, especially when you’re trying out new tools and trying to figure out what will work best for you.
I would disagree with you that Obsidian frowns on top-down structure. One of the things I like about Obsidian is that it is primarily a Markdown text editor that provides a lot of tools for linking and organizing your notes. It doesn’t have an opinion about whether your notes are top-down, bottom-up, tagged, linked, in folders, or not. It’s happy to support whatever structure you want to impose on your notes.
But that’s also one of the challenges of using Obsidian – because the tool doesn’t impose a structure, you’re left with guessing and experimentation to find something that works for you. Add in Obsidian’s plethora of plugins, and it becomes easy to get lost in the woods.
So I suggest you start small. Don’t worry about plugins or organization strategies or folder hierarchies yet. You’re learning JavaScript – awesome! There are two ways I’d suggest you start with, and see if either one works well with the way you think:
I suggest you start with a single file called “JavaScript”. As you work through the concepts in the book, take notes. Don’t worry too much about organizing the file at first, just start getting your notes in there. After a while the file will get large, and a natural organization will suggest itself to you. Break the sections into new files linked from “JavaScript”, perhaps “JavaScript Syntax”, “JavaScript Objects”, “JavaScript Arrays”, or however your notes naturally cluster. When you’re done, you have a collection of linked files that contain a bunch of knowledge you’ve accumulated. A good start!
Or, you could start with a single file named after the book. In that file you could create headings for each chapter, along with the notes you take in each one. As some chapters’ notes get larger you can break them into separate files, linked from the main file. When you’re done, you’ll have a bunch of pages linked together that follow the structure of the book.
Either way you’ll have some useful content that is organized in a way that follows the content, instead of hard-to-use content stuffed into an awkward structure – or worse, no content at all because you spent all your time organizing!
My point here is suggest you avoid pre-organizing your notes. You don’t know exactly what you’ll create yet, so any organization you choose now will probably not fit what you end up creating. Time spent now trying to guess at what will become the best organization for your notes is, frankly, mostly wasted.
Instead, just start – and let the content you create suggest the best organization later. After a while you’ll begin to see where links, tags, folders, and so forth might be useful – or not!
I hope this helps. If you have specific questions, please feel free to post them here!
Best of luck, and I hope you enjoy the journey,
Craig