RoboHelp 11 Can Do That? Anatomy of a Project …Wednesday, July 23 2014 @ 12:51 PM, By Maxwell Hoffmann
Although many of us are aware of RoboHelp 11’s power, it is always refreshing ot have an eye-witness account from the field, delivered by professionals who don’t work for Adobe. In late July we had a refreshing webinar from Tanner Services Corporation on “I Didn’t Know RoboHelp Could Do That!‘ [Click on the title to launch the webinar recording.]
This brief blog summarizes highlights and provides minute markers so you can fast forward to key concepts.
Technical Solution based on 3 advanced features
[4:45] Shelley Bates explains how 3 main features were used with the project described:
- Multiple merged projects
- Dynamic User Centric Content (DUCC)
- Resource Manager and Synched Assets
Two Sets of Requirements
[5:00] The following slides shows the complexity of two sets of requirements from the project’s client
The number of locations and policies in the 2nd project radically increased the complexity. The client fit a typical profile of companies who are struggling to move away from paper P&P and move to friendly, online formats.
[07:00] Multiple Merged Projects
Definitions of Parent and Child level projects are discussed. Tanner Services also introduces the 3-levels of basic file structure employed.
Emphasis was placed on the importance of which order steps are taken.
[09:00] File Structure – Plan Ahead
Simple illustrations make file structure obvious. The importance of main structure is emphasized and the point of separating project files from content. The project example employed WebHelp.
[11:00] Child Projects Explained
At this point of the webinar, Tanner Services shares a more detailed diagram illustrating how parallel “child” project folders are employed for “Admin,” “Customer Service,” and “Maintenance.” This division is typical of most projects.
[13:00] Knowing where to point the Output Files
The importance of pointing child project output to the correct location is vividly illustrated.
[15:00] Single Source Layout (SSL)
Importance of having a blank “shell” project file folder is illustrated.
[17:00] File Structure for Operations Merged Help File Explained
[20:00] Multiple Merged Projects with DUCC (Where things get Tricky)
[22:00] Organizing RoboHelp projects based on their relationships
[24:00] Knowing where to point output files for DUCC
[28:00] Importance of output paths for Child Projects in Single Source Layout (SSL)
[30:15] File Structure Comparison
[32:20] Live Demo of DUCC in Project with 3 “Child Levels”
[36:40] Resource Manager and Synched Assets explained
[40:00] Advice on which features to use and project planning
[41:30] Summary of useful Resources
(note: bulleted items on slide at this point are hyperlinked)
[54:00] Final questions and sharing of resource URLs in the chat pod