How do I create content in one space but distribute it across difference spaces with labels?

[Paul-Julian]

Hi All

We are creating all our pages in one parent ('Global') space, but we want to be able to distribute it across multiple child spaces ('Microsite') so we only have one library to maintain and everyone can have their own UI, navigation and search results without creating content in individual spaces.

We are using labels to make it appear in all different spaces, which is great, but when the user clicks the title in the navigation or search results in their microsite, it takes them back to the the Global space (where the pages is originally created) and not keep them in their own Microsite space. Its not a great user experience.

How can we distribute pages across multiple spaces, but allow the user to keep their navigation/UI in the space they are in and not transported back to where the pages originates from? Am I missing something or is there a plug-in which keeps them in their own space?

[Paul-Julian]

Hi David, thanks for the response. Yes we tried that, we are looking for a solution where we can share pages across multiple spaces but all sources from the one location.

Of course this is possible with labels but when the user opens that shared spaces, the users is then transported from where the space where the page to originally sourced from in a different space. They loose the navigation (and UI) their space which they clicked the link from.

How do we work around this then?

[David at David Simpson Apps]

You can use the Include Page macro to distribute the page content from one space into another page in other spaces. This would be a manual approach, but still mean that you can edit is a single space.

The only other way you could do this entirely automated is for the links (based on labels) in the microsite spaces to open a modal/dialog view of the page content from the parent space. this would mean that on close of the modal/dialog, the context would still be the original microsite. This could likely be done with a little Javascript on Confluence Server. On Confluence Cloud, you'll be out of luck.