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.
|Content Last Reviewed||
Thanks for visiting the Wiki category direction page in GitLab. This page belongs to the Editor group of the Create stage and is maintained by Eric Schurter (E-Mail). More information about the Editor group's priorities and direction can be found on the Editor group direction page.
This strategy is a work in progress, and everyone can contribute to it:
GitLab Wikis are a great way to share documentation and organize information via built-in functionality. Each GitLab project includes a Wiki rendered by Gollum, and backed by a Git repository.
Walkthrough of GitLab wikis (starts at 9 minutes):
Shipping in 13.5, we've added Group Level Wikis which will give our organizations the ability to collaborate in a shared wiki that spans multiple projects. (This is currently the most upvoted issue on GitLab!) In the future, we will be tackling issues around Markdown rendering, improving support for other formats, and tidying up navigation in the Wiki.
We are beginning to explore a Confluence integration and testing Confluence Cloud with our own projects. Work on this can be seen in this epic.
As we look to future plans beyond 2020, we will be exploring ways to implement real time editing and WYSIWYG collaboration. We know that our backend of Git will support WYSIWG, but we may need a new architecture for live editing. 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).
As our current wiki is built on top of Git, there may be a need for a more streamlined editing experience that is not backed by Git. We may call this GitLab Notes.
We are currently working on:
After we complete the work on Group Wiki, we'll be focused on:
In October 2020 the Wiki category was moved into the Editor group. Among other benefits, this realignment of categories means the Wiki has the same DRI as the Web IDE, Snippets, and Static Site Editor and one of the immediate goals for the Editor group is implementing a new rich text, WYSIWYG editor. The intent of this new editor is to allow other categories to adopt the same component for a consistent experience. While the implementation of this WYSIWYG editor is not our primary focus for the Wiki, it's likely that we will be able to benefit from the new editor with relatively little effort. Given its usage and similar target persona, the Wiki would be a great secondary dogfooding opportunity for the new rich text editor.
In other words, while we're not actively working on WYSIWYG or collaborative, real-time editing for the Wiki, other categories have similar needs and the work being done on these features may be valuable to the Wiki in the near future.
This category is currently at the Viable maturity level, and our next maturity target is 2021 (see our definitions of maturity levels).
We currently most closely compete with GitHub Wikis but we would like to compete with:
GitLab does not have any organization-wide wikis, but some teams do use them for various purposes.