Confluence vs GitLab

It has a comment option on the page, where you can tag other teammates tagging them. it sends the mail notification. Comment at the page end is pretty good for referring to other stakeholders and future references of the topic on the page. Creating the highlights of the discussions, and meeting held points with highlighted tagging. Easy shortcuts such as to add a date just type "//". The interface is cool and has easy shortcuts for quick page making.

Gitlab is a good platform for collaboration with the team, version control, and optimized way to handle the modifications in the project. GitLab is less appropriate in some cases, though it has a lot of options for integration, new users find it difficult to integrate; there is also room for improvement.

• QUICK How-to Guides that can be generated and share instantly
• One can subscribe to the pages and spaces and receive updates in the feed on their home page
• Automatic Email notifications of new updates in the Confluence area
• The platform integrates easily with other Atlassian platforms including third-party apps thus improving its reliability

• The way they have managed to provide the version management aspect using git with project setup and users is mesmerising cause there's no product out there that gives this freely.
• Continuous updates and hearing what users need is what the product engineers at GitLab are doing best. They come back to you with exactly what you need every while.
• Quality features, Latest tech integrations have made the end-to-end solution very flexible and agile.
• CI/CD tools implementation with pipelines and deployment strategies is just making the job for Infra teams smoother.

• Navigation. Similar to other Atlassian products, users have complained that aspects of Confluence are difficult to learn right away[.]
• An issue that users can face when using Confluence is attempting to edit a document while someone else is editing. Although users can access the document and save it, they are unable to see the changes happening in [real-time] that other users are implementing until they refresh their page. Some users have also noted that this can result in loss of edits.
• Another drawback of using Confluence is its specific organizational structure. All information is stored within one page or project, although the page is able to be broken up into sections, some users do not prefer this style. Users can use the ‘page tree’ on each page to organize the different elements of each project.

• Sometimes, it is really challenging to manage conflicts when a lot of merge requests are coming for multiple separate branches to the main branch.
• One area of improvement for the software, is sometimes, the interface can work slower
• A few times, we have faced difficulties testing CI builds locally.

I am confident that Atlassian can come with additional and innovative macros and functions to add value to Confluence. In 6 months, Atlassian transformed a good collaborative tools into a more comprehensive system that can help manage projects and processes, as well as "talk" with other Atlassian products like Jira. We are in fact learning more about Jira to evaluate a possible fit to complement our tool box.

Gitlab is the best in its segment. They have a free version, they have open-source software, they provide a good service with their SaaS product, they are a fully-remote company since the beginning (which means they are fully distributed and have forward-thinking IMO). I would certainly recommend them to everyone.

Confluence can - and in my personal opinion, it will - be a bit hard to use in the first moment. Atlassian is a great company and is eager to help you with any question you have, though. The interface seems to be a bit clumsy at first but the customization options are enough to make it easier and simpler. In general, Confluence is easy to use when you understand what each section does, but this can take a while.

The web console management is superior and I would have given Gitlab a 10, but sometimes it is hard to find documentation about a configuration setting in the gitlab.rb configuration file. As we move everything to code that means moving our CVS tools to code as well - and Gitlab to code. The usability of Gitlab from the end user's perspective is superior and the usability from the operations team is very good and getting better but there could be a little improvement in the gitlab.rb config file layout and documentation.

I do not recall having outages or applications error so far, very reliable and available.

Pages load very quickly, which makes it useful for quickly obtaining information. The search functionality is also very quick and is able to parse through all of the documents to provide the most relevant results for the query. Other information based software gets bogged down, but so far Atlassian Confluence maintains its performance.

This rating is specifically for Atlassian's self-help documentation on their website. Often times, it is not robust enough to cover a complex usage of one of their features. Frequently, you can find an answer on the web, but not from Atlassian. Instead, it is usually at a power user group elsewhere on the net.

At this point, I do not have much experience with Gitlab support as I have never had to engage them. They have documentation that is helpful, not quite as extensive as other documentation, but helpful nonetheless. They also seem to be relatively responsive on social media platforms (twitter) and really thrived when GitHub was acquired by Microsoft

Overall, I am very satisfied with the initial implementation (and the subsequent upgrades and implementations made over the years).

This product has never rose to the level of being an major issue at an executive level. It has quietly and valiantly done it's job for our company!

I haven't use any other software that I could compare to AtlassianConfluence. The closest one would be Sharepoint, but it's a different beast. Sharepoint has more feature, but it's a lot harder to use and understand. Furthermore like many Microsoft solutions the UI is terrible and very difficult to understand sometimes. Atlassian Confluence is just plain easy to use.

We have a small custom code development group. We only needed a basic entry-level code management repository. Gitlab meets our needs and is very price advantageous compared to others on the market. We also needed a system that is easy to administer and easy to grant access to our limited-size user base. Gitlab does what we need and gives the necessary flexibility for application support, user administration, and code/version control needs to be required.

This tool is very adaptable. So much so we use it for three completely separate projects, in three very different ways.

• We've gone from folders and folders of Word documents and PDFs into a single system with a search feature to bring all of our data together and trackable
• While onboarding took a bit longer for the company (to switch from a Word document centric mindset - to a web-based one), overall the company has embraced the features and power of Confluence within the working stack
• However, as costs continue to climb for the Atlassian product, we are forced to continue our evaluation of the product - with replacing it a remote possibility if it begins to outprice its usefulness to us.

• We are moving towards Gitlab only as our SCM & CI tool. So it would be an alternative to Jenkins. Saving our licensing cost there.
• We have also stopped using Confluence & using Gitlab for our documentation purposes. Reducing cost there as well.