Documentation

I ran a live stream a while back where I looked at new features in Snagit 2021 and how they can help those writing technical documentation or explanatory content generate great screenshots. And then I had a deadline, another deadline, and all sorts of other chaos, and somehow I only got around the blog post to accompany that livestream... now. Well, on the positive, in the meantime, I have had much more time to get my hands on Snagit 2021 in a real-world context. So, if you need to create, edit...

I won’t repeat any famous phrases about how pictures equalling a quantity of words, I think we all understand the potential power of a good visual. Well considered images in documentation can help illustrate a concept, clarify a complex idea, or show a reader what they can expect from undertaking certain steps.

When comparing products, you want to decide on their usefulness. Yet, we often forget to evaluate the project's documentation. A project might offer an excellent set of features but might lack easy-to-use documentation. This can have a detrimental effect on the developer experience and your team's efficiency. So, how do you evaluate the developer experience of documentation?