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:RE: Best Modern Alternative to CHM? From:Chris Despopoulos <despopoulos_chriss -at- yahoo -dot- com> To:"techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 27 Jun 2017 08:04:59 +0000 (UTC)
If the app is client/server, then implement an HTML window in the client. Windows libraries provide all you need to do that so you can integrate HTML display in your app. Then have the server also serve up the content. Yes, it means your developers have to add more to the client, but in the long run it will improve the user experience. And yes... They can implement different types of HTML windows in the client to embed the help more directly into the user experience.
IMO the ONLY reason to consider CHM is if you need a stand-alone delivery of HTML that doesn't use a server of any kind. And I would question that need. But for a modern, client/server app, there's no excuse for using CHM. (Again, my opinion...)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
