Pages: 1
Print
Author Topic: Navigation Syntax with a Command  (Read 2272 times)
kwag_myers
Member

Posts: 69


« on: September 09, 2010, 01:27:45 PM »

I need to come up with a standard way of telling users how to get to several pages that, well, are buried so far into the application that you can't get there from here. Users have to navigate to a certain page, select a data element and click the Edit button. The result of this is a whole new world of pages, menus, and navigation bars (A.K.A. Outlook Bars). It goes something like this:

Home>First Layer; Edit the desired item; NavBar>Another Layer, etc.

Is there a better way to express this?
Logged

XMetaL 6 Author in Windows 7 Home Premium
Derek Read
Program Manager (XMetaL)
Administrator
Member

Posts: 2621



WWW
« Reply #1 on: September 09, 2010, 03:21:14 PM »

Does it make sense in your context to use a DITA <steps> element for this?
(see the DITA Language Reference for suggested usages)

<steps> is valid inside a DITA task.

Maybe something like this?

<steps>
 <step>
  <cmd>From the main menu select
   <menucascade>
    <uicontrol>Home</uicontrol>
    <uicontrol>First Layer</uicontrol>
   </menucascade>
  </cmd>
 </step>
 <step>
  <cmd>Press the <uicontrol>Edit</uicontrol> button to edit the desired item.</cmd>
 </step>
 <step>
  <cmd>From the main menu select
   <menucascade>
    <uicontrol>NavBar</uicontrol>
    <uicontrol>Another Layer</uicontrol>
   </menucascade>
  </cmd>
 </step>
 <step>
  <cmd>etc...</cmd>
 </step>
</steps>
« Last Edit: September 09, 2010, 03:23:56 PM by Derek Read » Logged
Pages: 1
Print
Jump to:  

email us