To get started, make sure you have node installed:

brew install node
make install

To run a local dev server, simply run:

make

or

make run

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

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 will not update dynamically, but it will 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 best usability.

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.