Subject: Re: Security and help systems

Subject: Subject: Re: Security and help systems
From: Chris Despopoulos <despopoulos_chriss -at- yahoo -dot- com>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Wed, 31 Jul 2019 08:22:48 +0000 (UTC)

I'm with Robert L. on this. Why would anybody want to tamper with your help system? In addition, if your HTML is packaged with your product and served by it, then isn't the product GUI also HTML? So how is your help system more vulnerable than your product's GUI client?
We deliver online help as a single-page HTML app. It transforms our DITA to HTML on the fly. In fact, the same service we developed to do the transform also transforms content in the product GUI. Modern apps are server/client, with the server installed in the enterprise IT environment, either on-prem or on the cloud. The client is inevitably HTML implemented in some framework such as Angular or its offspring. The risks of implementing onine help in the same way are equal to the risks of delivering the GUI itself. So are the benefits equal... We are approaching the day when GUI == Docs, and Docs == GUI!
Visit TechWhirl for the latest on content technology, content strategy and content development |


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 for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @

Previous by Author: RE: "Every project is a monster you battle and slay"
Next by Author: RE: the Oxford comma
Previous by Thread: TechWhirl online discussion with Jack Molisani from LavaCon Conference
Next by Thread: What do you call these little triangles?

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

Sponsored Ads