Git-Wiki stores the pages in a git repository. Therefore you can use all the benefits of the revision control software (distributed content etc). Multiple markup languages are supported via plugins. The wiki has a very extensible architecture. Custom markup can be added via filters. Additional tags can be added (e.g. the math tag which is provided for LaTeX-rendering).
- Support for images and attachments - You can add images to /img folder of your git repository. Subfolders are also supported. At least gif, png and jpg supported
- Custom h1 header - If your wiki page contains a markdown h1 header, then this one is used on the page.
- Sections - Content separated by headers like h1 is wrapped with divs, so you can style such blocks as you wish. Every header gets a unique id
- Style - You can provide a custom stylesheet for your wiki or project in the project.css file.
- Wiki in a subfolder - You can use git-wiki for documentation of your software project. Simply put all the content in markdown format into a subfolder, e.g. wiki and provide the folder name as optional parameter.
- Upstream git repository
- Integrated TODO list(s)
- Inclusion - You can include tasks from other wiki pages.
- No wiki words - For a hacker the wiki words is more a distraction than a help.
- Git-based CMS
- ikiwiki - a wiki compiler. It converts wiki pages into HTML pages suitable for publishing on a website. Ikiwiki stores pages and history in a revision control system such as Subversion or Git. There are many other features, including support for blogging, as well as a large array of plugins.