conventionalcommits.org
conventionalcommits.org copied to clipboard
Scheme for documentation
I'm inspired by Conventional Commits, and would like to have a scheme for writing projects, e.g. documentations or personal or organizational knowledge management system. It's like how Semantic Versioning for Documents be to Semantic Versioning. I'm thinking of using these structure elements:
- title: for changes in project title
- structure: for changes in project folder structure
- fileA/B/C: for changes in an important file (to avoid to tediously create many submodules for tracking many individual files)
Do you have any feedback?