Last updated Apr 2, 2024

Using Standard Page Decorators

Purpose of the Standard Page Decorators

Atlassian applications support standard page decorators, allowing your plugin to generate new web pages with consistent decoration by the host application across the Atlassian products.

Specifying a Decorator

Specify the decorator with an HTML meta tag in your head element:

    <meta name="decorator" content="atl.general"/>

The following decorators are available.




For application administration pages.

Version of Atlassian Plugin Framework: 2.1 and later


For the header and footer of general pages outside the administration UI.

Version of Atlassian Plugin Framework: 2.1 and later


For content that you want placed in a new browser popup window.

Version of Atlassian Plugin Framework: 2.3 and later


For content on a page in the user profile.
This decorator will generally be accompanied by a web item link or tab. The tab, if applicable, should be specified by the tab meta tag. For example:

In the above example, the value of the content attribute is the ID of the tab. Since plugins can be shared among applications, we recommend that cross-application plugins define their own tab to ensure the same ID will be used everywhere.

<meta name="decorator"
<meta name="tab"

Note: The profile decorator is still experimental. In some applications it may function in the same way as atl.general. Tabs are not yet supported by all Atlassian applications. If not supported, the tab will simply be ignored.

Version of Atlassian Plugin Framework: 2.3 and later

Limitations on Standard Page Decoration in Confluence

In this version of Confluence, the standard page decorators are only available on the following URL patterns:

  • *.action
  • *.vm
  • /display/*
  • /label/*

Other URLs do not pass through the Sitemesh decoration filter, so the HTML they return will not be decorated.

Writing Confluence Plugins

Rate this page: