Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
50 lines (39 sloc) 4.21 KB


Pull requests are always welcome both for content and wiki improvements.

Adding a wiki page

Adding a wiki page is as simple as creating a markdown file in the proper directory: the _posts subdirectory of either guides, pages, or knowledgebase depending on the type of page.

Page types

  • Guide - installation guides, tutorials, anything too long for a simple page, etc.
  • Page - flat pages covering a topic useful to self-hosters (e.g. containers vs native, nextcloud, Linux distro comparison)
  • Knowledge Base - problems/errors encountered while using/deploying/upgrading self-hosting apps and their solutions

Page format

File Name

The filename MUST start with a properly-formatted date code: YYYY-MM-DD-. This date is shown on the page as it's 'Last Updated' date, so it should be updated any time a page is updated. The remainder of the filename should be the page title, lowercase, with non-alphanueric characters removed, and spaces replaced by hyphens. (e.g.

Front Matter

Pages must start with jekyll's "Front Matter":

layout: post

layout must be post, but the rest of the fields are author-defined. title is the only required field, but authors are encouraged to complete all of them:

  • title - The title is automatically listed at the top of your page (so no need to include it in your content). It is also used in the wiki page listings
  • tags - The syntax for tags is [tag1, tag2, tag3]. Tags should be lower case alphanumeric. Please search the existing tags (see /tags) before adding your own. If you do add a new tag, you need to run scripts/ from the repository root to regenerate the tag listings.
  • author - The author's name, which is listed at the bottom of the page. Consider making this a link (i.e. [Author Name](<URL>)) to your Github profile, Reddit profile, or e-mail address so readers can get ahold of you.
  • assets - A convenience variable for the directory containing your pages assets (see below)


The first paragraph of content in a page is used as an excerpt shown in the "Related" section and also in search results. For this reason the first content on a page should be paragraph text (i.e. not a heading) and summarize the page. Since the page title is automatically added by jekyll, it should not be explicitly added to the page's source markdown.


If a page requires additional assets, such as images, scripts, pdf files, etc, those should be stored in a subdirectory of the assets directory adjacent to the _posts directory in which the page resides. The subdirectory should be the same as the page's filename, without the date code or extension. For example, if the page is guides/_posts/ then the assets should be placed in /guides/assets/example-guide-title/. For convenience, define an assets variable in the Front Matter above containing the path to that subdirectory. Use the following Liquid syntax to point to your assets: {{ "image.png" | prepend: page.assets | relative_url }}).

Syntax and Formatting

Most pages should be written entirely in Markdown. Although jekyll does support various variables via Liquid, use is strongly discouraged for the sake of compatibility. The exceptions are: asset paths, links, and syntax highlighting. For those, Liquid must be used. Additionally, always use | relative_url for paths. See the jekyll documentation for details. Guides and pages are relatively free form. For knowledge base entries, however, please follow the formatting in the example.


Please test build your changes before submitting a pull request. See The IPFS instance of the r/selfhosted wiki is built using jekyll, but note that you can contribute to the wiki entirely through Github by using its built-in editor and Github Pages.


You can’t perform that action at this time.