Consider writing your docs from the bottom up. Start with an API reference. Then think about the N most important use cases. Create a "Cookbook" section that walks the user through those use cases. Add a "Getting started" section that describes how to install and configure your app/product. Finally, a "Hello world" section that walks the user through the simplest way of knowing they've installed and configured their system correctly.
Don't forget to include a way for people to provide feedback on every page. I find it enormously annoying to hit a feedback button and it does not pre-populate the feedback with some identifying information about the page I was reading.
Then find a few people to vet your docs. Maybe offer a free t-shirt or some other swag.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Consider writing your docs from the bottom up. Start with an API reference. Then think about the N most important use cases. Create a "Cookbook" section that walks the user through those use cases. Add a "Getting started" section that describes how to install and configure your app/product. Finally, a "Hello world" section that walks the user through the simplest way of knowing they've installed and configured their system correctly.
Don't forget to include a way for people to provide feedback on every page. I find it enormously annoying to hit a feedback button and it does not pre-populate the feedback with some identifying information about the page I was reading.
Then find a few people to vet your docs. Maybe offer a free t-shirt or some other swag.