Confluence Blueprints: Creating Multiple Blueprints within Single Plugin

[Gavin Fowler]

I've been following the excellent Atlassian guides "create a blueprint plugin" (simple, intermediate, advanced) and I now have a plugin that contains one fully functional blueprint.:)

My question is: are there there any examples/resources out there (or community guidance) that outlines how I can manipulate my plugin so it houses more than one blueprint (as is done with Atlassian's "Blueprints for Business Teams Pack"). Like i mentioned i have the basics for single blueprint, so just need to understand how to organise the contents / references to now support multiple blueprints within a single plugin.

All feedback/suggestions welcomed (apologies if this is a noob question, this is my first time at coding for Atlassian products / Java).

Many thanks!

Gavin.

[Sherif Mansour · Accepted solution]

Hi Gavin,

This is done by simply appending more tags to your atlassian-plugin.xml file. As an example with our Business Blueprints, we've got common descriptors shared up the top of our file, then for each Blueprint we just keep adding the standard descriptors. Hope this helps. Here is a sample:

<atlassian-plugin key="${project.groupId}.${project.artifactId}" name="${project.name}" plugins-version="2">
    <plugin-info>
        <description>${project.description}</description>
        <version>${project.version}</version>
        <vendor name="${project.organization.name}" url="${project.organization.url}" />
    </plugin-info>

    <!-- Common descriptors -->
    <component-import key="localeManager" interface="com.atlassian.confluence.languages.LocaleManager"/>
    <component-import key="i18nBeanFactory" interface="com.atlassian.confluence.util.i18n.I18NBeanFactory"/>
    <component-import key="sharePageService" interface="com.atlassian.confluence.plugins.sharepage.api.SharePageService"/>
    <component-import key="contentBlueprintManager" interface="com.atlassian.confluence.plugins.createcontent.ContentBlueprintManager"/>
    <component key="contextProviderHelper" id="contextProviderHelper" class="com.atlassian.confluence.plugins.BusinessBlueprintsContextProviderHelper" />

    <!-- Common index page -->
    <web-resource key="common-template-resources" name="Common Templates Resources">
        <transformation extension="js">
            <transformer key="jsI18n"/>
        </transformation>
        <transformation extension="soy">
            <transformer key="soyTransformer">
                <functions>com.atlassian.confluence.plugins.soy:soy-core-functions</functions>
            </transformer>
        </transformation>
	    <resource type="download" name="common-style.css" location="com/atlassian/confluence/plugins/blueprint/common/css/common-style.css" />
        <resource type="download" name="common-templates.js" location="com/atlassian/confluence/plugins/blueprint/common/soy/common-templates.soy" />
        <context>atl.general</context>
        <context>atl.admin</context>
    </web-resource>

...

    <!-- File List descriptors -->
    <web-item key="file-list-item" i18n-name-key="file.list.blueprint.name" section="system.create.dialog/content">
        <description key="file.list.blueprint.description"/>
        <styleClass>file-list-blueprint-icon large</styleClass>
        <param name="blueprintKey" value="file-list-blueprint"/>
    </web-item>

    <blueprint ....>
    </blueprint>

    <content-template ....>
    </content-template>

    <resource name="file-list-i18n" type="i18n" location="com/atlassian/confluence/plugins/filelist/file-list-i18n"/>

    <web-resource ...>
    </web-resource>

....

    <!-- Meeting Note descriptors -->
    <resource name="meeting-notes-i18n" type="i18n" location="com/atlassian/confluence/plugins/meetingnotes/meeting-notes-i18n"/>

    <web-item key="meeting-notes-item" i18n-name-key="meeting.notes.blueprint.name" section="system.create.dialog/content">
        <description key="meeting.notes.blueprint.description"/>
        <styleClass>meeting-notes-blueprint-icon large</styleClass>
        <param name="blueprintKey" value="meeting-notes-blueprint"/>
    </web-item>

    <blueprint ...>
    </blueprint>

    <content-template ....>
    </content-template>

    <web-resource ...>
    </web-resource>
....

</atlassian-plugin>

[Gavin Fowler]

this example is most appreciated Sherif!

[Stephan Sutter]

Hi,

With our approach you can build blueprints based on normal confluence pages. No programming skills are needed and therefor all your users can improve the blueprints and fully collaborate.

Marketplace Link: Page Tree Creator

Regards,
Stephan