feat(ADR): Documentation Strategy (#129)

[minkyraccoon]

This ADR proposes a documentation strategy for 4 specific use cases for documentation and the proposed structure using GitHub as the Content Management System.

[PaddyMc]

👍

[barriebyron]

@SenorMonito I love this formal approach! In past jobs, we have adhered to 3 primary content types: concept (called Explanation by Divio), task (how-to), and reference. Tutorials were managed by another group since tutorials are closely tied to software release versions and typically include assets required to run code for that particular release.

This documentation strategy is a wonderful step in a good direction. Be proud!

I provided more editorial suggestions, but went ahead and approved so you can merge it after you commit the changes you agree with. Cheerio!

[barriebyron]

food for thought @SenorMonito
Perhaps add some language to add flexibility to achieve the best outcome, following https://www.digitalocean.com/community/tutorials/digitalocean-s-technical-writing-guidelines

[minkyraccoon]

Based on reviewer feedback. moving to accepted status