Thank you for raising this issue. While we can see how this feature would be useful, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Thanks again for your idea.

>Being able to edit the included content just for particular pages and not others I'm a little confused by. Are you wanting to create a new 'variant' include page, and essentially swap the page that is being included for a new one? Or would it be copying the content of the include onto the current page so that it is edited just like normal page text? I'm not sure I understand this part enough to really offer any useful comments.

Basically, I need to "prebuild" documents based on reusable content that I've created in my Inclusions Library. Once I've built the skeleton document, I need to go back through it and modify the content for the particular project I'm working on. When I modify that content, I need to only modify it within the current document. If I modify the original and it propagates to other documents, the other documents will become inaccurate. When I include content, it needs to essentially paste the content into the page I'm working on, instead of just linking to the content in the Inclusions Library.

This is my minimum requirement for something like this. It would be even better if there was a "Page Builder" wizard that would allow me to drag/drop pages from the Inclusion Library into a hierarchical tree, and then build my page using the content from the inclusions library and setting the correct Heading levels based on where I put it in the tree. But right now, that's wishful thinking on my part. I just really need to be able to edit included content without modifying the source content.

Hi rrobins,

The idea is more about being able to edit the content from within the page (perhaps modularized) and not have the changes propagate to all pages that use the included template. It shouldn't just be easier to navigate to the source of the content, although that should be something you can easily do, its about being able to modify the content to be specific to the inherited page.

I'd like to keep the source for future use, you should be able to edit it and have a notification stating which pages will be affected by the changes but you should also be able to edit the content on a single page and not have it affect the template.

Hi akassab
My two cents - I like part of this idea. A way to view the content of the include macro in the Editor (perhaps shaded like instructional text), and a simplified navigation path to edit the included page (e.g. click the include macro placeholder and select 'Edit this included page" with a little warning of which pages it is used on) would be really useful, and make the include and include excerpt macros more elegant.

Being able to edit the included content just for particular pages and not others I'm a little confused by. Are you wanting to create a new 'variant' include page, and essentially swap the page that is being included for a new one? Or would it be copying the content of the include onto the current page so that it is edited just like normal page text? I'm not sure I understand this part enough to really offer any useful comments.

Thanks Alexandra for giving us a heads up about this. My two cents, this would be a nice-to-have feature, since Confluence tells us what the source page of an inclusion is (in the editor). This improvement would save us having to navigate to that source page.

Dropping the Blueprints label as this seems less related to Blueprints and more to do with the excerpt include macro or templates. I guess the desired feature is essentially what the excerpt include macro already provides, except with a "copy on modification" feature?

Hi Sherif, Yes, I'd like to create a section of a page as a template to be able to re-use in other pages. The difference between this feature and that of the include page macro is that in order to edit the content in the include page macro you have to change the source of the content on another page (the original page, not the inherited page). In addition, if you change the content in the original page you change the content on all the inherited pages.

The feature requested here would allow someone to:
1. Create a template-like structure for content which they can reuse in other pages.
2. Modify the template and have the changes instantly made on any page that uses the template (all at once)
3. Modify specific pieces of content within the template on the pages that use the template and have only those changes on the inherited page.

Point three is where the include page macro is limited.

It sounds like you want the ability to create a section of a page as a template, and then re-use that in other pages.

Could you tell me what's wrong with using the include page macro to do this? Just tying to get a better understanding of the problem.

Yes, this is exactly what I need. Preferably, I'd like a way to organize that content also. I have hundreds of pages of reusable content, and having it in a "flat" structure would be a nightmare. Ideally, this Content Object would be able to pull content from my _InclusionsLibrary page tree.

This was an answers post requesting the feature.