A software developer's day using confluence.
Overall Satisfaction with Atlassian Confluence
We use Confluence to document our engineering practices. From documenting releases and server updates to storing coding guidelines for developers. We've basically replaced MS Office documents and Sharepoint with Confluence. Confluences make for a more user-friendly way to store documentation that is searchable, flexible and far easier to maintain.
Pros
- It is really easy to make document templates with Atlassian Confluence.
- If you don't like how you've organized your documents in Atlassian Confluence, you can easily rearrange your documents into a structure that better fits your business.
- Building a linked document structure is really easy within Atlassian Confluence.
- Atlassian Confluence is extensible with macros and extensions.
- There are integrations with other platforms for Atlassian Confluence.
Cons
- I was perusing the developer documentation and I found it to be poorly organized. It just felt unapproachable.
- We get too many status updates from Atlassian cloud. I think they are trying to be transparent, but it feels more like oversharing.
- We spend less time looking for documentation.
- Our documentation for audits is much more complete and less cumbersome.
- We are able to move more information into the cloud and reduce local server maintenance load.
We were using MS SharePoint which was integrated with TFS for managing our developer workflow and it was quite clunky. We had to be signed into the VPN to access any of it and it relied upon Internet Explorer for access. It felt slow and sometimes you could use other browsers and sometimes you couldn't. We have also moved to VSTS, Confluence, and TestRail; and things are much more usable and better documented.
Comments
Please log in to join the conversation