Contributing to Meshery Docs

Before contributing, please review the Documentation Contribution Flow. In the following steps you will set up your development environment, fork and clone the repository, run the site locally, and finally commit, sign-off, and push any changes made for review.

Documentation Framework

Meshery documentation is made of these components:

  • Framework - Jekyll
  • Theme -
  • Repo -
  • DNS -
  • AWS API GW - an instance is configured to redirect from to, because of the repo location of where the docs currently reside.

Set up your development environment

For Windows

Note: Windows users can run Jekyll by following the Windows Installation Guide and also installing Ruby Version Manager RVM. RVM is a command-line tool which allows you to work with multiple Ruby environments on your local machine. Alternatively, if you’re running Windows 10 version 1903 Build 18362 or higher, you can upgrade to Windows Subsystem for Linux WSL and run Jekyll in Linux instead.

  • Fire up your WSL VM and install the ruby version manager (RVM):
  sudo apt update
  sudo apt install curl g++ gnupg gcc autoconf automake bison build-essential libc6-dev \
    	libffi-dev libgdbm-dev libncurses5-dev libsqlite3-dev libtool \
    	libyaml-dev make pkg-config sqlite3 zlib1g-dev libgmp-dev \
    	libreadline-dev libssl-dev
  sudo gpg --keyserver hkp:// --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3
  curl -sSL | sudo bash -s stable
  sudo usermod -a -G rvm `whoami`

If gpg --keyserver gives an error, you can use:

  sudo gpg --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3


  sudo gpg2 --keyserver hkp:// --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3 7D2BAF1CF37B13E2069D6956105BD0E739499BDB

Restart your WSL VM before moving forward.

  • For installing Ruby, run:
      rvm install ruby
      rvm --default use ruby 2.7.1
      gem update
      gem install jekyll bundler

For Linux

  • Prerequisites
      sudo apt-get update
      sudo apt-get install autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-dev

Installing rbenv

  • Cloning the rbenv repository
      git clone ~/.rbenv
  • Setting the path
      echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc
  • rbenv init
      echo 'eval "$(rbenv init -)"' >> ~/.bashrc
  • Reload your bashrc
      source ~/.bashrc

    Note: Change bashrc with your shell specific rc file, for eg: if you are using zsh then the filename is zshrc.

  • Check installation
      type rbenv

Install Ruby

  • rbenv install version
  rbenv install 2.5.1
  • To list all the versions that can be installed
  rbenv install --list-all
  • Set which Ruby version you want to use
  rbenv global version
  • Check Ruby installation
  ruby -v

For MacOS

Get the code

  • Fork and then clone the Meshery repository
    $ git clone
  • Change to the docs directory
    $ cd docs
  • Install any Ruby dependencies

    $ gem install bundler
    $ bundle install

    Note: If you are a Mac user you do not need to install the Ruby dependencies, after moving on to the docs directory, you can serve the site.

Serve the site

  • Serve the code locally
    $ make site
  • If that gives an error run:

      $ bundle exec jekyll serve

    Note: From the Makefile, this command is actually running $ bundle exec jekyll serve --drafts --livereload. There are two Jekyll configuration, jekyll serve for developing locally and jekyll build when you need to generate the site artifacts for production.

Using Docker

If you’ve Docker and make installed in your system, then you can serve the site locally

$ make docker-docs

This doesn’t require the need for installing Jekyll and Ruby in your system

But, you need to make sure that GNU make is working in your system (might not work in Windows)


While performing the above step, if you’re facing errors with a message like below…

Your ruby version is x.x.x but your Gemfile specified 2.7.x

This is because Jekyll always considers the exact version of Ruby unlike JavaScript.

So, you need to follow either of the three steps to resolve this problem;

  • Install the required Ruby version by using rvm or by any means given above
  • Alternatively, if you have Docker installed, then type make docker-docs to view the changes
  • If you’re unable to install the required Ruby version, then manually configure the Gemfile as below (not recommended! Do only if above two steps fail):
source ""
ruby '2.7.1' //to any version you have installed

Automatically the Gemfile.lock will update once the make site is given (for Windows, run bundle exec jekyll serve if WSL2 isn’t present)

WARNING: If you have followed the third step then please don’t commit the changes made on Gemfile and Gemfile.lock in your branch to preserve integrity, else the CI action will fail to generate the site preview during PR.

Create a Pull Request

  • After making changes, don’t forget to commit with the sign-off flag (-s)!
    $ commit -s -m “my commit message w/signoff”
  • Once all changes have been committed, push the changes.
    $ git push origin <branch-name>
  • Then on Github, navigate to the Meshery repository and create a pull request from your recently pushed changes!

Using the features of Meshery Docs

Clipboard Feature

Most popular clipboard plugins like Clipboard JS require the manual creation of a new ID for each code snippet. A different approach is used here. For code snippets, we either use html tags or markdown in the following manner:

   <pre class="codeblock-pre"><div class="codeblock">
   <code class="clipboardjs">
     code snippet

<pre></pre> tags are optional unless the code snippet is in a paragraph format and also gives a terminal like effect to the code

A full block:

```code snippet```

Inline formatting:

`code snippet`: code snippet

Language specific:

```(language name)
  code snippet

Whenever the code tags are detected, the clipboard javascript file is automatically loaded. Each code element is given a custom id and a clipboard-copy icon to copy the content.

Documentation Contribution Flow Summary

The following is a concise summary of the steps to contribute to Meshery documentation.

  1. Create a fork, if you have not already, by following the steps described here
  2. In the local copy of your fork, navigate to the docs folder. cd docs
  3. Create and checkout a new branch to make changes within git checkout -b <my-changes>
  4. Edit/add documentation. vi <specific page>.md
  5. Run site locally to preview changes. make site
  6. Commit, sign-off, and push changes to your remote branch. git push origin <my-changes>
  7. Open a pull request (in your web browser) against the repo:

Table of Contents in Sidebar (toc)

Sidebars use toc to create a table of contents. It is written in the following manner:

  - title: Group 1
      - page: Thing 1
        url: /thing1.html
      - page: Thing 2
        url: /thing2.html
      - page: Thing 3
        url: /thing3.html

The output of the code snippet would be:

    Group 1
      Thing 1
      Thing 2
      Thing 3

if condititional

This executes the block of code only if the given condition is true. It is executed in the following manner:

    {% if product.title == 'Awesome Shoes' %}
    These shoes are awesome!
    {% endif %}

If the condition is true, the output would be:

    How are you?

for loop

The for statement executes a block of code repeatedly. It is wriiten in the following manner:

    {% for names in collection.names %}
    {{ name.title }}
    {% endfor %}

The output produced by the above code snippet:

    Sam Ham Ethan


Comments allow to leave a block of code unattended, any statements between opening and closing comment would not be executed.


The above tag is used to insert a already rendered file within the current template. It is written in the following manner:

    {% include file.html %}


The assign tag is used to create a new variable. It is written in the following manner:

    {% assign variable1 = true %}

Suggested Reading