'Style Guide' and its importance in content writing and what style guides should a content writer follow?
In order to write documentation in a clearer way and keep a consistent tone, voice, and style in our documentation, I follow following style guides:
A list apart style guide: For design, development, and meaning of web content, with a special focus on web standards and best practices.
Techprose techwriting guidelines: For technical writing, training, and creating logical and professionally written material.
Microsoft manual of style: To maximize the impact and precision of the computer technology message, I use, fourth edition, the Microsoft Manual of Style that provides essential guidance to content creators, journalists, technical writers, editors, and everyone else who writes about computer technology.
Oxford manual of style: For writing and formatting documents written by staff on behalf of the company (or one of its constituent departments etc. I use Oxford manual style guide for branding toolkit which enables the University's formal documentation to be presented consistently across all communications.
IBM style guide: For API/SFDC projects or software doumentaion/ developerWorks I used IBM style evolves to adapt to shifts in how readers consume content.
Handbook of Technical Writing: To get the ideas for topics, checklist, dynamic videos break downs the best practices, and models, I use Handbook Manual.
A11Y Style Guide: To use ready to use helpful links or HTML markup and SCSS/CSS code, to inform designers, front-end and back-end developers at every stage of the website's creation I prefer to use A11Y style Guide.
Open SUSE Style Guide: To get help to choose the right XML element for writing, style, and layouts I prefer to use Open SUSE which makes the documentation more understandable and easier to translate.
Keywords: Style Guide, Technical Writing, Content Writing, Microsoft Style Guide, A11Y Style Guidel, Manual, Open SUSE, TechProse
0 Comments