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.
I'm trying to explain to my boss that I'm do more than just write documentation. I take the interface that the programmer
and the designer have created and I edit the on-screen language, button and field names and change placement of items on the screen. I also edit the text of the error messages to make them more helpful for the users. I don't want to call it interface design because the designer came up with the look & feel and the programmer uses it. I'm editing what's already been created. It's not really quality control/assurance/improvement because I'm not testing the validity of the data itself or streamlining the process of how the data is gathered. I'm not doing any direct testing with users (nor am I focusing on special needs users) so I hesitate to call it usability. I'm looking for a phrase to describe it. Does "interface editing" describe it well enough? Any suggestions?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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-
