Re: Best Practice...Reuse Content

Subject: Re: Best Practice...Reuse Content
From: David Neeley <dbneeley -at- gmail -dot- com>
To: techwr-l -at- lists -dot- techwr-l -dot- com
Date: Wed, 02 Feb 2011 09:31:10 +0200

Database replication is a common situation, enough so that this is often
set up to be done "automagically" in the background with little or no
human intervention.

However, in this case--whether the content should be the same in all
cases might depend upon the reception it would receive in either Canada
or the UK. As you are probably aware, there can be considerable
animosity toward too much content being clearly American in nature.
Thus, if the client base in those countries is extensive and if there
are local competitors there, it may still be worthwhile to have a
somewhat custom presentation for them.


> From:
> "Gene Kim-Eng" <techwr -at- genek -dot- com>
> Date:
> Tue, 1 Feb 2011 19:50:42 -0800
> To:
> Â TechwriterList <techwr-l -at- lists -dot- techwr-l -dot- com>
> It's important to draw a distinction between shared content and shared
> storage. Multiple locations working with synchronized local databases
> are still sharing content. You will need a process to resolve
> conflicts in case disconnected locations change the same content.
> Gene Kim-Eng
> ----- Original Message ----- From: "Keith Hood" <klhra -at- yahoo -dot- com>
>> If you consolidate your 29% common content in one physical location,
>> then 29% of your content will be accessible only as long as the links
>> stay up. If you consolidate that 29% in the US and a winter storm
>> blows down half the lines between here and Canada, then your Canadian
>> users have a problem. Users in the UK would have to be able to get
>> reliable round-trip connections across the Atlantic. The longer your
>> communications chain is, the more vulnerable it is. Your company
>> isn't hurting for storage space, is it? I would say keep the
>> distributed iterations of the common content but set up a system that
>> allows you to push content changes from a centralized source.B That
>> could be a software system or, in the right circumstances, it might
>> simply be a procedural change.


Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days.

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-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Please move off-topic discussions to the Chat list, at:


Previous by Author: Re: Customer-friendly word for "landline"
Next by Author: RE: Customer-friendly word for "landline"
Previous by Thread: RE: Best Practice...Reuse Content
Next by Thread: Re: Best Practice...Reuse Content

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

Sponsored Ads