Re: Book on Modern Technical Writing

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

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

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


References:
Re: Book on Modern Technical Writing: From: Chris Despopoulos
RE: Book on Modern Technical Writing: From: mbaker

Previous by Author: Re: Book on Modern Technical Writing
Next by Author: Re: Book on Modern Technical Writing
Previous by Thread: RE: Book on Modern Technical Writing
Next by Thread: Another maddening RoboHelp problem


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


Sponsored Ads
http://www.techwr-l.com/archives/1607/techwhirl-1607-00103.html
www.techwr-l.com
crawl=CC-MAIN-2021-39
25010
application/http; msgtype=response
sha1:OOOQ2R7PX5UGWLWAQ6XG3LJMOWVBEMBT
<urn:uuid:fefbf429-8da8-46ed-bc1d-1139bffd4dbe>
2021-09-20T13:31:04Z
184.106.92.169
text/html
sha1:TFHDCHIIT5EVOPZ4INSDRBOHHPRQ6ZNH
<urn:uuid:9fcd2454-efd3-42de-88f6-1bafa1c106ff>
http://www.techwr-l.com/archives/1607/techwhirl-1607-00103.html
response
<urn:uuid:60f207e7-e596-4a07-8291-4a18b85113e8>
isPartOf: CC-MAIN-2021-39
publisher: Common Crawl
description: Wide crawl of the web for September 2021
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-232
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.2-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/