Help & Manual Forums

Having multiple Xplains for this would seem like overkill for what is basically a simple task. I would use a single Xplain with a single slide for each set of browser instructions. @Darren, I was thinking you could animate the "how to download" sequence separately for each browser, so ins...

Any pointers appreciated as not spent much time using Xplain yet - although I know I really should be making use of its abilities for things like this. I imagine it's going to be something like... Have one "router" xplain that detects the browser, which then "chains" to the actu...

How can I insert this script into a specific point of my page and how do I replace the document.write with code to show specific image? Quick answer (I'm busy today!) rather than using an image, maybe think about putting the code into the start of a HelpXplain, and have it jump to the relevant inst...

The use case is for several pages on my website with instructions for customers to download an executable file - a lot of my user base are not very tech savvy so rather than lots of different instructions covering different browsers I wanted to only show the browser instructions relevant to the bro...

Looks like you have a solution. Would be interesting to hear more about the use case etc

Bowser might do it? I've not tried that personally but its GitHub repo has 4.4k stars and 460 forks, so probably isn't too shabby.

Dave Gehman wrote: ↑Wed Jun 10, 2020 4:23 pm Do I have this right: symlink = symbolic link or soft link?

Sorry, sloppy of me. I meant 'directory symbolic link' - have amended my earlier message

Looks like #MERGE is the way. [but] if I'm reading your docs right, the HTML files have to be on my computer (because #MERGE appears to work on sources that are stored relative to the H+M project). In this case, the desired HTML is on the Web, residing in a virtual folder that is different from the...

Your forums aren't going to be very helpful unless you fix the increasing problem of spam.

How about having a new forum for unlicensed users, with all the existing forums being writable only by users from licensed organisations?

Dave Gehman wrote: ↑Thu Apr 02, 2020 11:36 pmWe're maintaining version control manually

OK, I'll stop now

Dave Gehman wrote: ↑Thu Apr 02, 2020 6:03 pm I want to turn it off, not implement it

...unless you're using Github

Tim Green wrote: ↑Mon Mar 30, 2020 8:42 am Good luck.

Suggestion duly deleted

I would like the surrounding text to be shown as it makes it easier to spot relevant content. I think you need the "full" version of zoom indexer, and have to host the documentation on a CGI-enabled web server. You can read more in their documentation — seach for "context" and s...

The skin home/back/forward/print buttons all disappear when you uncheck the menu option. I didn't explain clearly. The home/back etc buttons in eWriter aren't from a skin, they are rendered by the eWriter host. You can achieve what you want, with the greatest degree of control, by publishing to eWr...

... this also removes the Back and Forward buttons (browser history). However, in my opinion, these buttons are essential for the usability of an online help system. Is there any way to get rid of the menu but to keep the buttons? You could publish using a skin that includes these navigation button...