3 ms·
As a practicing technical writer I can testify that these content types are a common way to organize your documentation collection and identify gaps. It’s a us
by kaycebasques 7y ago
As a practicing technical writer I can testify that these content types are a common way to organize your documentation collection and identify gaps.
It’s a useful exercise to list each doc as a row in a spreadsheet, and then mark whether each doc is a tutorial, guide, conceptual overview, or reference, or a confused combination. Many times you’ll see that you have explained how feature A works but have no tutorial that shows how to use feature A, or vice versa.
- franciscop 7y agoAs an OSS author this is very interesting, could you share more info or references about this please? Also I'm curious, how do you become a technical writter? Does it involve writing articles/blogposts/etc to promote the project?
- carapace 7y ago*writer ;-P
- gautamsomani 7y agohttps://www.linkedin.com/in/kaycebasques/ https://www.linkedin.com/in/kaycebasques/ This should help you :)