Extending Confluence - Atlassian Confluence 5 Essentials - page 295

I'll explain this example a bit more in detail:
<web-item key="config-link" name="Plugin Configuration"
section="system.admin/plugin-admin-section" weight="10">
The web-item attribute knows a section argument instead of a location, as Web
Items must be placed in sections. In our example, I'm placing this Web Item in the
section we have defined earlier.
<linklinkId="config-link">/plugins/config/alpha.action</link>
The link element will determine where the user will go after clicking on the
menu item. The linkId argument is optional and will provide an HTML ID when
rendered. The link can either be relative to the Confluence server or absolute,
pointing to any website you wish.
<icon height="16" width="16">
<link>/images/icons/config.gif</link>
</icon>
Web Items can contain icons that will be placed before the their label elements.
The icon can have a width and a height attribute. The location of the image is
defined by the link element.
Just like Web Sections can, Web Items can contain conditions to determine when a
link is shown and to who.
Online resources
This chapter gives you only a small insight into the possibilities on extending
Confluence and writing your own plugins. There are many online resources
available to move you forward from this point.
All developer documentation is bundled and located at
https://developer.atlassian.com .
• The Confluence module types : For more details about the available modules
and which arguments and elements they accept, visit https://developer.
atlassian.com/display/CONFDEV/Confluence+Plugin+Module+Types .
• Confluence Plugin Tutorials : Various Confluence tutorials from beginner to
advanced developer are available at https://developer.atlassian.com/
display/CONFDEV/Confluence+Tutorials .