15. ‹#›
Content area is a
bucket we fill with
HTML generated from
DITA source.
Framework container
manages navigation,
SCORM
communication, and
features.
21. ‹#›
Promise:
Timely. Relevant. Mobile.
Avoid vendor lock-in by
leveraging web standards
and open-source plugins.
Adapt to business changes, like
new branding, more quickly
than would be possible with an
off-the-shelf solution.
Retain control over
framework behavior and
can add new features
and activities as needed.
But we are always in
development.
32. ‹#›
Promise:
Timely. Relevant. Mobile.
Avoid vendor lock-in by
leveraging web standards
and open-source plugins.
Automatically assess
quality by reporting on
language and
engagement metrics.
Minimize code maintenance
by leveraging the DITA Open
Toolkit.
36. ‹#›
Storyboard
{
type: "interaction",
layout: "texttop",
interaction:
{type:"sequence",
feedback: "“ }
}
<div class="contentBlock sequence ">
<h2 class="title sectiontitle">Test Your Knowledge</
h2>
<div class="body blockBody">
<div class="note ctxDirections directions"><span
class="notetitle">Directions: </span> Place the
following steps in the correct order. </div>
<ol class="ol sequence">
<li class="li questionSet">
<div class="itemgroup questionBlock"></div>
<ol class="ul choices">
<li class="li correct">A user logs into Receiver.</li>
<li class="li correct">StoreFront passes the credentials
to the Controller.</li>
<li class="li correct">The Controller queries Active
Directory and the site database. </li>
<li class="li correct">The user launches an application
from Receiver.</li>
<li class="li correct">StoreFront sends an ICA file to
Receiver.</li>
<li class="li correct">The VDA verifies a license is
available.</li>
<li class="li correct">The application is displayed to the
user.</li>
</ol> </li>
</ol>
</div>
</div>
40. ‹#›
Pros and Cons
Pros
• No manual coding
• All template based
• Consistent input and output
Cons
• Manage XML markup
• Building new templates
• Ramp up for new authors
41. ‹#›
Promise:
Timely. Relevant. Mobile.
Avoid vendor lock-in by
leveraging open-source
standard.
Future-proof content by
automatically generate
HTML5 now, and later, 6
or 7….
Adapt to changing package
requirements because
content is highly
reconfigurable.
