You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I'm using Bitbucket, JIRA and Confluence in the Cloud.
At the moment, I'm building up the representation of my customer projects distributed over the three applications.
This mainly consists of migrating the former representation in svn, Trac and Confluence over to the new representation.
My question is now: What to use as a knowledge base around Bitbucket Repos?
Bitbucket offers its own Wiki as versioned Markdown files which is directly connected to the repo, but currently I'm building most of the customer documentation in Confluence.
Ideally, I would be able to use Confluence as a drop-in replacement for the Bitbucket Wiki, creating one space per repo, but this does not seem to be an option.
How do others handle this, or is there a canonical way? Should I live with two distinct Wiki technologies?