dannydannydanny/methodology
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

🎨 clean sections

Browse source
This commit is contained in:
dannydannydanny 2021-11-16 14:25:16 +01:00 • committed by GitHub
parent 5ba644dfa1
commit ae17e88065
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

11
methodology-development.md
View file

@ -1,11 +1,17 @@
### Document Roadmap
* [ ] Sections by Project Phase (setup, develop, deploy, deliver)
* [ ] Each section has heading, [sections-link](#sections) and at least one bullet point
* [ ] Each section should covers fixed topics (version control, systems management, docuementation)
* [ ] Information that doesn't fit into phases goes to [_Topic Hierarchy_](#topic-hierarchy)
* [ ] Add [Custom utils](https://dev.to/kenbellows/a-few-python-repl-config-tricks-3o6i).
### Sections ### Sections
* [Gitmoji Reference](#gitmoji-reference)
* [Setup](#setup) ([Version Control](#setup-version-control), [Environments](#setup-server-management), Documentation) * [Setup](#setup) ([Version Control](#setup-version-control), [Environments](#setup-server-management), Documentation)
* [Develop](#develop) ([Version Control](#develop-with-version-control), Server Management, Documentation) * [Develop](#develop) ([Version Control](#develop-with-version-control), Server Management, Documentation)
* Deploy * Deploy
* Deliver? * Deliver?
## Setup ## Setup
### Project Planning ### Project Planning
* Always have some kind of roadmap * Always have some kind of roadmap
@ -97,6 +103,7 @@ Context:
# -> feature1 is rejected and made obsolete # -> feature1 is rejected and made obsolete
``` ```
#### Topic Hierarchy
* **Documentation** * **Documentation**
* Use [Google's Markdown Style Guide](https://google.github.io/styleguide/docguide/style.html) for written documentation. * Use [Google's Markdown Style Guide](https://google.github.io/styleguide/docguide/style.html) for written documentation.
* Conceptual graphical documentation as inline embedded images. * Conceptual graphical documentation as inline embedded images.