Technical Documentation: Guidelines, Templates, Examples & Other Resources #105075
Having these should help writing good and consistent documentation. People don't have to "reinvent the wheel", they can follow existing patterns that are known to be a good base.
- Simple guidelines to ensure consistent documentation (may also be part of the template).
- Template(s?) to define a good, general structure that can be copied.
- Examples of well written technical documentation for inspiration.
- Collection of other resources: Guidelines from other organizations, tools, articles, videos, etc.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?