We have many tools for delivering content to mobile. Now it's time to focus on the content!

1. a 45 #techcomm minute presentation by @mattrsullivan at #stc14, May 19, 2014
Delivering tech
comm to mobile

2. Thank you, Adobe
Kapil Verma, FrameMaker
Vikram Verma, RoboHelp
Saibal Bhattechargee

3. Nicky Bleiel
Paul Mueller
Lloyd Tucker
Development and Delivery Track
• Michelle Despres
• Stephanie Donovan
Thank you, STC

4. Software demos
cause 83% of all
presentation
fatalities

5. A bit of history
Background in Print
• Tough to leave LTR delivery
FrameMaker, RoboHelp
eHelp RoboHelp for FrameMaker - 2004
TCS - 2007
TCS4 - 2012
TCS5 – 2014

6. And then the “Ah ha” moment

7. LavaCon Oct 2013
Joe
Gollner
Bernard
Aschwanden
Matt
Sullivan
Joe
Welinske
Neil
Perlin
Val
Swisher
Thomas
Aldous
TechComm Deathmatch 2013

8. What did the
panelists all have
in common?

9. Structure
Or at least, consistency
XML/DITA/S1000D/ATA/MILSPEC
DocBook
Pseudo-Structure

10. Lots of conversations
Same goal
Different reasons

11. So what are the
advantages of
structure for
mobile?

12. LavaCon Oct
2013
Mobile
Accessibility
Localization
Content reuse
SEO
Regulatory
Rich media
Structure

13. Tools are
necessary

14. Translation
We focus on our own needs, rather
than the needs of the person seeking
information

15. Standards are necessary
Need to work backward from the goal
to arrive at the process.

16. Establish user’s needs first,
then choices/combinations
of tools are more obvious

17. So why is tool choice
important?

18. Responsive
output

19. Handling of rich
media

20. Ease of
processing

21. Intuitive editing,
creation tools

22. Ability to
brand/skin output

23. Situations benefiting
from a
FrameMaker-centric
workflow

24. Structure
Medical devices example
Localization

25. History of LTR docs, PDF
delivery

26. Highly referenced, reused

27. Rich media

28. When using rich media and
graphics, ensure these two
acronyms DO NOT apply:

29. PEBKAC

30. The dreaded
ID – ten - t
error

31. ID10T

32. Few(ish) electronic
outputs/versions

33. Situations
benefiting from a
RoboHelp-centric
workflow

34. You have a history of online
help delivery

35. Role-based (conditional)
output

36. Many output formats

37. And finally,
Context sensitive help (CSH)

38. Sophisticated print and
complex electronic output
Link FrameMaker content to RoboHelp
output for the greatest degree of
control

39. And remember…
Mobile delivery starts with the needs
of the end user, and moves
backward from there!

40. My remaining STC Summit
Presentations
Tuesday
11:30 Adobe Booth Presentation:
Using XML Author (15 minutes)
2:15 Progression:
Tips for new presenters (15 minutes)

41. TECHCOMM TOOLS
Helping folks with
 Tech Comm
 Video
 eLearning
 Content marketing

42. @mattrsullivan
youtube.com/user/tc2ls
youtube.com/user/mattrsullivan
twitter.com/mattrsullivan
facebook.com/mattrsullivan
linkedin.com/in/mattrsullivan
forums.adobe.com/people/mattrsullivan
Delivering Tech Comm
to mobile
MATT SULLIVAN