As your software project grows, it may involve more contributors. If you build a platform that publishes APIs that can be consumed by the public, you may expect more users to use your platform. If you work on an internal project that involves many parties from several vendors, you may expect everyone can understand your project and collaborate well. In any scenario, effective documentation can help you achieve what you want.
We should consider a user-oriented design for our documentation which considers who will use our product and what goal our users pursue by reading the documentation. Sometimes, it can help us in developing the project itself by trying to see the project from a user perspective.
These are types of common audiences and the information needed.
-
Evaluators who examine whether the service or tool is useful. They
need a high-level overview, a list of features, or expected benefits.
- New users who just learn the usage. They need a getting started guide, authentication method, or a "Hello World" example.
- Advanced users who want to optimize the utilisation or apply uncommon use cases. They need a full API reference, design information, or caveats.
- QA and technical support who intend to test or troubleshoot the tool. They might need a full API/CLI reference, upgrade/migration guide, or information about common problems.
- Administrators who engineer the system configuration. They need architecture reference, dependencies information, or a full CLI reference.
- Contributors who extend the features or documentation. They need an architecture direction, a full API/CLI reference, or a contributors guide.
- API reference manual that explains what the API does with the code example that shows the correct usage.
- Technical overview that explains the unique benefits, a high-level description, and main features.
- Installation and access guide that explains how to set up the environment and configure the tools.
- Getting started let newcomer jumpstart to utilise the service or a "Hello World" recipe.
- Glossary of terms
- Usage recommendations
- Example code
- Procedural documents (usage guides or tutorials)
- Release notes
- Migration guides
- Integration guides
- Complete coverage
- Accurate syntax
- Useful semantic description
- Introductory description to place information into a context
- Consistent use of terminology
- Consistent content presentation
- Consistent use of language
- Good navigation
- Clear information about the intended audience and prerequisites
Comments
Post a Comment