A style guide or style manual is a set of standards for design and writing of documents, either for general use or for a specific publication or organization. Style guides are commonly used by technical communicators in large organizations.
#35211
Do I Really Need a Style Guide?
Style guides recommend certain styles. In the domain of technical communication, we refer to guides for writing style, presentation of content in user documentation and technical documents, and graphical user interface of software and web sites.
Palagummi, Sharada. Indus (2009). Articles>Style Guides>Editing>Writing
#35227
This style guide represents some of John Allen’s extraordinary wisdom surrounding the use of English in written and spoken communications. This is in many ways at the heart of what the BBC does and what it is respected for.This is not a “do and don’t” list but a guide that invites you to explore some of the complexities of modern English usage and to make your own decisions about what does and does not work. It should improve your scripts and general writing, not to mention making you feel better informed, challenged and amused.
BBC (2009). Resources>Style Guides
#35402
Style Rules for Job Position Names and Titles in Policies & Procedures
Have you struggled with job position names and titles in your policies and procedures (P&P) content? Here are several style rules to follow.
Urgo, Raymond E. Policies and Procedures Authority, The (2009). Articles>Style Guides>Policies and Procedures>Organizational Communication
#35518
Style Manuals: The Politics of Selection 
Bette Frick and Betsy Frick discuss how a style manual can save time and money, how to select the proper style manual and get buy-in, and how to create a style guide to use in conjunction with a style manual.
Frick, Elizabeth G.'Bette' and Elizabeth A. 'Betsy' Frick. Intercom (2009). Articles>Writing>Style Guides>Standards
#35525
Consistency and Community-Generated Content
I’ve been collecting examples of wildly inconsistent writing lately. I’m not sure why these have stuck out to me, but when I think of book sprints and community writing events, consistency is an important, though sometimes difficult, goal and outcome.
Gentle, Anne and Janet Swisher. Just Write Click (2009). Articles>Documentation>Style Guides>Wikis
#35628
Choosing the Right Style Guide 
Style guides can improve the quality and presentation of documentation. They establish a layer of professionalism that may not have been there before. They also reduce arguments and ‘loose cannons’ within the department, as the style guide becomes the acknowledged reference. There are at least four points to consider when selecting a style guide.
Walsh, Ivan. I Heart Tech Docs (2007). Articles>Editing>Style Guides>Standards
#35678
Controlled Language – Does My Company Need It?
Controlled languages use basis writing rules to simplify sentence structure. Here is how they work and how your company can benefit from introducing a controlled language.
Muegge, Uwe. TC World (2009). Articles>Language>Style Guides>Controlled Vocabulary
#35709
Writing Great Documentation: Technical Style
Now that I’ve discussed what kinds of technical documentation to write, I can move on to the question of how to actually develop a writing style that produces great technical documentation. So how do you learn to write (anything) well? There’s only one answer: you’ll learn to write well if you write. A lot.
Kaplan-Moss, Jacob. Jacobian (2009). Articles>Documentation>Style Guides>Technical Writing
#35788
Sometimes, You've Got to Break the Rules
Sometimes, you don’t need documentation made up of perfectly-chosen words and phrases. Instead, you need something that can be easily scanned, easily understood, and easily digested. Documentation that distills the main points quickly.
Nesbitt, Scott. DMN Communications. Articles>TC>Style Guides>Writing
