A separate system for documentation called Wiki, is built right into each GitLab project. It is enabled by default on all new projects and you can find it under Wiki in your project.

Wikis are very convenient if you don’t want to keep your documentation in your repository, but you do want to keep it in the same project where your code resides.

You can create Wiki pages in the web interface or locally using Git since every Wiki is a separate Git repository.

Introduced in GitLab Premium 13.5, group wikis became available. Their usage is similar to project wikis, with a few limitations.

First time creating the Home page

The first time you visit a Wiki, you are directed to create the Home page. The Home page is necessary to be created because it serves as the landing page when viewing a Wiki. Complete the Content section, and then select Create page. You can always edit it later, so go ahead and write a welcome message.

New home page

Creating a new wiki page

noteRequires Developer permissions.

Create a new page by selecting the New page button that can be found in all wiki pages.

Enter a title for your new wiki page.

You can specify a full path for the wiki page by using ‘/’ in the title to indicate subdirectories. Any missing directories are created automatically. For example, a title of docs/my-page creates a wiki page with a path /wikis/docs/my-page.

After you enter the page name, it’s time to fill in its content. GitLab wikis support Markdown, RDoc, AsciiDoc, and Org. For Markdown based pages, all the Markdown features are supported and for links there is some wiki specific behavior.

In the web interface the commit message is optional, but the GitLab Wiki is based on Git and needs a commit message, so one is created for you if you don’t enter one.

When you’re ready, select Create page and the new page is created.

New page

Attachment storage

Version history

Any file uploaded to the wiki with the GitLab interface is stored in the wiki Git repository, and is available if you clone the wiki repository locally. All uploaded files prior to GitLab 11.3 are stored in GitLab itself. If you want them to be part of the wiki’s Git repository, you must upload them again.

Special characters in page titles

Wiki pages are stored as files in a Git repository, so certain characters have a special meaning:

  • Spaces are converted into hyphens when storing a page.
  • Hyphens (-) are converted back into spaces when displaying a page.
  • Slashes (/) can’t be used, because they’re used as path separator.

Length restrictions for file and directory names

Version history

Many common file systems have a limit of 255 bytes for file and directory names, and while Git and GitLab both support paths exceeding those limits, the presence of them makes it impossible for users on those file systems to checkout a wiki repository locally.

To avoid this situation, these limits are enforced when editing pages through the GitLab web interface and API:

  • 245 bytes for page titles (reserving 10 bytes for the file extension).
  • 255 bytes for directory names.

Please note that:

  • Non-ASCII characters take up more than one byte.
  • It’s still possible to create files and directories exceeding those limits locally through Git, but this might break on other people’s machines.

Editing a wiki page

You need Developer permissions or higher to edit a wiki page. To do so:

  1. Select the edit icon ().
  2. Edit the content.
  3. Select Save changes.

Adding a table of contents

To generate a table of contents from the headings in a Wiki page, use the [[_TOC_]] tag. For an example, see Table of contents.

Deleting a wiki page

You need Maintainer permissions or higher to delete a wiki page. To do so:

  1. Open the page you want to delete.
  2. Select Delete page.
  3. Confirm the deletion.

Moving a wiki page

You need Developer permissions or higher to move a wiki page. To do so:

  1. Select the edit icon ().
  2. Add the new path to the Title field.
  3. Select Save changes.

For example, if you have a wiki page called about under company and you want to move it to the wiki’s root:

  1. Select the edit icon ().
  2. Change the Title from about to /about.
  3. Select Save changes.

If you want to do the opposite:

  1. Select the edit icon ().
  2. Change the Title from about to company/about.
  3. Select Save changes.

Viewing a list of all created wiki pages

Version history
  • Introduced in GitLab 13.5, wiki pages are displayed as a nested tree in the sidebar and pages overview.

Every wiki has a sidebar from which a short list of the created pages can be found. The list is ordered alphabetically.

Wiki sidebar

If you have many pages, not all are listed in the sidebar. Select View All Pages to see all of them.

Viewing the history of a wiki page

The changes of a wiki page over time are recorded in the wiki’s Git repository, and you can view them by selecting Page history.

From the history page you can see the revision of the page (Git commit SHA), its author, the commit message, and when it was last updated. To see how a previous version of the page looked like, select a revision number in the Page version column.

Wiki page history

Viewing the changes between page versions

Version history

Similar to versioned diff file views, you can see the changes made in a given Wiki page version:

  1. Navigate to the Wiki page you’re interested in.
  2. Select Page history to see all page versions.
  3. Select the commit message in the Changes column for the version you’re interested in.

    Wiki page changes

Wiki activity records

Version history

Wiki events (creation, deletion, and updates) are tracked by GitLab and displayed on the user profile, group, and project activity pages.

Adding and editing wiki pages locally

Since wikis are based on Git repositories, you can clone them locally and edit them like you would do with every other Git repository.

In the right sidebar, select Clone repository and follow the on-screen instructions.

Files that you add to your wiki locally must have one of the following supported extensions, depending on the markup language you wish to use, otherwise they don’t display when pushed to GitLab:

  • Markdown extensions: .mdown, .mkd, .mkdn, .md, .markdown.
  • AsciiDoc extensions: .adoc, .ad, .asciidoc.
  • Other markup extensions: .textile, .rdoc, .org, .creole, .wiki, .mediawiki, .rst.

Customizing sidebar

Version history
  • Introduced in GitLab 13.8, the sidebar can be customized by selecting the Edit sidebar button.

To customize the Wiki’s navigation sidebar, you need Developer permissions to the project.

In the top-right, select Edit sidebar and make your changes. This creates a wiki page named _sidebar which fully replaces the default sidebar navigation.

Example for _sidebar (using Markdown format):

### [Home](home)

- [Hello World](hello)
- [Foo](foo)
- [Bar](bar)


- [Sidebar](_sidebar)

Support for displaying a generated table of contents with a custom side navigation is planned.