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.
Subject:Re: Thoughts on an Editing Portfolio From:"Raj Machhan" <raj -dot- machhan -at- gmail -dot- com> To:schu1663 <schu1663 -at- umn -dot- edu> Date:Mon, 3 Dec 2007 17:48:32 +0530
To a student standing on the fringe of this profession, I can only say that
instead of applying yourself to "showing off", you should be adopting
'rigour' as your middle name. You should be absolutely rigorous in your
approach while acquiring new skills. "Showing off" the resume at this stage
does not matter. The interviewer will be out to test the depth of your
knowledge and I guess a simple resume would do at this stage. I suggest you
just include the documents that you have designed and edited.
On Dec 2, 2007 4:05 AM, schu1663 <schu1663 -at- umn -dot- edu> wrote:
> I'm currently a student in a technical communication program and was
> recently thinking about portfolios. Specifically, I was wondering what
> of things one might include when trying to create a portfolio to show off
> editing skills. At first, I was thinking that I would need to include some
> "before-and-after" documents, but then I came to the conclusion that
> anything I have in the portfolio will show off editing skills. I'm just
> curious if anyone who works in the field agrees with this or not. If
> applying for a technical editing job, would I need "before-and-after" type
> documents, or would I simply be able to include documents that I have
> designed and edited?
> schu1663 -at- umn -dot- edu
> Create HTML or Microsoft Word content and convert to Help file formats or
> printed documentation. Features include support for Windows Vista & 2007
> Microsoft Office, team authoring, plus more.
> True single source, conditional content, PDF export, modular help.
> Help & Manual is the most powerful authoring tool for technical
> documentation. Boost your productivity! http://www.helpandmanual.com
> You are currently subscribed to TECHWR-L as raj -dot- machhan -at- gmail -dot- com -dot-
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit
> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwr-l.com/ for more resources and info.
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-