-
Suggestion
-
Resolution: Unresolved
-
None
-
8
-
17
-
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
It would be great if page blueprints had the ability to also create child pages. Similar to how space blueprints work, except this would create a parent page and child pages for already existing spaces. One such application for this would be for release notes. Each of our release notes have one parent pages and two child pages at a minimum. It would be great to be able to create a custom blueprint that goes ahead and creates those 3 pages. All the pages would be based on templates in the plugin, as it currently works, and when you create it, confluence would take you into edit mode for the parent page. So it would work the way it does now except it creates child pages and you can give them a title and pass variables to them like you can now with page blueprints.
- is duplicated by
-
- Closed
- relates to
-
- Under Consideration
- mentioned in
-
![[Confluence] Page](/images/icons/generic_link_16.png "[Confluence] Page")
Page
No Confluence page found with the given URL.
-
Page Loading...
-
Page Failed to load
-
[CONFSERVER-34208] Adding child pages to page blueprints
Wouldn't a work-around be to create a template for a page that has multiple template buttons on it? For instance, say I'm a large-scale organization that wants project to govern their own pages, but want to provide an "easy button" for each project to get set up. I could create several page templates, and one "master" page template. I add a button from wherever in the tree I want users to create their own page structure from the "master" template. On the "master" template, there are template buttons for other page templates. Yes, there is a smidge of manual work, but it's not labor intensive, and automating that wouldn't save more than a minute or two during setup. On top of that, perhaps not every project requires the same number of standard child pages, so you can modularize your page tree based on needs, and not just create pages that now someone has to go clean up!
Just my two cents.
Confluence is a wiki .. nothing more ... nothing less. This is not a tool which lends itself to the storage of formalised structured documentation, if it was then this functionality would be baked in as standard. Wiki's are useful just not for what we want to use it for, and this is why Word / PDF's will continue to exist, if only we could have the search/storage power of a wiki with the documentation features of word.
Very interested in the feature. It's a PIA to create the child pages for each project.
Structure aids discoverability. Creating parents with their default children from a template encourages consistency. Consistency reduces friction.
Less friction and more confidence (in where to find things) leads to greater use of the resource and better value from the platform.