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.
That's a good approach if your application has a update feature.
At my last job, we surveyed customers about removing the help from the
application and moving it to the web. No one had any objections, even
though many of them were in very secure environments.
On Thu, Apr 7, 2016 at 9:04 AM, Daniel Friedman
<daniel -dot- friedman42 -at- gmail -dot- com> wrote:
> At my current position, we have made the embedded help file update-able
> through the software's update feature. This means a customer doesn't have to
> install an entire release, but just an update package. Whether or not the
> customer has to re-validate their entire install after downloading an update
> package, is something that the customer would have to decide based on their
> SOPs (pharmaceutical industry).
>
> Having the help on a separate web server could fix the validation question,
> because then we wouldn't be changing anything in their installation to
> update help, but it assumes:
> 1. Access control to avoid other clients/3rd parties from viewing help for
> proprietary custom software.
> 2. End users would be able to visit our help website through the corporate
> firewall/web blocking, which can be quite restrictive at these companies.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
