IntenseWebs/grafana
3
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2024-11-22 00:47:38 -06:00
Code Issues Packages Projects Releases Wiki Activity
535ed75ab2
grafana/docs
History
ashishagarwal06 535ed75ab2
Docs : - Added period (#28260) 
* Docs : - Removed Dot 

Hi - Removed Dot to make it consistent with other points.

Thanks,
Ashish

* Update _index.md
2020-10-15 12:09:36 -04:00
..
sources Docs : - Added period (#28260) 2020-10-15 12:09:36 -04:00
.gitignore Docs: Add minimal hugo build, update docs README (#20905) 2019-12-13 15:47:28 +01:00
logo-horizontal.png Added back logo file (#21198) 2019-12-19 09:09:48 -08:00
Makefile Docs: Rename field configuration options page to field options (#27604) 2020-09-16 09:38:28 +02:00
README.md Docs: Fixed lazy numbering in all documentation files (#27975) 2020-10-01 12:45:05 -04:00
versions.json docs: update versions (#20635) 2019-11-25 15:40:27 +01:00

README.md

Building the docs locally

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.
  2. 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

Edit content in the sources directory.

Using relref for internal links

Use the Hugo shortcode relref any time you are linking to other internal docs pages.

Edit the side menu

Edit 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 if you'd like to do it yourself.