
* Docs:Adjust azuread.md for Powershell UUID command Why this change is needed: -Update the docs to include more Unique ID information for Windows users. This is intended to improve user experience. -Adjust passive to active voice where it improves the documentation. -Checking for style guide compliance. Closes issue: #23094 * Update azuread.md Fixed typo "possibile". * Update docs/sources/auth/azuread.md fix capital letter U and G. Co-authored-by: Diana Payton <52059945+oddlittlebird@users.noreply.github.com> * Update docs/sources/auth/azuread.md Adjust punctuation for clarity. Co-authored-by: Diana Payton <52059945+oddlittlebird@users.noreply.github.com> * Update docs/sources/auth/azuread.md Place Note in correct bold markup following style guide. Co-authored-by: Diana Payton <52059945+oddlittlebird@users.noreply.github.com> * Update docs/sources/auth/azuread.md Bold markup for UI fields. Co-authored-by: Diana Payton <52059945+oddlittlebird@users.noreply.github.com> * Update docs/sources/auth/azuread.md Capital for id > ID. Co-authored-by: Diana Payton <52059945+oddlittlebird@users.noreply.github.com> * Including suggestions as noted by Diana Payton * adjusting object IDs to match the docs.microsoft style * using bold for UI elements * Other fixes as needed Update docs/sources/auth/azuread.md Capital for id > ID. Co-authored-by: Diana Payton <52059945+oddlittlebird@users.noreply.github.com> * Update docs/sources/auth/azuread.md Add the adverb to place the next step directly after the previous step in sequence. Co-authored-by: Diana Payton <52059945+oddlittlebird@users.noreply.github.com> * Update docs/sources/auth/azuread.md Change remaining lowercase "id" use to upper case "ID" when it appears in text. Co-authored-by: Diana Payton <52059945+oddlittlebird@users.noreply.github.com> * Applying achatterjee's suggestions Accepting the changes: * Adding in articles * Adjusting prepositions * Other changes as requests Completing this commit through the Github web interface for added speed. Co-authored-by: achatterjee-grafana <70489351+achatterjee-grafana@users.noreply.github.com> Co-authored-by: achatterjee-grafana <70489351+achatterjee-grafana@users.noreply.github.com> Co-authored-by: Diana Payton <52059945+oddlittlebird@users.noreply.github.com>
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 Yarn >= 1.22.4
Build the doc site
- On the command line, first change to the docs folder:
cd docs
. - Run
make docs-quick
. This launches a preview of the website with the current grafana docs athttp://localhost:3002/docs/grafana/next/
which will refresh automatically when changes are made to content in thesources
directory.
If you have the grafana/website repo checked out in the same directory as the grafana repo, then you can run make docs-local-static
to use local assets (such as images).
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.
Syntax is:
{{< relref "example.md" >}}
You might need to add more context for the link (containing folders and so on, folder/example.md
) if Hugo says the relref is ambiguous.
Edit the side menu
The side menu is automatically build from the file structure. Use the weight front matter parameter to order pages.
Add images
Images are currently hosted in the grafana/website repo.
Deploy changes to grafana.com
When a PR is merged to main with changes in the docs/sources
directory, those changes are automatically synced 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.