The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
| Stage | Plan |
| Content Last Reviewed | 2025-02-06 |
Welcome to the Knowledge Group direction page! Knowledge Group is in the Plan Stage of GitLab and contains the Wiki, Pages, Markdown, and Text Editors categories. Knowledge Group also manages the development of GitLab Query Language (GLQL), as well as Views, powered by GLQL. These categories, and GLQL, fall within the knowledge management (KM) market as defined by Gartner. The focus of KM is to provide visibility and access to a flow of information across a variety of operations, enabling collaboration that has traditionally existed in silos. Commonly used products in the KM market include Confluence, and Notion.
If you have feedback related to Knowledge Group please comment and/or contribute in these Issues, or create a new issue if you find none fit your criteria. Make sure to tag @mmacfarlane, Product Manager for Knowledge Group, so he can read and respond to your comment. Sharing your feedback via Issues is the one of the best ways to contribute to our strategy and vision!
At GitLab, our vision is to become the AllOps platform, a single application for all innovation. Knowledge Group plays a pivotal role in this transformation by breaking down silos and enabling seamless collaboration across teams and roles. Here's how our Knowledge Group categories drive this vision forward:
Pages: GitLab Pages transforms web hosting by making it accessible to users of all skill levels. Our new Parallel Deployments feature significantly reduces deployment times and eliminates bottlenecks, letting you publish updates faster than ever. For teams managing multiple sites, we aim to develop robust user authentication and comprehensive audit logging to provide better security and governance. These improvements will give content teams more control while maintaining the technical flexibility developers love.
Text Editors and Markdown: Transform how your teams collaborate with GitLab's dual editing experience. Choose between our enhanced Rich Text Editor for intuitive WYSIWYG editing, or stick with our Plain Text Editor which used Markdown for precise control (both seamlessly integrated across the entire platform). Technical teams can work efficiently in Markdown while non-technical team members can use familiar formatting tools, all contributing to the same content. Switch between editors anytime, giving every user the flexibility to work their way. With advanced capabilities and lightning-fast performance in both editors, GitLab adapts to each user's preferences while maintaining consistency throughout your workflows. This unified yet flexible experience eliminates context switching and brings your entire organization into the same collaborative environment.
Wiki: GitLab's Wiki brings your documentation directly into your development workflow, making knowledge sharing natural and efficient. Create, edit, and collaborate on documentation using familiar tools - whether you prefer Markdown or our Rich Text Editor. New features like PDF export let you share documentation beyond GitLab, while customizable templates help teams maintain consistency. We're also experimenting with Wiki comments, enabling teams to discuss and refine documentation without leaving the context of their work. Based on extensive user research, these improvements transform GitLab's Wiki from a simple documentation tool into an integral part of your team's daily workflow.
Text Editors and Markdown: Rich Text Editor: Release Rich Text Editor Generally, Display and Edit Markdown Comments in the Rich Text Editor, Insert Table of Contents in the Rich Text Editor.
Wiki: Draw.io/diagrams.net integration with wiki, Editing Sidebar in Project or Group Wiki Removes Existing Sidebar,Relative Links are Broken On Wiki ASCII Pages, templates in wiki, and autocomplete.
Pages: GitLab Pages without DNS Wildcard and GitLab Pages Parallel Deployments Beta.
Pages: GitLab Pages Parallel Deployments GA
Rich Text Editor: Enabling the rich text editor across GitLab
Wiki: GLQL implementation in GitLab, including Wiki, Wiki Comments GA
GitLab's Knowledge tools break down information barriers by bringing documentation, planning, and collaboration into your development workflow. Unlike standalone solutions like Confluence, Notion, or GitHub, GitLab integrates knowledge sharing directly where work happens. Our unified platform combines powerful documentation capabilities through Pages, flexible editing with both Markdown and Rich Text, and collaborative Wikis - all in the same place where you plan, code, and deploy. This integration eliminates the context switching and fragmentation that comes from managing knowledge across multiple tools, making information naturally discoverable and actionable.
Pages: We are invested in supporting the process of developing and deploying code from a single place as a convenience for our users. Other providers, such as Netlify, deliver a more comprehensive solution. There are project templates available that offer the use of Netlify for static site CI/CD, while also still taking advantage of GitLab for SCM, merge requests, issues, and everything else. GitLab offers configurable redirects, a well-loved feature of Netlify, made available in gitlab-pages. We are seeing a rise in JAMStack and static site generators partnering in the media. This trend toward API-first, affirms our modernization effort of Pages, reinforcing our cloud native installation maturity plan. GitHub also offers hosting of static sites with GitHub Pages. Key differentiators between the two are that GitHub Pages configuration and deployment is more "automatic" in that it doesn't require you to edit a CI configuration file, and that GitHub Pages has limits placed on bandwidth, builds, and artifact size where GitLab currently does not.
Wiki: We currently most closely compete with GitHub Wiki but we would like to compete with Confluence, Notion, Roam Research, and Google Docs. We've heard from customers that managing wikis with tens of thousands of pages can be challenging. And while a full-featured product like Confluence has advanced features and integrations, the GitLab wiki would be a stronger competitor if we improved our sidebar structure and parity between Group and Project Wikis.