Docs contributions

Guidelines for contributing to the Dapr Docs

This guide contains information about contributions to the Dapr docs repository. Please review the guidelines below before making a contribution to the Dapr docs. This guide assumes you have already reviewed the general guidance which applies to any Dapr project contributions.

Dapr docs are published to docs.dapr.io. Therefore, any contribution must ensure docs can be compiled and published correctly.

Prerequisites

The Dapr docs are built using Hugo with the Docsy theme. To verify docs are built correctly before submitting a contribution, you should setup your local environment to build and display the docs locally.

Fork the docs repository to work on any changes

Follow the instructions in the repository README.md to install Hugo locally and build the docs website.

Branch guidance

The Dapr docs handles branching differently than most code repositories. Instead of having a master or main branch, every branch is labeled to match the major and minor version of a runtime release. For the full list visit the Docs repo

Overall, all updates should go into the docs branch for the latest release of Dapr. You can find this directly at https://github.com/dapr/docs, as the latest release will be the default branch. For any docs changes that are applicable to a release candidate or a pre-release version of the docs, make your changes into that particular branch.

For example, if you are fixing a typo, adding notes, or clarifying a point, make your changes into the default Dapr branch. If you are documenting an upcoming change to a component or the runtime, make your changes to the pre-release branch. Branches can be found in the Docs repo

Style and tone

These conventions should be followed throughout all Dapr documentation to ensure a consistent experience across all docs.

  • Casing - Use upper case only at the start of a sentence or for proper nouns including names of technologies (Dapr, Redis, Kubernetes etc.).
  • Headers and titles - Headers and titles must be descriptive and clear, use sentence casing i.e. use the above casing guidance for headers and titles too
  • Use simple sentences - Easy-to-read sentences mean the reader can quickly use the guidance you share.
  • Avoid the first person - Use 2nd person “you”, “your” instead of “I”, “we”, “our”.
  • Assume a new developer audience - Some obvious steps can seem hard. E.g. Now set an environment variable Dapr to a value X. It is better to give the reader the explicit command to do this, rather than having them figure this out.
  • Use present tense - Avoid sentences like “this command will install redis”, which implies the action is in the future. Instead use “This command installs redis” which is in the present tense.

Contributing a new docs page

  • Make sure the documentation you are writing is in the correct place in the hierarchy.
  • Avoid creating new sections where possible, there is a good chance a proper place in the docs hierarchy already exists.
  • Make sure to include a complete Hugo front-matter.

Contributing a new concept doc

  • Ensure the reader can understand why they should care about this feature. What problems does it help them solve?
  • Ensure the doc references the spec for examples of using the API.
  • Ensure the spec is consistent with concept in terms of names, parameters and terminology. Update both the concept and the spec as needed.
  • Avoid just repeating the spec. The idea is to give the reader more information and background on the capability so that they can try this out. Hence provide more information and implementation details where possible.
  • Provide a link to the spec in the Reference section.
  • Where possible reference a practical How-To doc.

Contributing a new How-To guide

  • How To articles are meant to provide step-by-step practical guidance on to readers who wish to enable a feature, integrate a technology or use Dapr in a specific scenario.
  • Sub directory naming - the directory name should be descriptive and if referring to specific component or concept should begin with the relevant name. Example pubsub-namespaces.
  • Do not assume the reader is using a specific environment unless the article itself is specific to an environment. This include OS (Windows/Linux/MacOS), deployment target (Kubernetes, IoT etc.) or programming language. If instructions vary between operating systems, provide guidance for all.
  • Include code/sample/config snippets that can be easily copied and pasted.
  • At the end of the article, provide the reader with related links and next steps (this can be other relevant “how-to”, samples for reference or related concepts).

Requirements for docs.dapr.io

Any contribution must ensure not to break the website build. The way Hugo builds the website requires following the below guidance.

Files and folder names

File and folder names should be globally unique. - \service-invocation - service-invocation-overview.md

Front-matter

Front-matter is what takes regular markdown files and upgrades them into Hugo compatible docs for rendering into the nav bars and ToCs.

Every page needs a section at the top of the document like this:

  1. ---
  2. type: docs
  3. title: "TITLE FOR THE PAGE"
  4. linkTitle: "SHORT TITLE FOR THE NAV BAR"
  5. weight: (number)
  6. description: "1+ SENTENCES DESCRIBING THE ARTICLE"
  7. ---

Example

  1. ---
  2. type: docs
  3. title: "Service invocation overview"
  4. linkTitle: "Overview"
  5. weight: 10
  6. description: "A quick overview of Dapr service invocation and how to use it to invoke services within your application"
  7. ---

Weight determines the order of the pages in the left sidebar, with 0 being the top-most.

Front-matter should be completed with all fields including type, title, linkTitle, weight, and description.

  • title should be 1 sentence, no period at the end
  • linkTitle should be 1-3 words, with the exception of How-to at the front.
  • description should be 1-2 sentences on what the reader will learn, accomplish, or do in this doc.

As per the styling conventions, titles should only capitalize the first word and proper nouns, with the exception of “How-To:” - “Getting started with Dapr service invocation” - “How-To: Setup a local Redis instance”

Referencing other pages

Hugo ref and relref shortcodes are used to reference other pages and sections. It also allows the build to break if a page is incorrectly renamed or removed.

This shortcode, written inline with the rest of the markdown page, will link to the _index.md of the section/folder name:

  1. {{< ref "folder" >}}

This shortcode will link to a specific page:

  1. {{< ref "page.md" >}}

Note that all pages and folders need to have globally unique names in order for the ref shortcode to work properly. If there are duplicate names the build will break and an error will be thrown.

Referencing sections in other pages

To reference a specific section in another page, add #section-short-name to the end of your reference.

As a general rule, the section short name is the text of the section title, all lowercase, with spaces changed to “-”. You can check the section short name by visiting the website page, clicking the link icon (🔗) next to the section, and see how the URL renders in the nav bar. The content after the “#” is your section shortname.

As an example, for this specific section the complete reference to the page and section would be:

  1. {{< ref "contributing-docs.md#referencing-sections-in-other-pages" >}}

Shortcodes

The following are useful shortcodes for writing Dapr documentation

Images

The markdown spec used by Docsy and Hugo does not give an option to resize images using markdown notation. Instead, raw HTML is used.

Begin by placing images under /daprdocs/static/images with the naming convention of [page-name]-[image-name].[png|jpg|svg].

Then link to the image using:

  1. <img src="/images/[image-filename]" width=1000 alt="Description of image">

Don’t forget to set the alt attribute to keep the docs readable for our visually impaired users.

Example

This HTML will display the dapr-overview.png image on the overview.md page:

  1. <img src="/images/overview-dapr-overview.png" width=1000 alt="Overview diagram of Dapr and its building blocks">

Tabbed content

Tabs are made possible through Hugo shortcodes.

The overall format is:

  1. {{< tabs [Tab1] [Tab2]>}}
  3. {{% codetab %}}
  4. [Content for Tab1]
  5. {{% /codetab %}}
  7. {{% codetab %}}
  8. [Content for Tab2]
  9. {{% /codetab %}}
  11. {{< /tabs >}}

All content you author will be rendered to Markdown, so you can include images, code blocks, YouTube videos, and more.

Example

  1. {{< tabs Windows Linux MacOS>}}
  3. {{% codetab %}}
  4. ```powershell
  5. powershell -Command "iwr -useb https://raw.githubusercontent.com/dapr/cli/master/install/install.ps1 | iex"
  6. ```
  7. {{% /codetab %}}
  9. {{% codetab %}}
  10. ```bash
  11. wget -q https://raw.githubusercontent.com/dapr/cli/master/install/install.sh -O - | /bin/bash
  12. ```
  13. {{% /codetab %}}
  15. {{% codetab %}}
  16. ```bash
  17. brew install dapr/tap/dapr-cli
  18. ```
  19. {{% /codetab %}}
  21. {{< /tabs >}}

This example will render to this:

  1. powershell -Command "iwr -useb https://raw.githubusercontent.com/dapr/cli/master/install/install.ps1 | iex"
  1. wget -q https://raw.githubusercontent.com/dapr/cli/master/install/install.sh -O - | /bin/bash
  1. brew install dapr/tap/dapr-cli

YouTube videos

Hugo can automatically embed YouTube videos using a shortcode:

  1. {{< youtube [VIDEO ID] >}}

Example

Given the video https://youtu.be/dQw4w9WgXcQ

The shortcode would be:

  1. {{< youtube dQw4w9WgXcQ >}}

Buttons

To create a button in a webpage, use the button shortcode.

Link to an external page

  1. {{< button text="My Button" link="https://example.com" >}}

My Button

Link to another docs page

You can also reference pages in your button as well:

  1. {{< button text="My Button" page="contributing" >}}

My Button

Button colors

You can customize the colors using the Bootstrap colors:

  1. {{< button text="My Button" link="https://example.com" color="primary" >}}
  2. {{< button text="My Button" link="https://example.com" color="secondary" >}}
  3. {{< button text="My Button" link="https://example.com" color="success" >}}
  4. {{< button text="My Button" link="https://example.com" color="danger" >}}
  5. {{< button text="My Button" link="https://example.com" color="warning" >}}
  6. {{< button text="My Button" link="https://example.com" color="info" >}}

My Button My Button My Button My Button My Button My Button

References

Translations

The Dapr Docs supports adding language translations into the docs using git submodules and Hugo’s built in language support.

You can find an example PR of adding Chinese language support in PR 1286.

Steps to add a language:

  • Open an issue in the Docs repo requesting to create a new language-specific docs repo

  • Once created, create a git submodule within the docs repo:

    1. git submodule add <remote_url> translations/<language_code>

  • Add a language entry within daprdocs/config.toml:

    1.  [languages.<language_code>]
    2.    title = "Dapr Docs"
    3.    weight = 3
    4.    contentDir = "content/<language_code>"
    5.    languageName = "<language_name>"

  • Create a mount within daprdocs/config.toml:

    1. [[module.mounts]]
    2.   source = "../translations/docs-<language_code>/content/<language_code>"
    3.   target = "content"
    4.   lang = "<language_code>"

  • Repeat above step as necessary for all other translation directories

Last modified May 26, 2021: Update to point to 1.2 (#1518) (c690379)