The adminCentral menu in Magnolia is configured in the config repository, within the adminCentral module. Menu items are defined at: modules/adminInterface/config/menu. If you navigate there now you will see the menu buttons currently defined for your configuration.

Changing an existing menu item

To define another menu it is easiest to copy an existing menu item and modify it. Out of the box, there are two menu items that you probably don't want to keep around as they are purely informational: "Documents" and "Processes". These are represented in the config tree as dms and bpn respectively. To remove one of them, simply right click the node and select Delete. Keep the other one around as we are going to modify it to create our new menu option.

Creating a menu item from scratch

If you have the dms or bpn nodes to work with, you'll want to create a new one from scatch. Right-click on the menu node (modules/adminInterface/Config/menu/) and select New content node. Give it a name and then create three nodes below it (right-click on new content node, select New node data).

• icon - This node gives a path from the root of the webapp to an image file. Magnolia stores its menu images under /admindocroot/icons/24/.
• label - You can either specify a resource bundle key here (Magnolia's preferred mechanism) or simply insert the text that you want displayed for the menu
• onclick - This is where you enter the command that will be executed when the user clicks the menu item. This could be an instruction to expand a respository tree (as is the case with Website, Users, Roles, and Config) or a command to navigate to another URI (as is the case with About, Documents, and Processes).

Note that menu items will be visible to users depending on their permissions. The workflow-base, for example, defines an acl to ensure users with this role can see the Inbox menu item.