Skip to content
This repository has been archived by the owner. It is now read-only.
YugaByte DB Docs -- this repository has moved to the subdirectory
HTML CSS JavaScript
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
content Update version to 1.2.11 and add release notes (#146) Jun 25, 2019
contributing Add files via upload Mar 29, 2019
styles Update shadows to make them similar to YW and docs index page (#134) Jun 11, 2019
.babelrc Add section icons, npm scripts, node-sass, webpack, eslint Nov 17, 2017
.gitignore Remove hardcoded keys Feb 5, 2019 Update May 28, 2019
LICENSE Create LICENSE Jun 2, 2019 Update Jul 15, 2019
package-lock.json Update the node-sass version to 4.12.0 (#91) May 28, 2019
package.json Update the node-sass version to 4.12.0 (#91) May 28, 2019
webpack.config.js Add section icons, npm scripts, node-sass, webpack, eslint Nov 17, 2017



YugaByte DB Docs

This repository contains the documentation for YugaByte DB available at

Please open an issue to suggest enhancements.

Contributing to YugaByte DB Docs

YugaByte DB docs are based on the Hugo framework and use the Material Docs theme.

Step 1. Initial setup

Follow these steps if this is the first time you are setting up the YugaByte docs repo locally.

  1. Fork this repository on GitHub and create a local clone of your fork. This should look something like below:
git clone<YOUR_GITHUB_ID>/docs.git

Add the master as a remote branch by running the following:

$ git remote add --track master upstream
  1. Install Hugo. For example, on a Mac, you can run the following commands:
brew update
brew install hugo
brew install npm
  1. Copy the config.yaml.sample to config.yaml.
cp config.yaml.sample config.yaml
  1. Install node modules as shown below:
$ npm ci

Step 2. Update your docs repo and start the local webserver

The assumption here is that you are working on a local clone of your fork. See the previous step.

  1. Rebase your fork to fetch the latest docs changes: Ensure you are on the master branch.
$ git checkout master

Now rebase to the latest changes.

$ git pull --rebase upstream master
$ git push origin master
  1. Start the local webserver on interface by running the following:
$ npm start

You should be able to see the local version of the docs by browsing to: http://localhost:1313/

Note #1 that the URL may be different if the port 1313 is not available. In any case, the URL is printed out on your shell as shown below.

Web Server is available at //localhost:1313/ (bind address
Press Ctrl+C to stop

Note #2 To start the webserver on some other IP address (in case you want to share the URL of your local docs with someone else), do the following:


You can now share the following link: http://<YOUR_IP_OR_HOSTNAME>:1313

Step 3. Make changes

Make the changes locally and test them on the browser.

Once you are satisfied with your changes, commit them to your local branch. You can do this by running the following command:

# Add all files you have made changes to.
$ git add -A

# Commit these changes.
$ git commit

Step 4. Submit a pull request

Create a pull request in the YugaByte docs repo once you are ready to submit your changes.

We will review your changes, add any feedback and once everything looks good merge your changes into the mainline.

You can’t perform that action at this time.