So we've just started a refactoring of our documentation in Confluence. Moving all the relevant documentation to a new space and building that space with templates and labels.
For example, We use Content by label to generate lists on what we expect different people to work on, this is built with labels and AND statement possible in Content by Label
What we've found out is that Confluence macros are a mess. There are multiple label macros built in for Confluence, and they all work in different ways.
When we're looking on how to solve this, most of the threads found here in the community links to plugins in the Atlassian Marketplace. If not, there are bugs that are 7 years old that never seem to be implemented.
As a government entity, we can't pay for a documentation system only to be told to pay for for 3-5 3rd-party plugins (that might break things when upgrading) to solve things that should have been in the product from the beginning.
Also I guess support would be a pain since I now have 4-6 different entities to raise support questions to depending on what breaks.
I'm beginning to doubt Confluences usefulness for documentation and longing back to DokuWiki (which BTW also required multiple plugins).
So, my question is this.
Confluence basic functionality without plugins, is it usable?
Hi, Confluence collaborators! As part of #Confluence-Collaboratory month, we’ve created a very special Mythsbusters segment, where we're dive into an interesting myth and uncover the truth behind i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events