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: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 | https://techwhirl.com
