Page management and versioning

[Chris X]

Hi

I have another question regarding versioning / page management.

I have a situation where I have a page; let's call it 'Master' and I need to have more than 1 person making updates for that page (not necessarily to that page).

The solution I have thought of is to duplicate Master twice, and treat Master as my 'Live' page and the duplicates as versions that can be worked on.

Let's call them Dupe1 and Dupe2.

Then what i need is for Dupe1 and Dupe2 to be merged into Master at a future time e.g. Dupe1 might merge in to Master in March and Dupe2 merge to Master in June.

So, I need to find a way to merge Dupe1 into Master - I know Confluence is great at comparing versions for the same page.

Can i compare Dupe1 and Master similarly and then maybe paste the changes from Dupe1 in to Master ?

When it comes to merge Dupe2 to Master - i then have the challenge that Dupe2 will have been copied from Master, NOT Dupe1 - so I have to be cognisant of any changes merged from Dupe1 to Master.

To be clear, I can't have people working on Master at the same time making updates toMaster as it needs to be correct for people to consume.  

I'm hoping there might be some in-built mechanisms im not aware of that will help with either or both of these scenarios!

Thanks!

[Kristian Klima]

Hi @Chris X 

I recommend looking at Space Sync for Confluence by Ricksoft.

In your setup - Master -> 2 Dupes, you have three options

• One way sync - Edit in Master, push to Dupes when the content is ready. 
  Dupes' history would consist of 'good' synced version from the Master.
• Two way sync - establish two bi-directional syncs. In this scenario, you can sync content like this:
  • Master <-> Dupe 1
  • Master <-> Dupe 2
• Multiway sync - immediately sync any change in any space to the other two spaces.
  This, effectively, reduces Master to Duper 3 :)

No need to duplicate, copy, or anything like that, just sync the the content.

The app is extremely flexible and customizable - including permissions, so you can determine who can sync pages individually per space.

Crucial feature of the app is that it also converts links - Master Page 1 link to Master Page 2 will become Dupe Page 1 link to Dupe Page 1, etc. (Just make sure to use inline links).

Disclaimer: I'm not affiliated with Rickosft, I just use their apps.

[Chris X]

Thanks - that looks ideal !!

So long as my company allows me to use the add on.!

I’ll investigate Monday.

[marc -Collabello--Phase Locked-]

Maybe you can approach the problem in a different way:

• have 2 spaces, a master space and a dupe space
• make a copy of the master document into the dupe space
• edit the document in the dupe space
• make sure the dupe space is only accessible to document editors and not all viewers
• when ready, move the document from the dupe space into the master space

In order to allow different people to edit different parts of a document, consider splitting the document into multiple parts and using the include macro ( https://support.atlassian.com/confluence-cloud/docs/insert-the-include-page-macro/ ).

[Chris X]

Good tips - thanks.

Yes - Dupe1 can replace Master once Dupe1 is complete.

However any version history would then be lost from the ‘Master’ as Dupe1 would then be the “master”.

Then still have the Dupe2 issue.

Both people might need to make updates to the SAME section. Good to hear about this feature though so thanks.

Your advice is appreciated.