| I don't think using a single tool for everything is feasible, but you can use it as a single starting point aggregating all other references. Here are some options: - "Project Name" bookmarks folder in your browser - GDoc - README in a git repo - Miro board - Obsidian Canvas/Notes vault backed by a git repo For a large project with non-tech collaborators, I think Miro board is the best option. For a solo project, or small project were everyone knows git, git repo + Obsidian vault in the /docs folder of the same git repo. You can also use Miro board to facilitate kick-start of a new project using various methods/frameworks such as Design Sprint, EventStorming, or Event Modeling. For Software Design I would use docs-as-code formats stored in the git repo, such as: - Markdown - GFM (GitHub Flavoured Markdown) for OSS, Obsidian Markdown if everyone on the team comfortable with Obsidian. - PlantUML or mermaid (use mermaid since it's natively supported in GitHub and Obsidian, fallback to PlantUML for more complex cases) - C4 Model + C3Model PlatUML (Architecture Design diagrams) - ADR (Architecture Design Records) - arc42 - Software Design Document templates in various formats (including GFM - GitHub Flavoured Markdown) |