You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,6 +42,7 @@ This focus helps guide our project decisions as a community and what we choose t
42
42
-[Naming conventions](#naming-conventions)
43
43
-[Vue components](#vue-components)
44
44
-[Internal linking](#internal-linking)
45
+
-[Command palette](#command-palette)
45
46
-[Cursor and navigation](#cursor-and-navigation)
46
47
-[RTL Support](#rtl-support)
47
48
-[Localization (i18n)](#localization-i18n)
@@ -400,6 +401,14 @@ For package links, use the auto-imported `packageRoute()` utility from `app/util
400
401
> [!IMPORTANT]
401
402
> Never construct package URLs as strings. The route structure uses separate `org` and `name` params, and `packageRoute()` handles the splitting correctly.
402
403
404
+
### Command palette
405
+
406
+
The command palette is a first-class navigation surface. When you add a new user-facing capability to the app, you should also register a corresponding command palette entry for it whenever that action or destination makes sense outside its immediate UI.
407
+
408
+
- Add global entries in the command palette composables.
409
+
- Add page- or component-scoped entries from the page/component that owns the capability.
410
+
- Prefer palette entries for actions users may reasonably want to trigger from the keyboard or jump to directly.
0 commit comments