This repo houses all of the assets used to build the Buf documentation available at https://docs.buf.build.

To get started, make sure you have Node installed:

brew install node
make install

To run a local dev server, run:

make

or

make run

This command starts a local development server on localhost:3000. The dev server serves content dynamically and should pick up most changes live without having to restart the server.

To view the fully built product, you can run:

make serve

This command generates static content into the build directory and then serves the static files on localhost. This doesn't update dynamically as with make run but the content you view this way should be identical to the deployed docs.

We are using version 2.0.0-beta.3 of Docusaurus.

The project extends the capabilities of docusaurus to render code blocks:

• sh is recognized as an alias for bash and shell and enables shell script highlighting
• proto is recognized as an alias for protobuf and enables protocol buffers source highlighting
• terminal will use shell script highlighting, and:
  • strip $ from every line of code copied to the clipboard
  • allow console output following a command to be separated by a line with three dashes ---, and not copy only the part above this line to the clipboard
• adding the suffix -nocopy to any language identifier will hide the Copy button

The project extends the docusaurus sidebar with badges.

To add a badge to a category, add the property customProps as follows:

{
  "type": "category",
  "label": "Remote generation",
  "customProps": {
    "badge": {
      "label": "experimental",
      "severity": "danger"
    }
  },

To add a badge to an item, change the string id to a doc object. I.e. for "bsr/authentication":

{
  "type": "doc",
  "id": "bsr/authentication",
  "customProps": {
    "badge": {
      "label": "beta",
      "severity": "warning"
    }
  }
},

The properties label and severity are mandatory. The severity can be one of:

• danger (red badge)
• warning (yellow badge)
• neutral (gray badge)
• info (blue badge)

Note that long badge labels in combination with long item labels might cause a line break, which should be avoided for the sake of readability.

All styles live in src/css/custom.css and CSS module files in src/theme/. If a style cannot be manipulated in custom.css as required, theme components can be overridden and wrapped.

There are a few custom components that you may find useful when working on the docs:

Use this component for embedding images. Here's an example:

<Image src="/images/weird-al.png" alt="Funniest guy ever" />

Required fields are alt and src. Required fields are alt and src. Optional fields: title, width, caption.

The Buf docs support five admonition blocks:

Here's an example note block:

:::note
Here is something to keep in mind.
:::

Admonition blocks support pretty much anything available in standard Markdown:

:::note
Here is some **bold text**. Here is some `code`. Here is a [link](https://example.com).
:::

To supply a custom title:

:::danger Please don't do this
No really, we mean it
:::

The Buf documentation uses the Vale linter for its prose sources. The current Vale config is in .vale.ini and Vale-related assets are in the vale directory.

To lint the docs, install Vale and run:

vale docs

# Alternatively:
make lint

There are currently two checks in place:

• A standard spelling check. Any words that we want Vale to ignore need to be added to the accept.txt file.
• A check for e.g. and i.e.

Linting is currently performed on an ad hoc basis.

Periodically, mostly when prompted by log output from various systems, we should update the Browserslist "database" using this command:

npx browserslist@latest --update-db

This is expected to update only the package-lock.json and no other files.