{{% readfile "./macos.md" %}}
{{% readfile "./ubuntu.md" %}}
## Configure Hugo
By default, Hugo uses the operating system's temporary directory to cache modules, which can cause some problems. You can avoid those problems by telling Hugo to put its cache elsewhere.
Add a line similar to the following to your `.bashrc` or `.zshrc` file:
```sh
export HUGO_CACHEDIR=~/.hugo-cache
```
Create the folder with `mkdir ~/.hugo-cache`, then start a new terminal session.
## Fork the repository
1. To make the commands in this section work correctly when you paste them, set an environment variable to store your GitHub username. (Replace `your-github-id` in the following command with your own GitHub ID.)
```sh
export GITHUB_ID=your-github-id
```
1. Fork the [`yugabyte-db` GitHub repository](https://github.com/yugabyte/yugabyte-db/).
1. Create a local clone of your fork:
```sh
git clone https://github.com/$GITHUB_ID/yugabyte-db.git
```
1. Identify your fork as _origin_ and the original YB repository as _upstream_:
```sh
cd yugabyte-db/
git remote set-url origin https://github.com/$GITHUB_ID/yugabyte-db.git
git remote add upstream https://github.com/yugabyte/yugabyte-db.git
```
1. Make sure that your local repository is still current with the upstream Yugabyte repository:
```sh
cd docs/
git checkout master
git pull upstream master
```
Refer to [Edit an existing page](../docs-edit/#edit-an-existing-page) to create a new branch, commit your changes, and create a pull request.
## Build the docs site {#live-reload}
The YugabyteDB documentation is written in Markdown, and processed by Hugo (a static site generator) into an HTML site.
To get the docs site running in a live-reload server on your local machine, run the following commands:
```sh
cd yugabyte-db/docs # Make sure this is YOUR fork.
npm ci # Only necessary the first time you clone the repo.
hugo mod get -u # Installs Hugo as a dependency of the site.
hugo mod clean # Only necessary the first time you clone the repo.
npm start # Do this every time to build the docs and launch the live-reload server.
```
The live-reload server runs at