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.
The OP is the sole author at one site, which is not necessarily the entire
company. And if there is a style guide, it may apply across the entire
company and be owned by another department, such as Marketing. Jumping in
and making changes at a new job without first investigating the status quo
is a really good way to reduce the life expectancy of the job.
Gene Kim-Eng
On Thu, Jan 5, 2012 at 8:45 AM, <> wrote:
> FApple vs. Microsoft arguments aside, you are the sole writer for the
> company, therefore you should have the freedom and agency to change
> whatever you think needs to be changed. Style Guides are working documents
> that are constantly being revised based on what the writers think needs to
> become part of the company's style. I say make the change, and any other
> changes you see fit.
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
