Can someone shed some light, please, on what the difference is between a page template (classic Confluence functionality) and a blueprint? Seems to be the same thing.
This is the difference based on my experience
Blueprint | Template |
Title can be pre-populated For e.g. dynamic dates in minutes page | Title is Blank |
UX Wrapper to pre-populate content dynamically in the page and have macros | No UX Wrapper, but can have pre-written/designed content and end user macros |
Needs more development efforts | Needs less development effort. Faster to create. |
Creates Index/Report page if Page Properties are included in the blueprint | Does not create any index |
Hi,
Our company is ISO9001:2015 certified and we started to use Confluence in 2013. We had the Vision to do all our documents within Confluence: contracts, offers, specifications, etc. But our customers still want Word documents and PDFs. So we had to find a way to get all your Word Templates into Confluence. With Confluence templates you can do only one page templates and that was a Show stopper. Blueprints can only be improved by a very small number of employees and that is not collaboration! So in the beginning we used the Plugin Copy Page Tree. It worked, but we were looking for a better way.
So we decided to write our own plugin called Page Tree Creator. The following table describes how we see the difference between the solutions.
If you want to see our Page Tree Creator in action, checkout our live examples under this link:
https://focuspro.eps.ch/display/PEPSMarktExample/Marketplace+Examples
Feature / Function | Page Tree Creator | Copy Page Tree | Blueprints | Template |
---|---|---|---|---|
Page Trees are supported | ![]() | ![]() | ![]() | ![]() |
Search & Replace in Page Title | ![]() | ![]() | ![]() | ![]() |
Search & Replace in Page Content | ![]() | ![]() | ||
Search & Replace in Macro Parameters | ![]() | ![]() | ![]() | ![]() |
Search & Replace in Label Fields | ![]() | ![]() | ![]() | ![]() |
Copy attachments | ![]() | ![]() | ![]() | ![]() |
Default Tags (variables, e.g. current user, template Version,...) | ![]() | ![]() | ![]() | ![]() |
No Programming Skills needed, so everybody can improve templates | ![]() | ![]() | ![]() | ![]() |
Create Index / Report page based on Page Properties | ![]() | ![]() | ![]() | ![]() |
Button with source and destination link to create new Page / Page Tree | ![]() | ![]() | ![]() | ![]() |
Cascade Creation of Multi-Page Trees | ![]() | ![]() | ![]() | ![]() |
No need of Administration Permisson for the design of Page Tree Templates | ![]() | ![]() | ![]() | ![]() |
Page restrications are copied | ![]() | ![]() | ![]() | ![]() |
Standard Confluence links behind Buttons: Renaming and rearrangement of template pages works like everywhere in Confluence | ![]() | ![]() | ![]() | ![]() |
Tag Markers can be configured | ![]() | ![]() | ![]() | ![]() |
Typed Input Fields (user picker is done, date, time, etc. will follow) | ( ![]() | ![]() | ![]() | ![]() |
Copy published Comala Pages | ![]() | ![]() | ![]() | ![]() |
Copy Page Tree without Search & Replace | ![]() | ![]() | ![]() | ![]() |
Create Space and copy Page Tree: Use our plugin Space Tree Creator | ( ![]() | ![]() | ![]() | ![]() |
Internationalization of Page Trees | ![]() | ![]() | ![]() | ![]() |
Internationalization of one Page | ![]() | ![]() | ![]() | ![]() |
Regards,
Stephan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This looks awesome. Thanks for making this. I was about to have to create this, or a version of it. Do you have developer documentation on how to use and extend this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Stephan Sutter I love the concept behind your add-on! I noticed, however, that the Cloud version is quite distinctly nerfed compared to the Server versions. . . so according to the features you list above (which is way more complete/clear than the feature sets explained here, which ones apply to the state of the Cloud version today? What features does it currently have compared to the native Cloud template editor? (If I am going to make a recommendation to my group, I need to have this information.)
Thank you, in advance, sir!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
One difference I have noticed is that with Blueprints, you can specify what you want the title of the page to be and add variables. Ex. if you create a page with the Meeting Notes blueprint, your page is automatically titled " Todaysdate Meeting Notes."
As far as I know, you can't do that with templates. When you create a new page from a template, you have to manually enter the name of the new page:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
templates are somewhat limited, with blueprints you can build a fully customizable wizard for your Jira pages. Look at what the polls plugin does with blueprints
https://marketplace.atlassian.com/plugins/com.simplenia.confluence.plugins.polls
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry to re-open an old thread, but I am still looking for this information, especially for Cloud. What are the differences between the Templates we can make with the Template Editor vs. Blueprints?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
"A blueprint is a page template with added functionality to help you create, manage and organize content in Confluence"; From https://confluence.atlassian.com/doc/page-templates-296093785.html , but that holds for Cloud as well.
I'd say start with Templates you can make with the Template Editor, if you run into any limitation in terms of customization/automation then start looking at blueprints
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
They are basically the same thing. You can read more here (https://confluence.atlassian.com/display/DOC/Working+with+Templates#WorkingwithTemplates-Templatesprovidedbyblueprints).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
TLDR; A blueprint is a template with extra sugar.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It says in the doc that "A blueprint is a page template with added functionality to help you create, manage and organise content in Confluence.". Can you, please, give an example of such functionality? So far I see a blueprint as just a large template that can include several simple page templates... Am I right?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
I invite you to look at the Gaia for JIRA plugin, which basically allow to create new spaces based on a template space. It has got several templates included, and it includes blueprints as well. This allows basically to have a broad set of Confluence pages, and blueprints. So anyone can start a new project based on an predefined environment. Pretty neat.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.