Lately I’ve been noticing a trend in user manuals. The omission of a syllabus or an overview of what the heck the manual or piece of software you’re about to use is supposed to do. It’s quite annoying and leads to me reading and rereading instructions and then getting it wrong. It’s like there is some sort of body of knowledge that all tech writers insert into their user manuals that is assumed… and doesn’t exist other than in the user manual tech writer’s head.
Again, quite annoying and is the reason that I’m writing mini rant posts while updating this website.
Ah well, nothing to do but post this page and hope it sticks.
Published the page and–surprise! It didn’t stick. Now to muck with other click boxes that aren’t documented in the user manual to figure out how to work this bloody thing.
Rinse and repeat while ignoring other “helpful” documentation and went with my gut instincts and… finally it stuck. Hooray! I’m not as stupid as I feel! Awesome. Moving on. (LOL)
Updating a website when one has had 2 hours of sleep is apparently my thing today. So please ignore the repeat posts while I try and work this stuff out.