grafana/docs/README.md

38 lines
1.6 KiB
Markdown
Raw Normal View History

# Building the docs locally
2015-03-12 14:19:59 -05:00
When you contribute to documentation, it is a good practice to build the docs on your local machine to make sure your changes appear as you expect. This README explains the process for doing that.
## Requirements
Docker >= 2.1.0.3
## Build the doc site
1. In the command line, make sure you are in the docs folder: `cd docs`.
1. Run `make docs`. This launches a preview of the docs website at `http://localhost:3002/docs/grafana/latest/` which will refresh automatically when changes to content in the `sources` directory are made.
---
## Content guidelines
2015-03-12 14:19:59 -05:00
Edit content in the `sources` directory.
2015-03-12 14:19:59 -05:00
### Using `relref` for internal links
2019-12-30 01:18:51 -06:00
Use the Hugo shortcode [relref](https://gohugo.io/content-management/cross-references/#use-ref-and-relref) any time you are linking to other internal docs pages.
### Edit the side menu
Edit [sources/menu.yaml](sources/menu.yaml) to make changes to the sidebar. Stop and rerun the `make docs` command for changes to take effect.
### Add images
Images are currently hosted in the grafana/website repo.
---
## Deploy changes to grafana.com
When a PR is merged to master with changes in the `docs/sources` directory, those changes are automatically synched to the grafana/website repo and published to the staging site.
Generally, someone from marketing will publish to production each day, so as long as the sync is successful your docs edits will be published. Alternatively, you can refer to [publishing to production](https://github.com/grafana/website#publishing-to-production-grafanacom) if you'd like to do it yourself.