RE: Getting input into the style guide

[Anne Robotti <Anne -dot- Robotti -at- radisys -dot- com>]

> But... I also don't want to get into an infight. I just have a strong
> feeling that any style guide that simply specifies "Arial" as 
> a font choice
> is not one that paid much attention to what user guides need 
> to look like;
> and if all the documentation I produce is to be formatted in 
> accordance with
> the company style guide, I want some input into what the 
> company style guide
> says!
> 
> I would appreciate insights and advice on how best to handle this...
> 

Jane, what I would do is to write a memo that uses the existing
company style guide as a jumping off point. Something along the
lines of, "To promote the company look & feel, headings of all
technical manuals will use Arial font, and body text (which needs
to be in serif fonts for readability) will be in TNR." You pretty
it up (sorry people!) but I think this accomplishes two main goals.
It makes it clear that you are certainly interested in following the
company style guide, and also makes it clear that technical manuals
have style considerations that may not already be addressed in the
company style guide.

Anne

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com

Sponsored by Information Mapping, Inc., a professional services firm
specializing in Knowledge Management and e-content solutions. See
http://www.infomap.com or 800-463-6627 for more about our solutions.

---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit 
http://www.raycomm.com/techwhirl/ for more resources and info.