Suggestions for when answering a software-recommendation question.
If your answer is less than a paragraph you likely haven't created a high quality answer to a software-recommendation.
A picture is worth over 9,000 words
The title says it all! Include screenshots of the software in action, a photo will typically help hook a user and encourage them to read more. It's no secret users love pictures in answers decorate your answer with 1-2 pictures of it in action and consider the quality of your post increased!
Details, Details, Details!
Consider highlighting features that are related to what the user originally requested or include use cases for this piece of software in particular. What sets it apart from every other solution? Why do you use it? The more information you can pack in the answer, without simply just copy-paste the product page, the more informative your answer becomes and the more awesome you are!
Learn more, tutorials, additional resources.
Topping off your post with a round of links to the software's tag, the homepage for the software, really good tutorials for getting started, or any other places for a user to explore further!
Ideally these answer should follow the same basic outline. Software name as an H1 with a link to apt.ubuntu.com (if applicable) with the details about that software following afterward. The following code should be sufficient:
#Software Name [![Install software-name](http://bit.ly/software-large)](http://apt.ubuntu.com/p/software-name)
Details, pictures, links.
Ensure you replace each instance of
software name and
software-name with the English and physical package name respectively of that software.