Re: So now we are content engineers?

Subject: Re: So now we are content engineers?
From: Chris Despopoulos <despopoulos_chriss -at- yahoo -dot- com>
To: "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Thu, 7 Nov 2013 01:38:56 -0800 (PST)

Interesting...  Last I looked, the title was "EYE am a content engineer", not YOU.  Not everybody in the biz does engineering, nor should they.  But some should.  There is engineering to be done with content.

BTW, Wikipedia has a page dated 2010 that tries to define content engineering. 


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.

Learn more: http://bit.ly/ZeOZeQ

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -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


Follow-Ups:

Previous by Author: RE: TechWhirl: Technical Communication Recap for November 22, 2013
Next by Author: Re: So now we are content engineers?
Previous by Thread: SGML - 38784 DTDs and FOSIs for Arbortext
Next by Thread: Re: So now we are content engineers?


What this post helpful? Share it with friends and colleagues:


Sponsored Ads