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.
The web help I'm currently using (generated by Scroll HTML Exporter)
uses jquery. It's as good as I've seen in any online help system, fast
and accurate. I don't know what they use to generate the index, could
probably figure that out from looking at the Confluence application
directory.
On Wed, Jul 13, 2016 at 12:47 PM, Lois Patterson
<loisrpatterson -at- gmail -dot- com> wrote:
> I know that if you have your product documentation online, Google does a
> great deal of the work when it comes to search. In addition, it's
> relatively straightforward to implement solutions like elasticsearch. I
> understand the benefits of public, online documentation for searchability.
>
> However, I need a solution for local documentation. The infrastructure
> required to set up something like elasticsearch for a local doc system
> (essentially comprised of HTML files) seems excessive. But the search
> provided out of the box by sphinx is not satisfactory.
>
> If you are delivering local documentation, what are you using for
> high-quality search?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com