kelu124
June 27, 2016
I have been working on a open-source hardware project and documentation is key. A question remains.
I'm lazy, how do I make the documentation process efficient, and as system-independant as possible?
I'm working only with a couple of Readmes:
We have identified a way to build a module documentation, following guidelines:
## Module: XX
## Name
## Title
## Description
## IOs
## Key Components
## License
Worklog -- Starting April 5th 2016
-------
### 2016-04-05 Title1
### 2016-04-06 Title2 ...
ConceptZ->ConceptA
To generate the blog, and to generate a mindmap of concepts.
It also highlights the TODOs
All dated elements generate individual posts on the corresponding github page, here http://kelu124.github.io/echomods/.
Worklog generates a mindmap of the concepts I have in mind at the moment.
An efficient (err, lazy) way of documenting. Only one place to edit information, will be updated everywhere, even in this presentation!
Or ping me @kelu124 / kelu124@gmail.com !