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 |
| Maturity | Viable |
| Content Last Reviewed | 2023-09-13 |
Thanks for visiting the Wiki category direction page in GitLab. This page belongs to the Knowledge group of the Plan Stage and is maintained by Matthew Macfarlane (E-Mail). More information about the Knowledge group's priorities and direction can be found on the Knowledge group direction page.
This strategy is a work in progress, and everyone can contribute to it:
The GitLab Wiki is a great place to store documentation and organize information Each GitLab project and group includes a Wiki rendered by Gollum, and backed by a Git repository. Premium and Ultimate customers have access to the group-level Wiki for consolidating documentation across multiple projects or teams.
We want the wiki to serve as a single source of truth for project- or group-level documentation that is approachable and easily accessibly by anyone. As we look to future plans, we will be exploring ways to encourage collaboration across all personas by improving the editing and navigation experience.
Specifically, we are looking to better integrate the Wiki experience with the rest of GitLab. One immediate opportunity is to better integrate with Issues and Epics. We are looking to better understand how users could benefit from a closer integration between the Wiki.
Our primary persona is Sasha, the Software Developer, but all personas can use Wikis for storing information and everyone should be able to quickly and easily contribute to a wiki page. As the wiki matures, we may need to investigate other, non-developer personas as our research found they are frequent users of wikis.
We have recently drafted Jobs to Be Done (JTBD) for the category in order to best drive the Wiki forward. We also have a backlog of feature requests that help inform us on what users are looking for both immediately and in the near term.
We know that our new WYSIWYG Markdown editor can support real-time collaborative editing, but we may need an entirely new backend to support collaborative editing of Wiki pages. Ideally, we want to solve the problem of collaborative note taking, be highly approachable for everyone, but also offer the tremendous benefits of storing the content in a portable plain text format that can be cloned, viewed and edited locally (properties of Git). However, we are not actively working on a new architecture that can support this experience.
Wiki transitioned from Create Stage to Plan Stage in GitLab in early FY24. The future direction of Wiki, as a result of this transition, is being evaluated. Prior to this change Wiki was in Maintenance Mode.
We compete with the following knowledge management tools (not and exclusive list):
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 fixed some low-hanging fruit related to page title and redirects.
GitLab does not have any organization-wide wikis, but some teams do use them for various purposes.
The Knowledge Team utilizes the GitLab Wiki for Opportunity Mapping via the recent introduction of diagrams.net. More information can be found on this integration via our Unfiltered channel.
Our top strategy items are aligned with what our customers are asking for. We have good data backing our need to fulfill the following asks: