Customize & Extend
App Suite UI is designed to be extended and customized. Custom plugin code is registered using manifests and is loaded dynamically at runtime. Usually this is used to register extension points, in order to inject new functionality or change existing behavior. For the model behind that - extension points, capabilities and how the client is composed at runtime - see the Architecture overview.
The pages below carry worked examples; Portal widget is a complete plugin in one file, and Manifests is how you get it loaded.
In this section
| Page | What it covers |
|---|---|
| Manifests | Declaring your code so the UI loads it, and gating it on a capability |
| Toolbars and menus | Where an entry ends up once registered - action order, what becomes a button and what moves into the overflow menu, and what a context menu is for |
| Portal widget | Adding your own widget to the portal |
| Sign In | Customizing the sign-in experience |
| Internationalization | gettext, plural forms and the rules for interpolating values into translatable text |
Branding that does not need code - colors, logos and the login page - is configuration rather than customization; see Theming and Login page.