I like the thinking behind this article, but it seems to me that the additional types the author brings up are all just specialized versions of the four primary

I like the thinking behind this article, but it seems to me that the additional types the author brings up are all just specialized versions of the four primary documentation types: - Conceptual Overviews: High-level "explanations" (broader instead of deeper). - Examples (and case studies): "How-to guides" that focus on more narrowly-specific use cases instead of more general or common ones. - FAQs: "Reference" -- what readers want from FAQs are short concise answers, ideally with links to further details. - Troubleshooting: "How-to guides" that focus on fixing common problems. - Best practices: Opinionated "explanations" that focus just on best practices -- the best "best practices" guides explain why, not just what.