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 | 2024-12-04 |
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). 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 GitLab, 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 is a signficant contributor to this vision given its focus on enabling collaboration across users regardless of their role. An overview of how each Knowledge Group category aligns with this vision is as follows:
Pages: Our vision for Pages is to provide an experience that guides and supports users to host static assets on the web, regardless of their level of development experience. At the moment we are working on one major customer request, GitLab Pages Parallel Deployments, which will further enable us to provide the aforementioned experience. We are already evaluating future opportunities around improving the experience of creating and configuring Pages sites and making content management and collaboration easier for non-developer personas. Two ideas include User Authentication and Authorization and Offering Audit Logs.
Text Editors and Markdown: We are primarily focused on creating location parity between the Rich Text Editor and Plain Text Editor via introducing the Rich Text Editor across more areas of GitLab. We're confident creating location parity will improve accessibility and allow users who traditionally feel GitLab is too technical a better opportunity to contribute. We are also continuously focusing on advanced editing and performance stabilization.
Wiki: The Wiki is an important part of the Agile Planning workflow. The Wiki was in stable maintenance mode for much of FY23 and early FY24. We've recently enhanced the Wiki to include a print PDF feature and introduced the rich text editor within it. In 16.10 we also introduced templates in the Wiki. We hope to leverage the JTBD we've identified for the category to create a solution that effectively compliments our Agile Planning offering.
Pages: Our 1 year plan for Pages can be broken into two distinct themes, stability and improvement.
Our first theme, stability, focuses on the breakdown of existing bugs and maintenance items, as well as updating documentation related to previous releases. Specific to documentation, we've come to understand that some previous feature rollouts did not include updates to technical documentation, which has caused some confusion to users in utilizing the product.
Our second theme, improvement, focuses on new feature development. We are acutely aware of four major customer requests as detailed on the Pages Direction Page. We aim to prioritize these items to improve our customer experience, and are thankful to our customers for their patience and feedback as we look to deliver these items.
Text Editors and Markdown: Our 1 year plan for Text Editors and Markdown revolves around the theme of GitLab as an AllOps plaftorm. We hope to implement the new Rich Text Editor across GitLab to improve accessibility and efficiency for all users of GitLab. You can follow our progress in the General Availability Epic.
Wiki: In FY24Q2 we completed research on the Wiki category in order to develop JTBD. We've finalized these JTBD and will utilize them to inform our Wiki strategy.
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
Knowledge Group Competitive Statement: The focus of Knowledge group 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 market include Confluence, Notion, and GitHub. We believe that fundamental improvements in our Pages, Text Editors, Markdown, and Wiki categories enable us to deliver a more competitive planning experience against industry leaders.
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.
Text Editors and Markdown: These two categories do not necessarily have a direct competitor but they are important to our vision of becoming an AllOps platform.
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.