This document explains the changes made to menus and their notation between Theme Builder 1.x and 2.x...
In Theme Builder 1, menus were defined as simple unordered lists like the one shown below:
The notation above would produce a menu something like the following if placed on a normal page within your space:
And if placed in the "Custom pre-menu" or "Custom post-menu" sections of the Theme Configuration screen it would result in a menu bar at the top of the screen similar to this:
The menubar macro turns an unordered (bullet) list of links in to a functional menu. The wikimenu macro processes a normal Confluence wiki notation unordered list to ensure it's in the correct format for processing by the menubar macro.
The neat thing about this is that you can now put the menu anywhere - for example, you put it in a sidebar, the footer or even on a wiki page (as shown above).
While the wiki notation is often really easy to work with, there are some downsides - most notably when a user does not have access to the item you are linking to which results in a "dead" (non-clickable) menu item. As such, we highly recommend using the new Menu Macros when defining menus in Theme Builder 2:
We've indented the items above to make it easier to see the hierarchical structure of the menu - this has no effect on the actual menu, so it's optional, but we highly recommend it as it makes your menu notation easier to read.
The menuitem macro replaces the *'s in the wiki notation and to indent the list (create a submenu) the menu macro is used (and for subsequent indentation levels the submenu macro and sub-submenu macro are used).
The menuitem macro has a very useful feature - it will hide any dead links in your menus automatically.
The menuseparator macro replaces the ---- used to create a divider in the menu. Should two menu separators be found next to each other (eg. because the menuitem macro has hidden inactive links between them) the surplus separator(s) will automatically be removed.
Likewise, if an entire menu or sub-menu is found to be empty, it will be removed.
The menulink macro provides an easy way to link to all common features within Confluence. For example, instead of using wiki notation to define the link to the home page like this:
You can use the menulink macro as follows:
The key benefit in this scenario is that it doesn't matter what the home page is called, or even if it's renamed at a later date, the menulink macro will still find it and link to it.
Another key benefit of the menulink macro is that it strictly adheres to Confluence permissions and user privileges and therefore provides a very reliable way of linking to Confluence features.
For more information, see menulink macro.
Furthermore, you can now fully customise the View and Edit menus to completely customise them or separate items out in to different menus, etc. For more information see Theme Configuration 2.x.