Note: This section applies to BriteCore documentation, not other collateral.
Instead of directing a user to select a tab, direct them to select the element name itself.
|Select the Processing tab.||Select Processing.|
Never refer to screens as tabs. Full-demo doesn’t use tabs.
|On the Legacy Search tab, select Create a New Policy.||On the Legacy Search screen, select Create a New Policy.|
For screens in BriteCore that use internal tabs (those not in the main navigation, but rather in the middle of a screen), refer to its instances in the main navigation instead, or identify and refer to the element by name without tab.
Example of internal tabs:
Example of internal tabs reflected in the [Policies] menu:
|Scroll to and select the Information tab, and then, under Contacts, select Add Another Named Insured.||Select Information in the Policies menu. Under Contacts, select Add Another Named Insured.|
Select Information. Under Contacts, select Add Another Named Insured.
Note: Use your best judgment for which approach will be clearest to the end user given the context of the documentation you’re writing.
Going forward, don’t use the [Module] – [Screen] naming convention used in the ops-playground. Screens aren’t titled this way in full-demo.
Ops-playground example: Policies – Legacy Search
Full-demo: Legacy Search
|On the Policies – Legacy Search screen, select Create a New Policy.|
(This is titled this way only in ops-playground.)
|On the Legacy Search screen, select Create a New Policy.|
(This works with what the user will see in both the ops-playground and full-demo versions.)
|On the Settings – Business Locations screen, in the System Wide dropdown list, select System Tags.|
(Only ops-playground titles the screen as Settings – Business Locations. While both sites have dropdown menus, they are located in different places in each, and in full-demo, the System Wide dropdown in the Settings menu is already expanded by default upon accessing the Business Locations screen, thus displaying the System Tags link without user interaction required.)
|In the Settings menu, under System Wide, select System Tags.|
(This works with what the user will see in both the ops-playground and full-demo versions. Accessing the System Tags screen isn’t contingent on first being on the Business Locations screen. The System Wide submenu is already open when you access Settings, which is why this rewrite doesn’t indicate to first select it. Selecting System Wide in this instance would effectively hide the System Tags option.)
|On the Settings screen, select the Modules dropdown list, and then select Lines.||In the Settings menu, under Modules, select Lines.|
In the Settings menu, in the Modules submenu, select Lines.
Refer to the main menu only as the BriteCore menu.
|In the top menu, select Lines. (The menu isn’t always on top.)|
In the main menu, select Lines.
In the side navigation, select Lines. (The menu isn’t always on the side.)
In the sidebar, select Lines. (The menu isn’t always a sidebar).
In the navigation, select Lines. (This isn’t clear. There are multiple navigation levels.)
|In the BriteCore menu, select Lines.|
Note: Exceptions such as BriteApps’ Navigation Menu, where the menu name is titled on the screen, are still acceptable.
Secondary (module-level) menus
Refer to module menus by name when applicable. This isn’t required, but can add clarity. Use your best judgment.
Note: Don’t refer to module menus (Contacts, Lines, Policies, Claims, Reports, Settings, etc.) as submenus.
- Select Lines. In the Lines menu, select Notes.
- Select Lines, then select Notes.
Tertiary menus (submenus)
Some modules, such as Policies, have a tertiary menu (Payments).
While not required, you can refer to this menu level as a submenu.
- Select Policies from the BriteCore menu. Select Payments. In the Payments submenu, select Daily Cash Receipt.
- Select Policies, then select Payments. Select Daily Cash Receipt.