-
Notifications
You must be signed in to change notification settings - Fork 79
[dev] GUI Design Guidelines
Infernio edited this page Feb 16, 2024
·
8 revisions
TODO Add some more here
-
Follow the [dev] Translatable Strings page.
-
For capitalization in GUI labels, we currently follow the AP guidelines (Associated Press Stylebook). You can use https://titlecaseconverter.com/ to check, AP is the default there.
-
For ellipses etc. in link texts:
- Use
..
for all submenus - Use
...
only for links that need more information to perform the action (see here as well)- For example, "Move To" on a plugin should be "Move To...", because we need more information (to what point in the LO are we moving the plugin?).
- On the other hand, "List Masters" on a plugin should not be "List Masters...". While it does show a popup, that popup is the whole result of the command already! We don't need any other information from the user to list the plugin's masters.
- By doing this, we follow both Microsoft's and Apple's UI/UX guidelines for ellipses.
- Use
-
Avoid hugely long context menus. Especially without icons (which we currently don't support - TODO look into that) these make it really hard to spot particular links. As a rule of thumb, once you're near 15 or so links, it's time to consider submenus.