Documentation
Last updated
Was this helpful?
Last updated
Was this helpful?
Documentation is key for any project success. When team members move to different projects, the will be lost, and it would be hard for new maintainers keep the project on track as per the original Roadmap. We believe in philosophy and keep related documents close to code in the same repository.
Docs should be organized under docs
folder in the root of the repo.
We recommend for writing documents and leverage and to embed diagrams directly into Markdown files.
Recommended minimal documentation for each project:
README.md - Should contain Project goals, big picture, list of features, developer's workflow to contribute to repo.
to keep tracking releases, milestones, features and project status.
Roadmap should include short and long term goals.
Changelog - Automatically changelog as part for release process.
- file contain resources who own specific module in the repository and who should review before PRs are merged.
Architecture Decision Record - is a document that captures an important architectural decision made along with its context and consequences.
Style Guide - Coding Style Guide
Extra GitHub Markdown tricks
Future improvements:
To generate it, markdown provides a shortcut: An easy auto-generation. All the titles defined with #will be edited into the table of contents if the [TOC] is added in the appropriate place.
Here need a footnote[^noteID1].
[^noteID1]: Here is the quote for ID1.