Hi there,

I'm a Product Manager @ Kolekti (Part of The Adaptavist Group) and we're currently exploring the content creation and management space. I'm looking at speaking to Confluence content creators who are creating and managing content at scale it seems this could be a good place to reach out. We've got some high level concept ideas related to this discussion and would value your feedback in shaping the next stages of our research. 

If you'd be willing to have an informal chat please also let me know and we can connect 🙏 🙂

Hello everyone,

We are currently shifting the efforts from templates to additional customization options for Confluence Cloud. However, this suggestion is under the team's consideration, meaning that even though our work for implementation is paused, we might come back and consider implementing it in the future.

We will still keep the maintenance and continue to fix bugs that have higher priorities as per our Bug Fixing Policy.

Thank you for your understanding.

Wish you the best,
Giuliano C.
Atlassian Team

Hi all! My name’s Avni and I’m the Product Manager that works on the template feature. Thanks a lot for your feedback. As we’re continuing to improve templates, understanding use cases like these always helps us figure out the most important items to prioritize in our roadmap. 

For this specific request, we don’t currently have short-term plans but are actively investigating what we could do. We’ll keep this ticket updated as we know more.

Thanks again for your feedback!

Cheers,
Avni Barman | Atlassian Product Manager

A vote from me for sure.

I'm new to confluence - and was pretty astounded to see this isn't a feature. Given that you'd likely want to link to sub pages through any documentation you write - it's frustrating that you can't easily establish the entire parent/child tree just in the left hand menu before you ever write one word. 

For now I'm doing this manually but it is a slow going, lateral process. 

Surprised this isn't a feature already! For people who use Confluence to manage projects there is a constant need to create a set of common documents (project plan / notes / etc). Spinning up a new Confluence space for each project is wasteful since we work on a myriad of smaller projects that don't require much documentation. We'd have hundreds of 4-5 page Confluence spaces to scroll through and search across.

This would be a game changer - please prioritize this soon! 

Is there any issue from Atlassian?

Similar to Kathryn we have the need for any Confluence Page which acts as a kind of "workflow" spreading over more than one document / document type to create a parent page (.i.e Project Overview) and the according subpages (such as Documentation, Meetings etc) so that the users of the "workflow" do not need to think how to structure it themselves, giving you a nice streamlined setup of projects, each looking the same way

We are in exactly the same position as Florian. We have a Projects template with 'buttons' at the bottom of the Project template for the user to manually create the other required pages, using the relevant child page template.
The child page templates we use are:

• Timeline
• Reference documents
• Requirements gathering
• Community Forum
• Meetings
  Creating these automatically has been on my 'most wanted' list for 2 years now.

same for us. actually we have templates for projects etc. and the needed child pages have to be created manually (and not everybody does this correctly). Having nested child-pages in blueprints would solve this problem.
what about a "create subpage from template" - macro that inserts a specified subpage from another blueprint (recursively) that can be included in the blueprint and get's removed from the created page when the page is stored?

For the record, this would help us out a lot! We have documentation on projects that all have the same basic structure - would save us a lot of time to be able to build these project pages in seconds instead of an hour!

Multi-page template, template in a template: no problem with our Page Tree Creator Add-on.

Our Add-on Page Tree Creator works a bit different than the Confluence blueprints / templates. The PTC-templates are based on normal confluence pages and therefore creating a PTC-template is as simple as creating a Confluence page. The PTC-tags (variables) can be used in the title, on the page and in macro parameters. Default variables like current date (_Current_Date_) are there.

Try our Live Examples (no registration needed).

Marketplace link: Page Tree Creator.

This would be a valuable feature. I'm creating a project template page where I'd like to include navigation links to preset pages, such as a blank meeting minutes page, project request, project materials. Or even better, a template of a template, such as creating a meeting minutes page that includes a template button to create minutes with and a list of yet to be created minute pages. Auto-generating child pages on behalf of a single template....vote yes. Thanks.

This is a importent feature!
The new page has been create under root of space when I created it by template, it‘s so trouble to my team, because the new page break my pages tree under root.

This would be a great feature to have!

Just thought I'd let you all know, in case it is useful in the interim

I wish the copy page tree will be an interim, but as it looks like it would be THE SOLUTION for a long time. This issue was created 1,5 years ago and at this time no comment from Atlassian, no Assignee, no fix Version, just growing Votes and Watches. I have seen way to many Suggestions like this that lasts kind of "for ever" and which are still not implemented...

Hi,

Not sure if it was here or elsewhere, but someone mentioned the Copy Page Tree add on. We now have this installed and this is working well for us, although a template or blueprint that allows a page structure to be created easily would still be our preference.
I have created the page tree as a template with no data in it, other than what is standardised data, using the page templates we wanted to be used for the different pages. When creating a new page tree, we copy this template tree to the location where the new tree should be created. As part of the process, you can add a prefix to all the pages in the page tree and edit page names as needed too. This has much simplified the process for us, it now only takes a minute or so to create a new page tree.
Just thought I'd let you all know, in case it is useful in the interim

Would be great to have sub-pages as a part of page template. For example for each software product it could be something like

Product
    Specs
    Roadmap
    Research
    etc.

at least one-level already would be a great help.

Our spaces are organised by budget; each space represents a budget type. We then create a page tree for each project belonging to that budget type. It would be great if we could have a standard page structure that is driven by a blueprint for each project in the space. We currently have a page template for the creation of the project, which has buttons for the creation of each of the sections. The buttons are then removed by the user once all sections have been created. This is not a very elegant solution, so having a Blueprint, which we can customise with a page structure (similar to the Space Blueprint) would be ideal.

Another Use Case ==>
I do a lot of Patent Application work (Drafting, Reviewing, and Submissions) and I would love to be able to create the page hierarchy quickly:

Patent Title --> includes goals, section status, etc

I use Scroll Office & Scroll PDF to export the documents so I can make sure my formatting and numbering sequence is uniform across all the patents, and of course that means each one of these pages basically require a template each right now... One-Click would be so much nicer!

Another Use Case:

Some Sales guys of ours would like to be able to create a pages tree from a template, to store some info about customers; for each customer, you'd get a main page, and some standard sub-pages focused on sub topics

They'd be interested in getting something very simple; for instance, in a page, they'd have a button on which they could click, being asked then to enter a customer name, and then, hurrah, they'd get their pages hierarchy set, with suitable pages names, based on a global template for the pages hierarchy & content.

Really, Really important.

Already talked about it with Samuel by Reference: CSP-138896

Hi,
Our add-on Yoikee Creator https://marketplace.atlassian.com/plugins/com.keinoby.confluence.plugins.yoikee-creator allows you to create space templates (i.e., space blueprints) by means of mind maps. You draw the structure of your space template in a mind map, where the nodes become pages in the space. Thus, the hierarchy of nodes-sub nodes become the structure of pages-sub pages in the space. You create once a mind map for your documenting your software, and you can create as many spaces as you need with the same structure of pages (consistent spaces).

We are about to release the 2.0 version, where you can choose page blueprints in the nodes (JIRA reports, blog post, file list, etc), mind maps can be embedded on pages, new rendering engine, and many more new features.

Give it a try and send us feedback, regards,

Gorka

UPDATE: The version 1.2 of Yoikee Creator has been released. This version has a new macro to embed mind maps within pages and allows you to select page blueprints directly on the mind map nodes.

Another use case: Documenting software

Conceptional Design using existing features: http://chickenbit.com/blog/2014/11/conceptual-design-of-implementing-a-software-architecture-document-with-atlassian-confluence/

Objective: Technical Writer wants to document a new feature.
Pre-Requisite: The "Pattern" for documenting the software is composed of a parent page for the Feature overview and child pages for Use Cases, Architectural References, Known Issues, and Revision History and implemented as a template.

Usage 1a:
1) Tech Writer create new set of pages with template
2) Tech Writer edits parent page and saves
3) Tech Writer edits child page(s) and saves

Usage 1b:
1) Tech Writer create new set of pages with template
2) Tech Writer fills in page hierarchy template information and saves
3) Page hierarchy template saves information to parent and child pages
2) Tech Writer edits parent page and saves
3) Tech Writer edits child page(s) and saves

One example which I mentioned in the description is Release notes for our products. They each have a few pages that are standard across all products. A blueprint with child pages would be great for these because it saves the authors the time to have to create those individual pages from regular templates. Another example would be when authors write processes for certain things. They have a few standard pages which are the same across products so even though some of the content changes, the layout of these pages are the same across products. We have a couple of other things that share the same problem as the previous things and honestly, if this were to work I can guarantee we can find a lot more uses.

Thanks for taking the time to raise this Alex.

It would be great to hear some examples of what you'd want to use these for?