- Notes about how I should create my documentation - https://docs.obsibrain.com/#introduction-to-obsibrain - Public-facing documentation like how I am doing it - Features page - Landing page ## Module - Background - A primer to relevant mindsets and understandings required - Learn Obsidian - Features and plugins - Learn the vaults and workflows - The actual substance in the vault - Set up - Checklist to help you set up Questions - Difference between background and vault workflows? - Digital Galaxy - Different sets ## Structure ### Links - Should link to the type of USV note it is (philosophy, note, workflow) - Should have a link to the note it is part of for quick access ### Why - Benefits - Why do you do it and why would it make sense for somebody else - Any related notes I have that can help showcase its importance - At its best it should be as short as possible explained, because then the person can choose if the time is worth to go on reading ### What Going more in detail what you do to achieve that benefit. ### How How you realize this in Obsidian? How do you do this? (steps) Top View: e.g. - Using a calendar - Combined with habit tracking. - ….. ## Example Detailed View: e.g. Explaining "Quick Add" in total To show then your quick add for Habit Tracking and what is included in your "Quick Add" Has it to be done in a specific order? (Makes a specific order sens?) Does is relate to anything else? Does it effect anything else in the vault? With such an order I think you could "cancle" at any time when the person thinks the system does not fit anymore to there needs. For example: Habit Tracking. You started at the begining what you are doing and why. As the person is reading through it, the person thinks that your core idea is a great idea but would not do that directly in Obsidian. At the end I think if you would follow such a structure you could share more value because you share your ideas detached from a program.