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: wiki vs blog From:Bill Swallow <techcommdood -at- gmail -dot- com> To:John Posada <jposada99 -at- gmail -dot- com> Date:Wed, 13 Jan 2010 13:31:01 -0500
Ah, your question made no sense as written. Thanks for the
The tool matters in that it does what you want it to. This is no
different in the realm if wikis and blogs as it is for tech writing,
application development, or heavy construction. If WordPress fits your
technological and intended use needs, then use it. If Drupal is a
better fit, use that instead.
On Jan 13, 2010, at 1:18 PM, John Posada <jposada99 -at- gmail -dot- com> wrote:
> I'll ask the question again. Pay attention :-)
> "from the perspective of authoring content. what differentiates an
> editing tool from between wikis and blogs"
> In other words...
> Does it matter, from the tool perspective, whether I'm using something
> like Word Press, to author in a wiki or a blog?
> On Wed, Jan 13, 2010 at 11:56 AM, Bill Swallow
> <techcommdood -at- gmail -dot- com> wrote:
>>> Wiki's are a read-write medium. Blogs are a read-respond medium.
>> A bit more than that.
>> Wikis are read-write-respond. They are designed for collaborative
>> authoring and idea development. That is, your audience should have a
>> hand in creating the content, whether in an open or controlled
>> Blogs are indeed read-respond mediums. They *can* be created by
>> multiple authors, but the goal is information dissemination, not
>> collaborative authoring, and the audience does not have a hand in
>> creating the content.
>>> IMHO, there IS a difference.
>> Bill Swallow
>> Twitter: @techcommdood
>> Blog: http://techcommdood.com
>> LinkedIn: http://www.linkedin.com/in/techcommdood
>> Available for contract and full time opportunities.
>> STC Ideas: http://stcideas.ning.com
>> Join: http://stcideas.ning.com/?xgi=6X1vNGI
> John Posada
> Senior Technical Writer
> NYMetro STC President
> Looking for the next gig.
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-