CommandMenu

OverviewExamplesPropertiesSlotsMethodsEventsCSS PropertiesDependenciesUsageIntegration

Command Menu allows users to navigate and use an app without touching the mouse and helps them transform into “power users” who can harness more advanced features far faster.

Loading...

Properties

PropertyAttribute Description TypeDefault
openopenShow or hide the command menu.booleanfalse
externalFilteringexternal-filteringUse external filtering mode. When set to true, the component will not perform internal text-based filtering and expects external filtering logic to be implemented.booleanfalse
exitNestedOnSearchexit-nested-on-searchWhen enabled, typing in the search input will automatically exit nested views to allow global search across all commands.booleanfalse

Slots

Slot name Description
footerUsed to replace the default footer contents.

Methods

Method nameParameters Description
show(options: { parent?: string }, options.parent: unknown) => voidoptions: Options for showing the menu.
options.parent: Opens the menu filtered to a specific parent command.
Show the command menu programmatically.
close() => voidN/AClose the command menu programmatically.
focus() => voidN/AFocus the command menu's input.
EventDetail TypeDescription
openNordEventThe command menu was opened.
closeNordEventThe command menu was closed.
inputNordEventFired as the user types into the search input.
nord-selectSelectEventUser selected a command from the menu.

CSS Properties

CSS Custom Properties provide more fine grain control over component presentation. We advise utilizing existing properties on the component before using these.

PropertyDescriptionDefault
--n-command-menu-inline-sizeControls the max inline size, or width, of the command menu.640px
--n-command-menu-block-sizeControls the max block size, or height, of the command menu.290px
--n-command-menu-block-startControls the command menu offset from the block start, or top, of the screen.16%

Usage

This section includes guidelines for designers and developers about the usage of this component in different contexts.

Do

  • Use to provide global and contextual keyboard shortcuts for users.
  • Make command menu available everywhere. Users must be able to bring up the command menu easily.
  • Make command menu central. Users should be able to find global shortcuts from one location.
  • Make command menu omnipotent. Give users access to every possible action.
  • Group related commands logically under sections with the section setting.
  • Use Alt key as the modifier, since this is less likely to clash with existing shortcuts.

Don’t

  • Don’t make command menu available only in certain views of the application.
  • Don’t define shortcuts such as Ctrl+C, since this will clash with the native "Copy" shortcut.
  • Don't create complex shortcuts, as users will struggle to remember them.
  • Avoid using KeyboardEvent.key for defining the shortcut keys.
  • Don’t use as a search field only.

Content guidelines

Command titles should be clear, accurate and predictable. It should be possible for the user to understand what will happen when they execute a command:

Start consultation
Consultation

Always lead with a strong verb that encourages action. To provide enough context to user, use the {verb} + {noun} content formula:

Open dashboard
Dashboard

When writing command titles, always write them in sentence case, not title case. The first word should be capitalized and the rest lowercase (unless a proper noun):

New appointment
New Appointment

Avoid unnecessary words and articles in command titles, such as “the”, “an” or “a”:

Change theme
Change the theme

Avoid ending in punctuation:

Switch user
Switch user.

Use ellipsis in the title when describing sections that have commands grouped inside of them:

Change theme…
Change theme

Commands data

Each command in the commands data array must include at least an id and title. A command may also include properties for section, icon, handler, shortcut , parent, and keywords:

NamePurpose
idAn identifier for each command, must be unique. Example: id: "user".
titleThe title shown to users. This is used when searching for a command. Example: title: "Change theme...".
keywordsNot visible in the user interface, but can make it easier to discover commands through search. Example: keywords: "command change log sign out in".
shortcutThe keyboard shortcut. Example: shortcut: "Alt+KeyU". See the sections Defining Shortcuts and Choosing shortcuts below for more information.
sectionUsed for grouping many commands under a common header. Example: section: "Commands".
iconA name of an icon form Nordicons to show beside the title. If not specified, default command icon will be used instead. Example: icon: "file-picture".
parentThe id of a parent command. This is used for nesting commands. Example: parent: "theme".
handlerA function to execute when an user triggers a command. Example: handler: () => { alert("Change to light theme") }. In cases where a command is only used as a parent command e.g. "Change theme", this is not required.

Defining shortcuts

Shortcuts in the Command Menu have the following form: [modifier]+[key]. Shortcuts are made up of a sequence of presses. A press can be as simple as a single key which matches against KeyboardEvent.code:

Copy code
// Matches: event.code:
'KeyD'

Presses can optionally be prefixed with modifiers which match against any valid value to KeyboardEvent.getModifierState().

Copy code
'Control+KeyD'
'Meta+KeyD'
'Shift+KeyD'
'Alt+KeyD'
'Meta+Shift+KeyD'

There is also a special $mod modifier that makes it easy to support cross platform keybindings:

  • Mac: $mod = Meta (⌘)
  • Windows/Linux: $mod = Control
Copy code
'$mod+KeyD' // ⌘/Ctrl + D
'$mod+Shift+KeyD' // ⌘/Ctrl + Shift + D

The Command Menu itself can be opened using ⌘+k (or Ctrl+k on Windows) and closed by hitting Esc. These are both non-configurable shortcuts in order to unify the experience across our platforms.

Choosing shortcuts

When choosing shortcuts, it is very important that they do not clash with native operating system or browser shortcuts.

For example, you should not define a shortcut like $mod+KeyC, since this will clash with the native “Copy” shortcut, and will be triggered every time a user copies text in the app. Nor should you use shortcuts like Shift+KeyA since this will get triggered whenever a user types an uppercase “A” character. Therefore, special care and attention must be given to each and every shortcut choice.

In general, we recommend using the Alt modifier, since this is less likely to clash with existing shortcuts. However, be aware, the Alt key is also used for accented characters e.g. Alt+KeyA produces the letter “å”. Again, it is crucial that you choose shortcuts carefully.

You should strive to choose shortcuts that are intuitive and easy to remember. The more complex a shortcut, the less likely a user is to remember it. Of course, a user can still find a command by searching the command menu, and for some users this may be their preferred way of triggering commands.

Common keybindings

Keybindings will be matched against KeyboardEvent.key and KeyboardEvent.code which may have some names you don’t expect. Please note that we recommend always using KeyboardEvent.code for defining the keys and only using KeyboardEvent.key for defining modifiers.

WindowsmacOSkeycode
N/ACommand / MetaMetaLeft / MetaRight
AltOption / AltAltLeft / AltRight
ControlControl / ^ControlControlLeft / ControlRight
ShiftShiftShiftShiftLeft / ShiftRight
SpaceSpaceN/ASpace
EnterReturnEnterEnter
EscEscEscapeEscape
1, 2, etc1, 2, etc1, 2, etcDigit1, Digit2, etc
a, b, etca, b, etca, b, etcKeyA, KeyB, etc
---Minus
===Equal
+++Equal*

In addition to the above table, you can use https://keycode.info/ for checking the specific values needed. Note that some keys will have the same code as others because they appear on the same key on the keyboard. Keep in mind how this is affected by international keyboards which may have different layouts.

  1. Use Ctrl+K (Windows/Linux) or Cmd+K (Mac) to open the command menu.
  2. Start typing the command you want to execute. The suggestions in the command menu change to match your text.
  3. Finish entering the name, or use the arrow keys to highlight the command you want from the list of suggestions.
  4. Use Enter to execute the chosen command.
  5. If you chose a command that has nested commands, you can use Backspace to return to the previous menu.
  6. When the command menu is active, you can use one of the following keyboard shortcuts to close it: Esc, Ctrl+K (Windows and Linux) or Cmd+K (Mac).

Integration

For integration guidelines, please see Web Components documentation .

Was this page helpful?

Yes No

We use this feedback to improve our documentation.