Documentation isn’t just for L1/L2s or products needing a technical integration. You need it for any product, regardless of what you're building. Creating great product and technical documentation involves an understanding of both the technology and stakeholder needs. 

Here are a few key principles to take note of:

Start with a Clear Introduction: Great docs begin with an accessible overview. It should answer what the project is, its core functionalities, and its unique value proposition. This sets the stage for deeper engagement.

Organize for Accessibility: The best documentation is well-structured, categorizing information logically from basic overviews to in-depth technical details. This hierarchical approach caters to both beginners and advanced users, ensuring everyone finds relevant information efficiently.

Comprehensive Coverage: Include all aspects of the project, from installation, configuration, API references, to common use cases, and troubleshooting. Users should feel that the documentation is a one-stop resource for all their needs. If you receive technical and product-related questions that aren’t covered in the documentation, add them in. 

Include Practical Examples: Real-world applications and code snippets are priceless. They illustrate concepts, provide quick reference, and can often communicate more effectively than abstract descriptions.

Interactive and Engaging Content: Incorporating interactive elements, such as live code environments or embedded tutorials, can significantly enhance the learning experience.

Maintain and Update Regularly: Keeping documentation current is crucial. Include version history and update logs to help users track changes and understand the evolution of the project. 

Announce when you update your docs, and what you’ve improved - it makes for great, well-received community updates. 

Solicit and Incorporate Feedback: Encourage user feedback and contributions to the documentation. This not only improves the quality but also fosters a sense of community involvement. 

Translate to multiple languages: You can ask your superusers to translate your docs to their native languages - of course, check with a proofreader, but the more languages your docs are available in, the more communities will choose to use/build/deploy with your product. And it’s not that devs can’t understand English docs. It’s the communities who make projects hot and worth building on to begin with that attract the subsequent devs. 

Devs on your chain = a result of your community proving you’re worth the time and dollar spend. 

Focus on Accessibility and Design: Ensure the documentation is easy to navigate, search, and read. Good design and responsive layouts make docs more approachable and user-friendly.

Legal and Ethical Considerations: Given the unique regulatory landscape of crypto, include necessary legal disclaimers, licensing information, and compliance guidelines.

Language and Tone: Remember - documentation is not sales copy. Use clear, concise language. While technical accuracy is paramount, the tone should be approachable and jargon should be explained or minimized. 

Here are some great docs that cover everything you need to know - whether you’re an investor, product user, prospective partner, or developer. They’re all different, but tick the same boxes. 

• Lens
• Injective
• Osmosis 

Want your docs to be best practice examples? Say wassup! 

‍