TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
My tech writing group has put together a style book that covers most of
the usual topics, but we're finding we also need to spell out the rules
for our graphics use.
We're at a software development company, and we have this pretty well in
hand for the callouts we use (always the same percentage of the screen
shot, always using the same heading style and so on). But now we're
trying to include more graphics: simple diagrams showing the tasks
users must complete and so on. We like including this stuff, but find
it lots harder to state the rules that will keep things
consistent-looking.
Do you have a graphics style guide? Or do you know about creating one?
Any help is most welcome!
