Documentation Hierarchy
README: quick start, what it does, how to install
API Reference: complete, accurate, with examples
Guides: tutorials, how-tos, conceptual explanations
Architecture Decision Records: why decisions were made
Writing Effective READMEs
One-line description of what the project does
Quick start with install and usage code
Feature list
API reference link
Contributing guidelines
Technical Blog Post Best Practices
Start with the problem, not the solution
Use concrete examples over abstract descriptions
Show code, then explain it
Include a 'when to use this' section
Keep paragraphs short (3-4 sentences)