.do-dont{display:grid;grid-template-columns:1fr 1fr;gap:16px;margin:16px 0}
@media(max-width:640px){.do-dont{grid-template-columns:1fr}}
.do{border-left:4px solid #1A7F5A;padding:12px 16px;background:#F0FDF4;border-radius:0 4px 4px 0}
.dont{border-left:4px solid #B91C1C;padding:12px 16px;background:#FFF5F5;border-radius:0 4px 4px 0}
.do-dont-label{font-size:11px;font-weight:700;text-transform:uppercase;letter-spacing:.08em;margin-bottom:8px}
.do-label{color:#1A7F5A}
.dont-label{color:#B91C1C}
.do-dont-content p{margin:0;font-size:13px;line-height:1.6}
.related-pages{margin-top:32px;padding-top:20px;border-top:1px solid #E5E7EB}
.related-pages h3{font-size:13px;font-weight:700;text-transform:uppercase;letter-spacing:.06em;color:#6B7280;margin-bottom:10px}

# Navigation and menus

Navigation patterns in Petrel include the Ribbon, context menus, pane toolbars, tree navigation, and workspace tabs. This page covers context menus, toolbars, and in-pane navigation patterns.
## Context menus

Context menus provide access to object-specific actions via right-click (or keyboard equivalent: Shift+F10 or the Menu key). Use context menus for secondary and object-specific commands that complement the Ribbon.

Context menu items must be ordered from most to least frequently used, with destructive actions separated by a divider at the bottom. The maximum number of items in a context menu is 12 — beyond this, use a submenu.

## Pane toolbars

Many Petrel panes have a compact toolbar along the top or side edge for pane-specific commands. Pane toolbar icons follow the standard icon sizing (16px), always have tooltips, and implement keyboard access.

## Tree navigation

Petrel uses tree views extensively for object hierarchy navigation (well trees, data trees, project trees). Tree navigation must support:

- Arrow keys to move between nodes (Up/Down) and expand/collapse (Right/Left)
- Home and End to jump to the first and last visible node
- Type-ahead search — typing a character jumps to the first item matching that character


## Do and Don't

DO
Mirror the most critical context menu actions in the Ribbon. Users who discover a command in the context menu expect to find it in the Ribbon too — and vice versa. Keep the two command surfaces consistent.
DON'T
Don't create more than two levels of submenu nesting. Deep menus are difficult to navigate and hide commands from users who don't know to look there.
### Related pages

Ribbon
Keyboard and focus
Custom controls
— Tree view accessibility