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.
On Wed, Feb 17, 2010 at 10:31 PM, Patricia Egan <
capdev -dot- communications -at- gmail -dot- com> wrote:
> I'm jumping in a little late, but Apple has its style guide available
> online. I think that it's a good example of a corporate style guide.
> On Tue, Feb 16, 2010 at 8:54 PM, Janice Gelb <Janice -dot- Gelb -at- sun -dot- com> wrote:
>> On 17/02/10 03:43 AM, Heather Anderson wrote:
>> > Good morning everyone!
>> > I have been tasked to create a style guide for my company.
>> > I was curious if people used them or if they simply used the Chicago
>> Manual of Style for their documentation?
>> > I was hoping to make a simple, quick style guide that covered fonts,
>> formats, and template usage.
>> > Does anyone have any examples or any other information I should include?
>> I am not sure if I should create a usage section with frequently misused
>> > I've used style guides in the past, but this is my first time creating
>> You might be interested in a best practices guide
>> booklet called "Developing a Corporate Style Guide":
>> -- Janice
>> Janice Gelb | The only connection Sun has with
>> janice -dot- gelb -at- sun -dot- com | this message is the return address
>> Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
>> produce desktop, Web, or print deliverables. Just write (or import)
>> and Doc-To-Help does the rest. Free trial: http://www.doctohelp.com
>> Explore CAREER options and paths related to Technical Writing,
>> learn to create SOFTWARE REQUIREMENTS documents, and
>> get tips on FUNCTIONAL SPECIFICATION best practices. Free at:
>> http://www.ModernAnalyst.com <http://www.modernanalyst.com/>
>> You are currently subscribed to TECHWR-L as
>> capdev -dot- communications -at- gmail -dot- com -dot-
>> To unsubscribe send a blank email to
>> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
>> or visit
>> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
>> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>> http://www.techwr-l.com/ for more resources and info.
>> Please move off-topic discussions to the Chat list, at:
> Patricia Egan
> P. O. Box 194391
> San Francisco, CA 94119-4391
P. O. Box 194391
San Francisco, CA 94119-4391
Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial: http://www.doctohelp.com
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-