66
Software Engineering Documentation Best Practice?
(lemmy.world)
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
Be bold and make changes. Document what you find out, what is outdated, what is missing.
Take ownership. If there's nobody that oversees overall structure, be the one to do so - at least where you're touching it or are being bothered by it.
Diatraxis gives some great insight and considerations input into writing and structuring documentation. Namely how different target audiences and doc use cases require different forms and detail levels of guidance.
My company's internal doc/guidance also links to https://www.writethedocs.org/guide/ which seems like a good source.
Sort of interesting that this documentation system appeared in two different places that don’t seem to reference each other.
https://docs.divio.com/documentation-system/
Looking at the Web Archive; Diatraxis has been around since 2021. That divio docs since May of this year.
I doubt they didn't "get inspiration" from Diatraxis.
I’ve been referencing that Divio doc since 2021, possibly earlier in 2020. I even linked to the document in early 2022. It’s quite likely that it simply wasn’t crawled by the Web Archive before May this year.
Now that you say so, I feel like I've read about this before. In comments about Diatraxis/one of them years ago. :)