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.
Re: 2 Concerns with accepting NDAs... Re: portfolio docs that WEREconfidential...
Subject:Re: 2 Concerns with accepting NDAs... Re: portfolio docs that WEREconfidential... From:yehoshua paul <yehoshua -dot- p -at- technicalwriting -dot- com> To:tech2wr-l <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Mon, 4 Jun 2012 23:01:46 +0300
I would do two things:
1. Clean up the documentation in an obvious way by changing specific
values, field names, windows, screen captures, or any other specific
feature that may be considered proprietary to something random and made up.
For example if a hardware model name is "RX5275", change it to "TE3470,"
which is a random name that I just made up. The people reading your
portfolio are not interested in the content, but rather in the writing
style and document setup.
2. Where it says in the header and footer "proprietary and confidential,"
change to "shared with permission." This makes it obvious to the reader
that you have permission to share these files.
On Mon, Jun 4, 2012 at 10:24 PM, Robert Lauriston <robert -at- lauriston -dot- com>wrote:
> I password-protect some of the writing samples on my Web site to make
> sure no one could mistake them for the current, real documentation.
>
> On Mon, Jun 4, 2012 at 12:03 PM, Daniel Dern <dern -at- pair -dot- com> wrote:
> >
> > If you can see it on your display, you can screen-snap it, probably
> > also "save as file." Even if these are somehow sneakily disabled,
> > they could always take a digital photo, retype, etc.
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 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://bit.ly/doc-to-help
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as
> yehoshua -dot- p -at- technicalwriting -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> info.
>
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.