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: Eric Sedor has a piece on tech writing for the cloud
Subject:Re: Eric Sedor has a piece on tech writing for the cloud From:Tony Chung <tonyc -at- tonychung -dot- ca> To:Chris Despopoulos <despopoulos_chriss -at- yahoo -dot- com> Date:Fri, 14 Mar 2014 12:29:41 -0700
Hi Chris,
On Fri, Mar 14, 2014 at 3:52 AM, Chris Despopoulos <
despopoulos_chriss -at- yahoo -dot- com> wrote:
> So laugh if you like, but "...slinging portable, concise fragments of
> instruction into rich, scalable
> user interfaces (while also mapping them to sequential help articles,
> blogs, and examples) " is what it takes to support this environment.
> Because that's what this environment does with the concept of a "product".
>
>
Well, with the advent of social coding, remote teams spend a lot of time
with their heads in the clouds:
- Video meetings: Skype/Google Hangouts/Adobe Connect/WebEx/GotoMeeting...
- Task managers: Asana, Trello, Leankit...
- Documents: Google, OfficeLive, Zoho...
- Source code managers: GitHub, Bitbucket, Sourceforge...
I'd be into finding more players in the field.
> This is precisely why I'm developing an open source framework that I call
> 4D Pubs (Distributed Dynamic Document Display). Distributed documentation
> is the key... A single, centralized doc server won't scale in this
> environment (or that's what I assert). Documentation stays with the
> service node, where it belongs.
>
> I support a product that is in this environment, and enables this
> environment (see http://www.vmturbo.com/). I had better be ready for the
> product to succeed, and for this environment to take hold. I deliver our
> docs in an embryonic version of 4D Pubs. The system loads raw DITA from
> the server, and converts it to HTML in the browser, on the fly. And I can
> do cool things:
>
> * Simple, agile doc delivery
> * Skinning the "look"
> * Dynamic filtering per user role or other criteria
> * Modification of transforms on the fly
> * Get and use state information from the server
> * Execute server actions from the docs
>
> When we add more products to the offering, we'll also offer a client that
> merges these multiple "products" in a single GUI. I'll then be able to
> merge the docs from these multiple "products" into a single delivery...
> Real time and on the fly.
>
I'd be interested in finding out more about your tool set. I'm guessing
that you're also working with DITA?
Thanks,
-Tony
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Doc-To-Help 2014 v1 now available. SharePoint 2013 support, NetHelp enhancements, and more. Read all about it.