I wonder where you all keep your technical (or maybe your project) documentation. Do you write it down in Word, Excel or s.th.? Or do you use other tools for it?.
Let me know! :)
For further actions, you may consider blocking this person and/or reporting abuse
Camilo Micheletto -
Nathan Orris -
Murtaza Joo -
Siôn Grabham-Madden -
Once suspended, saschadev will not be able to comment or publish posts until their suspension is removed.
Once unsuspended, saschadev will be able to comment and publish posts again.
Once unpublished, all posts by saschadev will become hidden and only accessible to themselves.
If saschadev is not suspended, they can still re-publish their posts from their dashboard.
Once unpublished, this post will become invisible to the public and only accessible to Der Sascha.
They can still re-publish the post if they are not suspended.
Thanks for keeping DEV Community safe. Here is what you can do to flag saschadev:
Unflagging saschadev will restore default visibility to their posts.
Top comments (5)
Well, Over at the SBTCVM project (a Project that develops a Balanced ternary virtual machine and related tools, utilities, etc.), we have an extensive users manual in both pdf and odt formats that provides the bulk of "polished" technical documentation, while we also have a directory full of .txt developer's notes, that are about as technical as one may expect such notes for a Balanced Ternary Virtual Machine and accompanying utilities and libraries would be...
We've been keeping our technical documentation in a github wiki. Here's a bunch of documentation examples that people seem to be a fan of: dev.to/ben/what-are-some-examples-...
We keep them in a github repo:
github.com/infinum/rails-handbook/
This looks great.
It's quite complex, therefore DITA-XML based, kept in Bitbucket and published by Jenkins.