Does Confluence support wiki branching and merging?

[Piotr Piasecki]

I would like to create a documentation for our product. However, as with any software products, things get changed over time. So I would want to maintain two versions of the same documentation - one for "live" version of the product, and one for "dev" version of the product that's being developed and updated.

The idea would be to adjust the dev documentation on the fly as the product gets updated and push the changes from dev to live at the same time the code gets pushed from dev to live environment so the users would always be able to check the live wiki documentation and see the correct, up-to-date documentation, while devs could work on the dev documentation that reflects the upcoming changes.

Basically, it's like a git flow but for the wiki with periodic "dev-to-main" pushes.

Does Confluence support a functionality like that that's not just "lets manually copy and paste the changes", and if so, how can I set this up?

[Matthias Gaiser _K15t_]

Hi @Piotr Piasecki,

as @Fabian A_ Lopez _Community Leader - Argentina_ Florida_ California_ mentioned that sounds like a perfect use case for some of our apps. It's on the heart of our vision that you can communicate your product value to your customers.

Since you've stated that you're on Confluence Cloud, I can see the combination of these two apps useful:

• Scroll Viewport: Scroll Viewport allows you to publish your docs from Cloud into a styleable help center. You can have a look at our docs for Scroll Viewport how it can look like.
  So you can work in Confluence on your "dev" branch and keep publishing it via Scroll Viewport to your live docs.
• Scroll Documents: If you want to version your content, you can also combine Scroll Viewport with Scroll Documents. This allows you to group several pages together as a Document and version it.

If you want to get a demo, visit our webpage or let us know any additional questions via help@k15t.com.

Cheers,
Matthias.

[James Conway]

Hi Piotr,

This is not a native capability of Confluence. Fortunately, the Atlassian Marketplace offers a fantastic range of add-ons to customise Confluence to meet your requirements. One option you may want to consider is Comala Publishing, this enables you to work in a draft (or dev) Confluence space, and then synchronise with your Published (or live) space as required.

If you are on Confluence Server or Data Center you can see the app summary and download a free 30-day trial from https://marketplace.atlassian.com/apps/143/comala-publishing?hosting=datacenter&tab=overview

If you are on Confluence Cloud please do get in contact with us at https://support.comalatech.com as we are currently working on a version of Comala Publishing for Cloud..

Let me know if you have any questions

All the best

James
Senior Product Manager

[Fabian A_ Lopez _Community Leader - Argentina_ Florida_ California_]

Good point, you can also enhance the experience by adding K15t ViewPort and k15t versions.

Read this article from Matt Reiner Rock the docs Introducing Rock the Docs: Your Team's Guide to Documentation in Confluence | K15t

@Matthias Gaiser _K15t_ can help you as well. the combination of Confluence, Comala Document Management, Publishing and K15t ViewPort and versions is a good one

[Matthias Gaiser _K15t_]

@Fabian A_ Lopez _Community Leader - Argentina_ Florida_ California_ , thank you for mentioning me. Since @Piotr Piasecki is looking for Cloud solutions, I've added a new answer to not confuse him - or anyone else reading the thread.