Technical writing and editing
The respect I have for the often-confidential nature of software documentation prevents me from displaying any actual samples of the user guides, manuals and other documentation I have developed, written, edited and maintained. But I can tell you what I do.
My specialty is in the creation of information that is easy to read and understand, easy to follow, and practical for any user at any level of technical ability. Each piece of software requires several documents or manuals depending on topic and user role. When the software is complex, detailed, and highly technical, it makes simple, "friendly" writing a challenge that I enjoy.
Stantive Technologies Group
Responsibility: writing, editing and consistent updating of all user guides for OrchestraCMS. Worked closely with developers and SMEs to translate and explain technical language about this complex product into about 18 clear and comprehensive guides for Salesforce customers; maintained a Salesforce Library for the documentation. Programs used: Adobe InDesign, Adobe Photoshop, Adobe Acrobat, Google, Microsoft Word.
Responsibility: writing user guides for the Bridgeline suites and companies in organized, attractive, easy-to-follow language.
Responsibility: Creating a knowledgebase of documentation and user guides for customers and support staff.
Responsibility: working as part of a team of writers and instructional designers to develop a curriculum for new employees.
Responsibility: writing five 1,000 to 1,500-word blogs on five different topics explaining the history, use, and benefits of vector technology.
Governor General of Canada
Responsibility (for a GG Contacts Consolidation Project): working with an Adobe Designer and the Project Manager to capture over 400 data elements, describing the functional and non-functional requirements.
Responsibility: creating a full internet service knowledgebase for customers who live in condos.