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
Menu plugins often do background work and the user doesn't really need to know about or see them in the hamburger menu.
The current best example of this is "Wizarding". Users think of New Zealand and Lord of the Rings and Gandalf and magic staffs when they think of wizards. So our development terminology is unnecessarily "leaking" into the user experience.
Would an option be to add to our API a flag to hide a menu plugin (presumably it would do nothing for editor plugins):
type Plugin = {
name: string;
translations?: Record<string, string>;
src: string;
icon: string; // Material icon name or image URL
requireDoc?: boolean; // disable plugin if no doc is opened
+ hidden: boolean
}
For discussion.
The text was updated successfully, but these errors were encountered:
Menu plugins often do background work and the user doesn't really need to know about or see them in the hamburger menu.
The current best example of this is "Wizarding". Users think of New Zealand and Lord of the Rings and Gandalf and magic staffs when they think of wizards. So our development terminology is unnecessarily "leaking" into the user experience.
Would an option be to add to our API a flag to hide a menu plugin (presumably it would do nothing for editor plugins):
type Plugin = { name: string; translations?: Record<string, string>; src: string; icon: string; // Material icon name or image URL requireDoc?: boolean; // disable plugin if no doc is opened + hidden: boolean }
For discussion.
The text was updated successfully, but these errors were encountered: