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: Book on Modern Technical Writing From:Robert Lauriston <robert -at- lauriston -dot- com> To:TECHWR-L Writing <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 29 Jul 2016 10:29:38 -0700
That stuff is certainly happening, but lots of hosted applications
make sense as single sites. On the back end, of course applications
with thousands or millions of users are distributed across multiple
physical and virtual servers in multiple locations, but when I use
online applications that's invisible. My stuff is always at the same
URLs.
With Chris's company's product, every customer may install a different
subset of available server features. I doubt that's ever going to be
common.
I think the more common approach will be using AI to tailor software
to individual users based on their past activity, which will probably
mean merging end user documentation with the UI. I can't see why the
nature of the internal documentation for the back end (the kind of
stuff I spend most of my time writing) should need to change much.
> -----Original Message-----
> ... On Behalf Of Chris Despopoulos
> ... SITE: Welcome to the 21st Century. With microservices, virtual machines, software-defined infrastructures, cloud providers, etc. the concept of a single machine for a single application is on the way out. By that token, a single site for all the content that pertains to such an application ultimately cannot scale. Add in the IoT, and you have a distributed environment where no two users necessarily see the same constellation of features/things in a distributed environment. That means the content has to be distributed across multiple sites.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
