- Local time
- 00:25
- Joined
- Oct 5, 2019
- Messages
- 1,187
- Pronouns
- he/him
Hey all,
I need some help how I should structure the Stancy documentation. It's my first fully self written (except contributions) open source package which I also have to write documentation for. I'm really not good in documentation structuring at all. š
Is there anyone who has some good tips how to structure one? So should I create a page for every usage step, should I explain every class or what do you think / would you prefer?
Primary because I've written every single line, wrote tests for them (100% coverage) it's pretty hard for me to switch perspective and imagine what a person that never heard about Development - Stancy would need to get started and how he would find everything. š¤