# Quick Thots - **The sparksnotes.org site, at its core, is this Obsidian Vault**. The best possible setup is one where the notes and other works in the Vault are post-able as they are, maximizing both their utilities for our personal learning and readability as notes/blog-posts/documentation, etc. - This means creating notes in the style of **Evergreen Notes** for information-centric notes/pages, atomic style, with descriptive titles that summarize the notes purpose > [!question] Question: > How would you organize atomic-style notes with long, explicit titles on the Obsidian Publish site (or another markdown-file-based-routing site solution) in a way that is easy to navigate for visitors? Would it be the same as in the local vault? From the dome, the following is my imagined workflow of my system in its current, mostly imaginary state: --- The perfect app, that is also a website, would have **4 core domains of organization**: # 1. Notes **Notes** will come in flavors of immediate note-taking that you quickly jot to get ideas in a document, and Evergreen Notes that have explicit titles and are atomic (complete) in nature--capable of standing on their own, while still being connected to other notes of the same domain or topic, forming a larger web of topics, interests, ideas, and more—like a neural network. > [!question] Question: > Given the prevalence of technical documentation in both my professional and personal life, how should documentation be written, titled, organized, and connected? # 2. Projects **Projects** are long term commitments that will be either YouTube content, written pieces (often research-heavy) like blog posts, programming projects, and more. They'll will be broken down into tasks, utilize the calendar and require scheduling, often reference numerous resources (including our own notes), and more (as it comes to me to be spelled out explicitly). - [x] Break projects down into Project Types, each with a format and description of its components, plus documentation for using each project type's organizational structures, sub-task system, and other requirements that will be determined as the optimum way for working on and completing the project ✅ 2024-12-01 # 3. Tasks Obviously, everything involved with our content creation--researching, writing, filming, publishing--and self-education in general, requires a good deal of work. Staying on top of all this without any sort of task-management system would be _exceptionally difficult_. The ability to embed tasks into research projects, _in-progress_ notes, research pieces, video scripts, and anywhere else we want, _**and**_ the ability to collect, query, and organize said tasks, would both make all of this much easier to organize and execute. > [!idea] > Consider having, in addition to **Content Map** pages for broad subjects or projects, **Task Index** (_that's just what I'm calling them off the dome right now_) pages where all tasks related to an overarching subject or project are consolidated. This could be done with the native task query features # 4. Resources > [!warning] > This section is under construction! **Resources** are anything offering information, of any medium, that is used in the system. This could be citations, YouTube video tutorials, quotes, music created or used for effect in content, and much more. Citations will need some sort of management application to both store them and generate properly formatted citations for our content. Having already logged over 100 citations in Zotero, it will likely due for the time being.