Skip to main content

Solutions

Law firms

Tax, audit & accounting firms

Corporations

Governments

Products

Legal

Trade & supply

Tax, audit & accounting

Corporate tax

Risk & fraud

Books

Recommended products

Questions? We are here to help.
Contact us

Purchase

Buy solutions

Buy books

Contact sales

Questions? We are here to help.

Resources

Insights

Events

Product training

Product communities

Developers

Article template styling test

Styling samples - task

This is a paragraph inside the "prereq" element where we put the prerequisites for starting this task.
This is a paragraph inside the "context" element. It's specific to task type topics.
  1. This is the first step. Following is a "menucascade" element:
    File
    Client Properties
    Notes
    .
  2. This is the second step. You need to go to
    C:/Users/[username]/Downloads
     to find the thing we need to keep going. That path is wrapped in a <filepath> element.
    This is text directly inside the "stepresult" element (no paragraph wrapper, if one needed we can do that). This is where we can say the result of this particular step (like "this random dialog box opens").
  3. This is the third step
    This is a paragraph inside an "info" element. Currently does not have any styling so it acts like a "div" or container element. OOTB, this element shows an "Additional information" heading.
  4. This is a "step section" element. It's intervening text where we can indicate that the rest of the steps are in another area of the program, for example, without interrupting the numbering of the steps overall.
  5. This is the fourth step
  6. This is the fifth step
    • This is the first choice
    • This is the second choice
    • This is the third choice
  7. This is the sixth step
    Choice
    Result
    If you choose the first option
    This is the result
    If you choose the second option
    Then this is the result
    If you choose the third option
    Then this other thing happens
    If you don't choose any of these
    Bad things happen
  8. This is the seventh step
    This is text directly inside the "steptroubleshooting" element. We can do paragraphs if needed. This is where we can put information about what to do if the reader doesn't complete this particular step successfully.
  9. This is the eighth step
    Example
    This is text directly inside the "stepxmp" element. This is where we can put examples for this particular step, including images.
  10. This is the ninth step
    1. Did you know DITA allows for exactly 1 level of substeps?
    2. That's what this is.
    3. You can't do an additional layer of substeps.
    4. We "cheat" and use the "info" element to make more substeps sometimes!
  11. This is the tenth step
This is a paragraph inside the "result" element where we can say what to expect after completing the task.
This is a paragraph inside the "postreq" element where we put information about what to do after completing the task.

This article applies to: