Problem is, Confluence doesn’t directly support the notion of merging or synchronizing spaces or changing the space URL.

port the preview content to the live site once the new major release is in production.Īs much as I adore continuous delivery, our use case begs for a conventional code/test/live pipeline, where we can start with a Dev version of the space, roll that over to a Preview version, and then put the Preview version into Production.roll out a preview help site as part of our major release rollout, and.synchronize production help content with production code changes,.To manage our product help pipeline, we need to (The Release is dead, long live the Release!) Like Salesforce, we go through a preview/production rollout every four months: We preview our new release in customer staging environments for a time, and then roll out the new release to all of the production environments. If you (google/bing/yahoo) around, you’ll find a lot of tips and tricks for using plugins, permissions, smoke, mirrors, and elbow grease to version Confluence, but our use case seems more straight-forward. The major stumbling block being: How do you version a Confluence space? I’m not saying Confluence is all unicorns and rainbows, but, for us, it’s a step up from Google Docs, and it’s head and shoulders above DITA editors.Īs we migrated more-and-more internal content to Confluence, using Confluence for our Nimble AMS help topics became a natural progression.

Confluence versions