Timeline for Does providing screenshots help with documentation manual?
Current License: CC BY-SA 3.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 14, 2014 at 15:37 | answer | added | UXUXUX | timeline score: 1 | |
| May 7, 2014 at 18:59 | answer | added | mike | timeline score: 4 | |
| May 7, 2014 at 17:49 | comment | added | Grant | Your users can read? And demonstrate this ability when looking at the manual? I'm very jealous. | |
| May 7, 2014 at 17:47 | comment | added | Grant | @RumiP. at least if they see a screenshot that looks radically different from what's on their screen, they will figure out something is wrong. Otherwise, they may spend half an hour looking for the button to click that no longer exists. | |
| May 7, 2014 at 15:27 | comment | added | user32565 | Peoples (atleast me) are lazy when it comes to reading documentation. Screenshots save a lot of time as I don't have read the whole paragraphs. | |
| May 7, 2014 at 13:02 | answer | added | notthefake | timeline score: 2 | |
| May 7, 2014 at 11:12 | vote | accept | Traven | ||
| May 7, 2014 at 10:40 | comment | added | Rumi P. | Note that usability is not the only thing to consider when deciding on screenshot inclusion. Applications evolve, and screenshots get stale quickly. It is terribly confusing for users to see a screen which differs from the screenshot (especially for the most computer-insecure ones who will benefit the most from the guide), so you will have to keep the screenshots current. Replacing dozens of images each time you make a slight adjustment in the UI is lots of work, you may not have the resources to commit to it. | |
| May 7, 2014 at 10:34 | answer | added | Anna Prenzel | timeline score: 29 | |
| May 7, 2014 at 10:24 | answer | added | roni | timeline score: 1 | |
| May 7, 2014 at 9:51 | answer | added | sandeep_jagtap | timeline score: 6 | |
| May 7, 2014 at 9:35 | history | edited | JonW♦ | CC BY-SA 3.0 |
edited tags; edited title
|
| May 7, 2014 at 9:21 | history | tweeted | twitter.com/#!/StackUX/status/463971980169854976 | ||
| May 7, 2014 at 8:03 | comment | added | JonW♦ | I could write down the directions from my house to the nearest shopping centre 5 miles away "Turn left here, forward 100 yards, turn right at the junction..." and someone could use that to navigate, but if I supplied those instructions with a map as well then it'd make their journey a whole lot easier. Adding useful, supporting information is a benefit. Is there any reason why you wouldn't include images? You don't browse websites using only words (aside from screenreader users) you do so visually, looking at screen areas to get visual cues as to where you are and what you're doing. | |
| May 7, 2014 at 7:39 | comment | added | bhttoan | Was going to post an answer but as it is only opinion I will share our experience instead. Our admin guide is ~120 pages long with ~75 images and we only use images where it makes the text easier to understand and adds something to the section rather than using to make it look better. | |
| May 7, 2014 at 7:24 | review | First posts | |||
| May 7, 2014 at 8:03 | |||||
| May 7, 2014 at 7:04 | history | asked | Traven | CC BY-SA 3.0 |