Doc-To-Help 2012 has a new Mobile Help output that is browser-based, and easy to create.
First I would like to point out that Help on mobile devices doesn’t have to be traditional Help (it absolutely can be, but it doesn’t have to be). It can be something completely different that can benefit people using mobile devices. Doc-To-Help includes 3 samples — one is a knowledgebase for a service team (“Brew Crew Answer Station”), one a tourism resource (“Pittsburgh Fun”), and one is Help for the fictional game named “Peeved Penguins.” These projects are a great starting point for trying out Doc-To-Help’s Mobile Help, and they may also inspire you to create something new and useful for your customers.
Structuring your project while writing it
Now we can use the “Brew Crew Answer Station” sample to discuss structuring a Mobile project. This sample contains one document, and that document has a fairly traditional structure that works well in both online and print outputs. This structure will also work for Mobile Help.
Doc-To-Help creates Help topics based on Styles, and uses those styles to create the Table of Contents for the project. The “Brew Crew” sample uses only the Heading 1 and Heading 2 styles, so the “home page” of the Mobile version will display all the Heading 1 topics, then users will tap to view to the Heading 2 topics nested under them. You can add more heading levels (H3, H4) and make a deeper table of contents, but for Mobile Help, keeping the table of contents “shallow” can make it easier for customers to find information. It is also a good idea to keep the Headings short, so that users don’t need to “wipe” to read the TOC.
Here is the Table of Contents of the “Brew Crew” project in Doc-To-Help, along with the style used for each topic. It is a single Word file, with 9 Heading 1′s — and each Heading 1 has two or more Heading 2′s under it. Doc-To-Help creates the TOC automatically for you, based on the Heading styles:
If you’d like to take a look at the document this TOC was generated from, click to open the Brew Crew Answer Station Word document. (Please note, the olive color text in the document indicates that those items have been added to the index — that color will not appear in the final output.)
When you build the Mobile Help, it will look like this:
The user can tap on the first item to read the introductory topic, and every other TOC option will display the Heading 2′s nested under it.
If you’d like, you can display the default topic for the project instead, just by selecting one check box in Doc-To-Help.*
Here is what the Mobile Help will look like on your device if you display the default topic as the “home page.” If you tap the Contents button on the top, the TOC will display. The “Related Topics” list at the end of the topic also lists the TOC entries, so your customers have another sensible navigation option.
So with Doc-To-Help’s Mobile Help, you have two different display options. An additional feature: if you don’t create an index, the Index button will not appear at the top of the display automatically — only the Contents and Search options will be displayed.
The “write topics first, create structure later” method
You don’t have to structure your project exactly as I described; you can create separate files for each topic, and arrange them later in the Doc-To-Help Contents Pane. The “Peeved Penguins” Sample project uses this method (the source documents for this project were written in the built-in XHTML editor, but you can do this with Word also). Here are the documents I created — each one contains 1 topic, each beginning with a Heading 1 style.
In the TOC, I created a “book” for each category, then dragged the appropriate Topics into each one. See below to view the resulting Table of Contents in Doc-To-Help and in Mobile Help. The “books” in the TOC do not contain any content, they are merely containers that organize your topics. Structuring your project in this way gives you the flexibility of working with individual topics, while still creating well organized and usable Mobile output.
Now that you have some examples, you can see how easy it is to structure a project for Mobile Help. In Part 2 Mobile Tips and things to consider, we’ll discuss some other Mobile tips and tricks.
Have fun creating Mobile Help!
About that check box …
* I mentioned a check box earlier that will switch your Mobile Help “Home page” from a TOC to a topic. That check box is in the Theme Designer. Click on the Edit Theme button and in the General category, select the “Show Topic At Startup” check box.









Nicky,
I just tried the new mobile help target, and upon initial experimentation it works freakin’ GREAT right out of the box. And my Word source file is heavily laced with conditionalization and variables and many screenshots. But so far so good, and you can bet I’ll be experimenting with it more. I actually can’t wait to show it off and see the reactions…
Thanks! –Chet
Cool beans Chet! Keep us posted!
So far so good. It shows really well, and I have the green light to deploy it with our production helpfile soon… I created a custom “Helpfile for Mobile” button in our NetHelp 2.0 build (using instructions from one of your other blog posts) — from which users can just launch the mobile version.
Nicky, the mobile jquery-ui theme is limited to one called Basic. OK… Will there eventually be more available themes for mobile, and/or support for custom themes for mobile? Or is that already in place and I just need to fish around and experiment? Or…?
Thanks. –Chet
That is great news! To answer your questions — #1, we do plan to provide more Mobile themes, but I don’t have an ETA on those — I will keep you posted. #2 — you can customize the “basic” theme. The docs will help you get started on that. See http://helpcentral.componentone.com/nethelp/d2h2012/#!WordDocuments/customizingnethelp20mobilehelpandeclipsehelpthemes.htm