/comparison: Update content with more relevant data
Description
We just launched a new version of the comparisons pages (/comparison). We now need to make sure the content is accurate.
Proposal
- Update each comparison page with more relevant data
- Update the text above each table (that currently mentions GitLab being open source)
Activity
@amara let me know what you'd like to change at the top of the pages!
assigned to @scornille
assigned to @amara
@regisF I suggest we use similar messaging from the standalone EE page compare section. I'll draft the needed copy for the top sections in the GDoc.
Also, Stephane did some work on researching the comparisons. I dropped his info into a Google doc.
Edited by Amara Nwaigwe-
@regisF We can have the below text at the top just below the header
GitLab compared to other toolsThat way people can get a quick snapshot and then read the feature table for the detail.
- One platform for development and delivery: GitLab is the only platform that covers 100% of the software development lifecycle. With tightly-integrated version control, project management, code review, testing, deployment, and performance monitoring you can improve development and accelerate delivery in a single UI.
- Scale: A single machine server handles thousands of users and repositories. If your team is distributed, easily spin up a secondary GitLab Geo instance to ensure your distributed teams can quickly fetch and clone large repositories.
- Updated monthly: We release on the 22nd of every month so you never have to wait too long for new features. Of course, you choose when you update.
- Transparency: GitLab’s roadmap and issue trackers are open. Submit an issue, add your perspective to open issues, and follow the development process.
- Open source: GitLab Enterprise Edition customers also have access to the source code. Scan or modify the code to meet your security and development needs.
- Cost-effective: GitLab is feature-packed, updated monthly, and is a fraction of the cost. No need for multiple products with different billing cycles or complex licensing rules.
Edited by Amara Nwaigwe -
As for the content in the table, have you had a chance to review the info in the google doc?
We can use that to update existing comparison pages. We will need to so some more research before adding the Jenkins and JIRA pages.
-
@SeanPackham can you check with Amara to update the main advantages of GitLab in the comparison pages? Thanks!
added Sales Enablement label
assigned to @SeanPackham
-
@SeanPackham based on our discussion from last week the priorities for open technical content issues are:
- This issue to ensure that our comparison pages are up to date. Most pages say they were updated this month so we may be able to close this issue.
- Jenkins vs. GitLab CI comparison page, we should also link people to our documentation so they know that we also integrate with Jenkins
- Help people understand our Jenkins integration
- We agreed that GitLab vs. JIRA was not in our best interest right now as more prospects want to know how we can integrate with JIRA. Therefore, our goal should be help people understand how they can use GitLab and JIRA
Can you please take a look at these issues and assign to the relevant people on your team and let us know what timing is realistic for these deliverables? Let me know if there is anything you need from me as you look through each issue.
@amara and @SeanPackham this would be a good place to link to a short video as well demonstrating how the Jenkins and JIRA integrations work and look within the GL workflow.
@regisF as discussed with Job, going forward the PMs are responsible for updating their relevant product comparison pages as part of the development process when features are added/updated. I created a comparison page for Jenkins vs GitLab CI but I suggest creating specific issues for each comparison page and assigning it to the relevant PM.
