4 ms·
> Outdated screenshots can cause customers to lose trust in documentation accuracy. as opposed to outdated documentation without screenshots, where the user ha
by d--b 3y ago
> Outdated screenshots can cause customers to lose trust in documentation accuracy.
as opposed to outdated documentation without screenshots, where the user has no idea that he's reading stuff from 5 years ago?
- rcxdude 3y agoIndeed. I lose a lot more trust when I've spent 15 minutes trying to find the damn option the documentation insists should be there, only to find it doesn't exist any more. A screenshot at least gives me that information faster.
- scantron4 3y agoThis is what I was going to say. Nothing more frustrating than trying to find an option that has been moved somewhere else (why is android documentation the worst about this). At least with a screenshot you know it is either where they say it is or that you need to find a different tutorial.
- Popeyes 3y agoIf you are writing documentation you should put a date on your content and a version number if it relates to a product. I've been reading about accordions because I want to refresh a UI, but I read a document about the <details> element and accessibility and didn't realise it was from 2019 until I got to the end and saw the comments were all from that year.
- baby_souffle 3y agoExactly! Even with old screenshots, you can still see what your next action is supposed to be and what functions were near it. That’s invaluable for trying to find the function you need in a new UI. I can give you a guide for how to do just about anything using screenshots of the AWS console from years ago and you probably wouldn’t have that tough of a time adapting them to the current UI.