1. Welcome to git-wiki demo!
    1. Getting started
    2. Features
    3. Who is using git-wiki
      1. Share your wiki with us! and keep the “Powered by Git-Wiki” footer link please. It will help both of us!
    4. Installation instructions
      1. Remote theme method
      2. Direct installation method
      3. Notes:
      4. Local development
    5. Configuration and customization
    6. Current known limitations
    7. Support & Collaboration
    8. Components used

Welcome to git-wiki demo!

This is both documentation and demo of git-wiki theme project.

it’s a modular and full featured wiki powered by git, github/gitlab pages and pull-requests!

The git-wiki project is composed by 3 different repository:

  • git-wiki-theme: This is the repository of the theme that implements the wiki functionalities. You would have not fork it unless you need to send a Pull Request or create your wiki project from scratch.

  • git-wiki-skeleton: This is the repo that you should fork or use as a template. It uses the jekyll remote theme functionality that allows you to create your own wiki based on git-wiki-theme. By using the remote functionality you can automatically keep your wiki always updated with latest features from the git-wiki-theme, but you can also fully customize it.

  • git-wiki: This is the documentation repository and website of the git-wiki-theme project. You would have not fork it unless you want to contribute to the git-wiki project documentation.

Getting started

The easier and faster way to use git-wiki is the “skeleton” method.

You don’t need to install anything locally!

  1. Simply fork/clone skeleton repo or click on “Use this template” button to create your copy of the skeleton project.

  2. Edit _config.yml and other pages as you need and then deploy it on github/gitlab pages.

Done! now wait that your page will be published and you’re ready to wiki!

For more installation options see the Installation instructions


  • Improvements in the cooperative aspect: forks, pull-requests and roles.
  • You can customize your wiki as you want with style sheets and even changing the layout. (see customization section below)
  • No databases! Only static files that can be downloaded in a few seconds.
  • Blazing fast and free thankfully to Github/Gitlab Pages and Jekyll Server Side Generation process!
  • Markdown and html mixed together!
  • Multiple free search engines! on a static site!
  • History, revision comparison and everything you need from a wiki platform.
  • You can edit your pages with the standard git editor, (integrated) or any kind of editor you prefer.
  • Non-existent wiki page links are “red”, you can click on them to automatically create a new page!
  • External links get the right icon automatically
  • Component system with hooks that allows you to totally customize your wiki UI. (see customization section below)
  • Some nice internal themes to change your entire wiki UI with 1 simple configuration (see customization section below)
  • Integrated Blogging feature thanks to jekyll!
  • Automatic generated TOC
  • You can download the entire wiki for offline usage and even navigate directly using a markdown reader

You can use it with jekyll “remote_theme” feature or fork/copy the master branch and start your wiki in just 1 minute*.

Git-wiki can be used as theme for jekyll

*Github/Gitlab pages takes about 10 minutes to show up the first time you configure it

Note: You can even include the official github wiki as a submodule and enable the option in our conf file to use github wiki pages in git-wiki system, but it’s an experimental feature and it implies less advantages and greater disadvantages for now.

Who is using git-wiki

List of git-wiki installations

List of forked repository

Installation instructions

Remote theme method

  1. Fork, Clone the skeleton repository or click on “Use this template” button to create your copy.

  2. Edit _config.yml and other pages as you need and then deploy it on github/gitlab pages.

Description: This method will allow you to create a wiki based on our skeleton repository and that extends git-wiki-theme.

Direct installation comparison:

  • pros: This will allow you to avoid upgrading process pulling files from git-wiki-theme and eventually merge them.

  • cons: To edit/fix git-wiki-theme core files you need to configure a second repository forked by git-wiki-theme repo. However, YAGNI

GITLAB SUPPORT: if you want to fork the skeleton from gitlab, you can use this repo

Without skeleton: you can avoid to use the skeleton repository if you want start from scratch, however it’s important to use at leaset the configuration variables needed by the theme: _config.yml

Direct installation method

  1. Fork, Clone git-wiki-theme repository or click on “Use this template”

  2. Edit _config.yml and push your changes in your repository, then configure the github/gitlab pages in your repository settings

Description: This method will allow you to create a wiki using git-wiki-theme directly. You can create your theme from scratch. It’s for advanced users and people who want directly collaborate to git-wiki-theme project.

Remote installation comparison:

  • pros: You can build your wiki and collaborate with git-wiki-theme project by PR at the same time.

  • cons: Upgrading your wiki to the latest version need a merge with git-wiki-theme repo.


In both cases please is preferred to use Fork instead of Template and Template instead of Clone (Fork > Template > Clone). Fork will allow you to make pull request to/from original repository to keep your files updated (for skeleton too). Please, keep everything open and collaborative!

Local development

If you need to work on git-wiki locally before publish, then clone your wiki repo and follow this instructions from official github article: Git wiki already contains the Gemfile for local installations.

You can also use our docker files to run git-wiki under docker, the easiest method is to run docker-compose up command in this folder

Configuration and customization

Current known limitations

  • You can’t use the wiki internal link format: [[example]]. Please, use gh-pages links instead: [example](example) . It’s a known jekyll limitation:

Support & Collaboration

You can open a public issue on github , send a private email or create a PR to improve it.

Thank you!

Components used