![]() The "hidden" TOC content will not appear on the TOC, but will be searchable.Ĭheck out this video demonstration of the process. On the Content Properties panel, select Hide in output. Contents 1 Features 2 Product history 2.1 Version renumbering 2. Put anything you want to be searchable in that section. (You can add all of your topics if you'd like.) in: RoboHelp Adobe RoboHelp Edit Adobe RoboHelp is a series of help authoring tools, developed and published by Adobe for Windows -based computers. The solution is to create an extra section on the TOC. If you want to keep your TOC streamlined, but the TOC is tied to Search, what's a RoboHelp developer to do? Because users will first rely on Search, keeping the content on the TOC streamlined is a great idea. However, if a topic is not on the TOC or referenced by a link or cross reference by something on the TOC, the topic won't be searchable. One thing to avoid in a TOC is bloat-a TOC that has so much content that it's difficult, if not impossible, to find anything quickly. Of the three, Search wins the award for being the most used feature. ![]() You then need to change the path in two places in each font’s CSS file: for the EOT reference and the TTF (or OTF) reference.When I teach RoboHelp, I tell my students and the three main areas users will rely on to get help in a help system are the table of contents ( TOC), Index, and Search. I keep it simple, and place the fonts folder directly below the stylesheets folder (in Flare, this is in Content/Resources/Stylesheets). By following step-by-step instructions, you will learn. 'Adobe RoboHelp HTML 11: The Essentials' is a self-paced, step-by-step workbook that will teach you the essential skills needed to create and deliver user assistance (Help systems, policies and procedures, and knowledgebases). Note: To generate the Mobile App output, see Generate mobile apps using Apache. The following tables describe all options available in the Outputs tab. The only change you need to make in the CSS files is to specify the path to the fonts folder. Orders placed after 2 PM Eastern may ship the next business day. The Outputs tab of the Publish Settings dialog provides options to customize publish output format settings such as the title, favicon, layout, and table of contents (for eBook output formats). I downloaded and used the Gentium serif font for body text, and the PT Sans sans-serif for headings. It’s easy to use, reduces clutter in your CSS files, and allows you to easily swap fonts by referencing a different CSS file. RoboHelp is extremely powerful and yet easy to use. Easily show or hide widgets such as glossary and TOC. Deliver a superior content experience using the new Frameless Responsive HTML5 layouts with intuitive navigation, unique URLs for SEO, and best-in-class search. I like this modular approach to the font files, originally shown to me by John “VSC” Zavocki at a Drupal meet-up. Next-generation Frameless Responsive HTML5 layouts. All you need to do is change the path to your fonts on the server or local machine ( not the windows/fonts folder), and then add these CSS files to your Flare project. These kits include the CSS file for the font, which defines the properties you need, and the font files. Since 95% of the work is done for you (did I also mention free?), we’ll use Font Squirrel’s font face kits. IE supports the EOT format, while most other browsers support TrueType (TTF) and some OpenType (OTF) format fonts. All major browsers, including Internet Explorer 7, 8, and 9, Firefox, Chrome, Opera, and Safari, currently support using the font-face attribute, but of course they are implemented differently. The CSS and font files are quite small, taking up only a few kilobytes each, so it shouldn’t add a lot of overhead to your projects. You can use the fonts locally, in addition to on a server. This should work similarly in Adobe Robohelp. MadCap’s Flare help authoring tool (HAT) uses CSS to style its WebHelp, so you can easily embed fonts into your help. There are thousands of free fonts out there, but not all font creators support font embedding, so be sure to read any license agreement before using them in your projects. The web site Font Squirrel creates the CSS for you, using only free, embeddable fonts. However, you can also save and host freely available font files on your company’s web server, or install on your users’ PCs, and use these fonts in your WebHelp projects. New technologies have sprouted up, with Google creating its own font API, and Adobe announcing font support through TypeKit. Have you ever been bored using Georgia, Tahoma, Verdana, and (sigh…) Arial over and over in your help projects? The font-face property has been available for some time in Cascading Style Sheets (CSS), but browser and font foundry support are only now allowing use of fonts other than those that ship with operating systems and applications, without workarounds like sIFR and cufon. It requires knowledge of HTML, CSS, and a help authoring tool such as MadCap Flare or Adobe Robohelp. ![]() This story is for intermediate to advanced help developers. ![]()
0 Comments
Leave a Reply. |