Open saragon02 opened 6 months ago
I can suggest Diataxis approach. It basically divides documentation to four main types, with clear goals and styles.
It doesn't need a "burn to the ground/rewrite" approach either. One can just start adapting the documentation page by page to this method. We use this on our cluster/user documentation, but unfortunately it's in Turkish. If you want to give it to a translator it's at https://docs.truba.gov.tr
@hbayindir woah this approach clearly formulates so many principles I hold dear well beyond documentation
Thank you for that :pray:
@fenekku very happy to hear that. I'm becoming a low-key documentation geek myself, and it helped me a lot. Glad that it helped someone else, too.
Cheers!
One example I can think of:
Examples
https://python.langchain.com/docs/get_started/introduction
https://iiif.io/get-started Two routes for onboarding: end user or implementer
https://www.archivematica.org/en/docs/archivematica-1.15/ User manual documentation is organized according to tabs that appear in the software, which in turn is organized in the order of routine tasks completed by archivists. Our user oriented documentation might be organized by routine tasks a depositor completes.
Add new links either to this issue or in Discord