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.

Agreeing with the others here, it's quite tedious and time-consuming for my teammates that they have to create all the child pages manually after using my template to create a parent page. This gets one vote from me, I'm somewhat disappointed that this hasn't received more priority from Atlassian.

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.