Software Alternatives & Reviews

Should you add screenshots to documentation?

ApiFlash Floik
  1. ApiFlash is a powerful serverless screenshot API built with Chromium and AWS Lambda. It can easily scale to millions of screenshots per day and has an ever growing number of satisfied big clients.

    #Developer Tools #Software Development #API Tools 5 social mentions

  2. 2
    Interactive demos, videos & guides, created in minutes
    Screenshots are a must-have for any kind of documentation, especially product how-tos. But outdated screenshots can quickly backfire and do more harm than good. We've all been there when we land on a help center and the screenshots don't make sense! The good thing is, when you use tools like Floik (https://floik.com/) to create documents, you can update them whenever your product updates and add new screenshots. So, your documentation doesn't go stale <i>and</i> you don't have to go through the hassle of creating the same content again and again (and again).

    #Sales #CRM #SaaS 1 social mentions

  3. The only cheat sheet you need Unified access to the best community driven documentation
    Pricing:
    • Open Source
    Cheat.sh [0] has been a godsend when the man pages are too dense and I just want to use the tool and move on with my life. [0] http://cheat.sh/.

    #Mac #Text Expander #Shortcuts 51 social mentions

  4. bro pages are concise examples of using command line programs
    I haven’t used it in a long time and I’m guessing there might be something better now but I used to use “bro” instead of “man” when first starting out with a cli tool: http://bropages.org/ It’s documentation but with only examples.

    #Mac #Productivity #Text Expander 7 social mentions

Discuss: Should you add screenshots to documentation?

Log in or Post with