1 person found this helpful
I'll try to address some of these.
- For years we have generated WebHelp and used the topics on their own, without using the main help "start" file, because we wanted a single frame, not the tri-pane look. Each topic has a header that we include using the templates/master pages. The header includes icons that work as a "back" button and links to the TOC and Index, as well as a print icon and a search field. If the user clicks the TOC or Index, that opens in the main window instead of the text from the previous topic. I had hoped that we could make a screen layout with this approach (since we are also interested in multi-screen layout for tablet and desktop support), but I'm still not seeing a way to get a simple topic window with a header. Is that possible?
Nothing really changes between 8 and 10 in this respect. You should still be able to generate as you did before. But your mention of wanting a "screen layout" seems that you are wanting to delve into the fun brave new world of HTML 5. Good luck with that! I'll have to let Willam or another that has lots of HTML 5 experience answer that one.
- I'm also not seeing a way to create your own screen layout from scratch. You seem to have to start with one of the layouts that are included. Is that correct?
I believe it's possible to create your own layout. But it's certainly NOT the most intuitive process and it's one I honestly hope Adobe will simplify in a future build so that us mere humans are easily able to create and customize our own HTML 5 layouts without requiring a PHD and 40 years experience coding HTML 5 and CSS. As it stands, it's not a process for the faint of heart.
- If we wanted to be able to search across multiple generated help projects, would we need to merge the help projects?
Since the first two questions seemed to be HTML 5 (Multiscreen) centric, are we to assume this one falls into that area as well? If so, again, Willam or someone with HTML 5 Multiscreen skills will have to advise. I'm unsure if merging is even possible using that output type.
1 person found this helpful
Just to add to Rick's reply, serious editing of the screen layouts does require CSS skills more of the level of a web site designer than a technical author. As for starting from scratch, think of flying a plane without tuition.
See www.grainge.org for RoboHelp and Authoring tips
Thank you both for your responses. It's a little frustrating to me that after all this time there is still so little control over the structure of the page. That makes the Multi-screen output less useful to us because we are tied to pre-defined looks for the help.
After playing with this a bit more, it appears I might be able to get the look I want with a little work in the HTML. I'm looking into this more. Thanks for your responses!
I think we are all use to the good ol' WebHelp Skin Editor which was very WYSIWYG. But, the reality is that HTML5 and especially, the CSS part of it, is very complicated because of the variables and variety of devices.
I am not a CSS expert by any means, but I was able to create and make some modifications to existing Screen Layouts. I finally got some help from Willam van Weelden (see below)
I'm sure there will be improvements in future versions, but for now I highly recommend these things:
1. Visit Willam van Weelden's website. He is the acknowledged expert on HTML5 output and has some useful items on his blog.
http://www.wvanweelden.eu/product-category/multiscreen-html5-layout (there are other related pages on his site as well)
2. The new Adobe RoboHelp Product Manager, Vikram Verma, has just posted an article on this subject here:
3. Take a look at a free recording of an hour-long webinar which I conducted with Willam as my guest.
You'll find a link to the webinar here:
(Scroll down to this sub head:
Multiscreen HTML5 for multi-device publishing with Adobe RoboHelp 10
Hope this helps.
Adobe Certified RoboHelp and Captivate Instructor