Option Description Click in the same window To open the perspective in the same window. When you open the window, it replaces the currently open window. Click in a new window To open the perspective in a new window. When you open the window, it opens in a new window and the currently open window remains open.
Task with unordered steps
Bullets instead of numbers
<steps-unordered> element
Task topics: Results
DITA element: <result>
Illustrates the successful completion of the task
Example:
The device is fully configured and ready for use.
Task topics: Example
DITA element: <example>
Illustrates a successful completion of the task steps.
<example> is a type of <section> element
Task topics: Postrequisites
DITA element: <postreq>
Things that users need to know or do upon completing the task steps.
Workbook Exercise: Task Topics
Cross-references and links
Types of links
Inline links <xref>
Cross-reference <xref href="#target"/>
File reference <xref href="file.typ"/>
Web link <xref href="http://..."/>
Related links <related-links>
Links generated by relationship tables
Inserting links
Insert > Link > ...
Cross-reference
File reference
Web link
All add <xref> elements
Related links added at end of topic
Refreshing References
To update content in cross-references:
Click Edit > Refresh All References
Close and reopen the document
Workbook Exercise: Cross-references and Links
Metadata and index elements
Metadata in DITA
Maintained in <prolog> element
Examples: author, publisher, copyright information
Metadata is usually company-specific
Click Insert > Topic Metadata This dialog can get you started, but best to create your own
Indexing
Use <indexterm>
Can nest <indexterm> elements
Cannot put in <title> elements
Place <indexterm> where appropriate
DITA Open Toolkit will compile an index
Creating index entries
Click Insert > Index Marker
Tip: Press Alt+Shift+X
Use commas to create subentries
Editing index entries
Braces ({ and }) are XMetaL
Index entry:
Nested index entry:
Nested entry produces:
“ Stylesheets, troubleshooting....37”
Advanced indexing features
DITA 1.1
Page ranges
See/See also
Sort as
Workbook Exercise: Metadata and Index Elements
Track changes
Purpose:
Communicate to reviewers about what’s new
Have reviewers communicate about what they want
Help you manage your writing process
XMetaL uses processing instructions to track changes
Track changes
Using change tracking
Turn on and off:
Tools > Track Changes
Accept/reject changes:
Tools > Accept or Reject Changes
Can also use: View > Toolbars [Reviewing]
To change styles:
Name: Tools > Options [General]
Format: Tools > Options [Change Tracking]
Workbook Exercise: Track Changes
DITA Maps
DITA maps
Organize DITA topics in a TOC-like structure
References to DITA topics
Analogous to a FrameMaker Book file
Can also contain topic metadata
Topics and maps
Topic
Unit of information that is meaningful when it stands alone
Map
Organizes topics into a coherent set
Typically for different deliverables or media
Topics DITA Maps Deliverables
Working with maps
Map Editor displays maps in a GUI
You can:
Add and remove topics
Change topic order
Nest topics
Edit with drag and drop or toolbar buttons
Change map properties
Insert a reference to an existing topic
Select the map entry under which you want to nest the topic
Click Insert > Topic Reference
Browse for a topic
Tips for working with maps
Plan where to put your map and topic files
usually close to each other
Remember file and folder naming rules:
no spaces, no special characters
Make sure you’re using files in the location you think you’re using
Insert and create a topic
Select the topic above where you want the new topic
Click Insert > Topic Reference
Insert a topic heading
Click Insert > Topic Heading
Create a new map
Click (small) File > New Map.
or
Click (big) File > New
Then choose the DITA Map template
Insert a submap
Both maps must exist
Click (small) Insert > Map Reference
Specify map properties
In the Map Editor, select the Properties button.
In the Map Properties dialog, click the Special Attributes tab
Interesting attributes include:
Navigation title
Scope
Include in TOC
Print
Workbook Exercise: Organizing Topics with Maps
Switch to XML view
Click (small) File > Switch to XML View of Map.
Switch to Map Editor
Select File > Switch to Map Editor
Different views for different tasks Task Map editor XML View Create the table of contents, a.k.a. the “hierarchical” part of the map Browse topics by double-clicking Edit relationship tables Use conditional text to make parts of the map conditional Troubleshoot
Relationship tables
Automatically generate “Related x” sections
Special type of semantic table
Columns define information types
Rows define relationships between topics
Each <topicref> in a cell will link to the other topic references in that row
Can control linking
Map metadata
Metadata in maps
can fine-tune linking in relationship tables
can be used instead of topic metadata
is inherited from parent elements
Relationship Tables: XML View
Create a relationship table
Switch to XML view
Insert the relationship table
Add the <topicref> elements
Generate the map
Review the links
Update the relationship table
Generate and review
Switch to Map Editor
Insert a relationship table
Click Table > Insert Relationship Table.
Choose one of several common formats, then click OK:
Attributes for managing links
In a <relcell> element:
collection-type = “family”
topicrefs in cell link to each other
linking = “targetonly”
topicrefs can be targets, but cannot be links
linking = “sourceonly”
topicrefs can be links, but cannot be targets
Add topics
Hold CTRL and drag Task topics from the navigation portion of the map into the relationship table. This copies the <topicref>.
Think of the Concept and Reference topics that are related to each Task. Paste <topicref>s for those topics on the same row.
Generate the map and open the file.
Workbook Exercise: Relationship Tables
Glossaries
Glossaries
Writing glossary content
Assembling glossary content
Glossary content
Basic markup:
<glossentry>
<glossterm></glossterm>
<glossdef></glossdef>
</glossentry>
One or more <glossentry> elements in a file
Specialization of <concept>
DITA 1.1
Assembling glossary content
Create a Bookmap file and point the <glossarylist> element to your glossary content files.
Add a <topicref> to your map file pointing to your Bookmap file.
Publishing glossaries
During “Generate Output”: All glossary content is pulled into the same glossary and is sorted alphabetically.
Reusing content
Content reuse: overview
Reuse is about reducing duplication and delivering more customized content
If you make selected text conditional, XMetaL inserts <ph> tags so it can “hang” attributes on the <ph> element.
Style conditional text
Styles help keep track of conditional text
XMetaL only, not in deliverables
Reuse > Style Conditional Text
Generate conditional output
Choose what platforms, products, and audiences you want to include
How DITA handles multiple condition types For an element marked as audience = “Europe” and platform = “windows” *Would appear if you used native FrameMaker ® 7.x conditions instead of DITA In output for this audience and product: Does the element appear? Notes Europe Macintosh No* The element is for the right audience. The element is not for the right platform. North America Windows No* The element is not for the right audience. The element is for the right platform. Europe Windows and Macintosh Yes The element is for the right audience. The element is for one of the right platforms.
Multiple condition types: the rule
In this example: Content must be for both the right platform and the right audience in order to be included.
The general rule: An element is included if, for each attribute mentioned in Show/Hide Conditional Text:
It doesn't have any values for that attribute, i.e. it is "common to all"
OR it matches at least one value that should be included.
Planning to use conditional text
Determine your team's needs in terms of content reuse:
What product variations are similar enough they could be documented through one set of source files?
What audiences do you want to customize documentation for?
Would it make sense to achieve reuse through conditional text, through content modularization, or both?
On output, content from referenced element substituted for the conref element
Similar to FrameMaker “text insets”
Analogous to referencing an image file
Content references in XMetaL
Content shown in conref is:
Read-only
Updated when a document is opened
To manually refresh:
Click Edit > Refresh All References
Or press F11
Working with content references
Open a document containing a content reference
Right-click to switch between viewing local content and referenced content
Local content is highlighted in yellow
Reusable components
Reusable components:
Managed snippets of XML
Have titles, short descriptions, and reusable-content.
One reusable component per file
Click Reuse > Create Reusable Component
XMetaL only; not transportable
Reuse strategies Reuse Opportunity Solution Multiple similar deliverables Flag some content as conditional Piece of content used in many different contexts Include it in different topics using content references (Modular reuse) Topic used in many different deliverables Include it in different deliverables through DITA maps (Modular reuse)
0 comments
Post a comment