After you've gotten the docs site running locally, make your changes. If you're going to be doing this a lot, read some tips on setting up your text editor.

If you need to edit syntax diagrams, see Edit syntax diagrams.

Edit an existing page

  1. In your local copy of your yugabyte-db fork, make a branch.

    git checkout -b my-branch-name
    
  2. Find your file in docs/content/<version>/ and edit it as required.

  3. Verify that your changes look good in the live-reload server.

    npm start
    
  4. Commit your changes.

    git commit -A -m "Your commit message here"
    
  5. Push your changes to your fork.

    git push origin
    

At this point, you're ready to create a pull request.

Add a new page

If you can, copy an existing page in the location you want the new page to be, and adjust.

Adding a new page is similar in most ways to editing an existing page, with the added complexity of sorting out the frontmatter so that the page works correctly in the site, including showing up in the left-side navigation menu. See how docs pages are structured for more information.

More content in this section is forthcoming.

Make a pull request

After you've made your changes, make a pull request by telling GitHub to compare a branch on your fork to the master branch on the main repository.

Use the PR preview build

Preview builds take 5 minutes to build.

All PR previews on the main repository are of the form https://deploy-preview-ABCDE--infallible-bardeen-164bc9.netlify.app/ where ABCDE is the pull request number.

Add a line in your PR's description to tag the Netlify bot and tell it where to launch the preview:

@netlify /preview/quick-start/

https://linkchecker.github.io/linkchecker/

Ask for a review

Internal contributors, please tag a member of the docs team for review, along with technical reviewers as required, and let us know about your PR in the #docs channel in Slack.

External contributors, please add the area/documentation label to your pull request, and let us know about it in Slack.