When and how do you improve documentation?
I dont mean "added new/refactored code, gotta document it" but active improvement.
Which feeback channels do you have for your docs?

  • 2
    Whenever I feel like my users are struggling a bit or I feel like some things might not be clear before a major release.

    I really hate it when a tool isn't documented properly so I made it my mission to give all the examples anyone could need
  • 2
    The one of methods would be collecting feedback directly from docs website. This way, page URL is automatically attached.
  • 0
    Having properly anchored headers in docs helps everyone to refer to certain portion of the text just by sharing link, hence providing a shortcut to related knowledge. Even docs have UI/UX.
Add Comment