Confluence Docs 3.0 : Ensuring Standard Page Decoration in your Plugin UI This page last changed on Sep 07, 2009 by ggaskell. On this page: Purpose of the Standard Page Decorators Specifying a Decorator Limitations on Standard Page Decoration in Confluence ## Purpose of the Standard Page Decorators Atlassian applications which support Plugin Framework 2.1 and later will also support standard page decorators. This allows 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:
    <html>
    <head>
        <meta name="decorator" content="atl.general"/>
    </head>
The following decorators are available: `atl.admin` for application administration pages. `atl.general` for the header and footer of general pages outside the administration UI. ## 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. ##### RELATED TOPICS Writing Confluence Plugins Enabling TinyMCE Plugins Converting a Plugin to Plugin Framework 2 Creating your Plugin Descriptor Confluence Plugin Module Types Accessing Confluence Components From Plugin Modules Including Javascript and CSS resources Adding Plugin and Module Resources Adding a Configuration UI for your Plugin Ensuring Standard Page Decoration in your Plugin UI Making your Plugin Modules State Aware Confluence Plugin Tutorials Form Token Handling Information sourced from Plugin Framework documentation

Document generated by Confluence on Nov 05, 2009 23:34