Skip to main content

Writing syntax

This guide explains how to write Pulsar documentation using the MDX-compatible Markdown syntax.


The Pulsar documentation uses Markdown as its markup language and Docusaurus for generating the documentation and website, with MDX enhancement.

Why use new Markdown syntax?

The new Pulsar website is upgraded to Docusaurus V2, which uses MDX as the parsing engine. MDX can do much more than just parsing standard Markdown syntax, like rendering React components inside your documents as well.

How to test doc changes?

You can play with the MDX format in the MDX Playground. Write some MDX to find out what it turns into. You can see the rendered result, the generated code, and the intermediary ASTs. This can be helpful for debugging or exploring.

For how to test doc changes locally, read the Content Preview Guide.


This guide just highlights a few selected important rules and frequently used syntax. For the complete syntax guide, read the Markdown Features document from Docusaurus and Markdown document from MDX.


  • Use Markdown rather than HTML as much as possible, or else MDX may not recognize it. For example, when constructing complex tables, do not use <table>.
  • Use closing tags. <li><li/> and <br/> are especially useful for constructing complex tables, such as creating a list and adding a blank line.

Example 1

| Directory | Contains                            |
| **Hello** | <li>a</li><li>b</li><br/><li>c</li> |
  • a
  • b

  • c
  • Example 2

    | a   | b   | c                        |
    | aa | bb | cc1<br/>cc2<br/><br/>cc3 |



    Before using multiple tabs, add these imports at the beginning of the file:

    import Tabs from '@theme/Tabs';
    import TabItem from '@theme/TabItem';

    Then, you can write tabs as:

    <TabItem value="apple" label="Apple" default>
    This is an apple 🍎
    <TabItem value="orange" label="Orange">
    This is an orange 🍊
    <TabItem value="banana" label="Banana">
    This is a banana 🍌
    This is an apple 🍎

    Read more about how to write multiple tabs at Tabs.

    Code blocks

    Read more about how to use syntax highlighting and supported languages at Syntax highlighting.


    Docusaurus supports these admonitions:


    Some **content** with _Markdown_ `syntax`.



    Some **content** with _Markdown_ `syntax`.



    Some **content** with _Markdown_ `syntax`.



    Some **content** with _Markdown_ `syntax`.



    Some **content** with _Markdown_ `syntax`.


    Some content with Markdown syntax.


    Some content with Markdown syntax.


    Some content with Markdown syntax.


    Some content with Markdown syntax.


    Some content with Markdown syntax.

    Read more about how to write admonitions at Admonitions.


    Static assets are hosted under /assets for all documentations:

    ![Page Linking](/assets/page-linking.png)

    Indentation and space

    • Use the same indentation for running texts and code blocks.
    • For the content block after an ordered list, indent the content block by only 3 spaces (not 4 spaces).
    • For the content block after an unordered list, indent the content block by only 2 spaces.
    • Insert exact one empty line (not two empty lines or more) between code blocks and running texts.

    If you don't insert the empty line, the text cannot be rendered properly. You should encounter an error by preview.


    If you create a new .md file, add quotes for the value of sidebar_label.

    id: admin-api-partitioned-topics
    title: Managing partitioned topic
    sidebar_label: "Partitioned topics"

    If you don't set the sidebar_label property, the label is default to title.


    To help tables be easier to maintain, consider adding additional spaces to the column widths to make them consistent. For examples:

    | App name | Description         | Requirements   |
    | :------- | :------------------ | :------------- |
    | App 1 | Description text 1. | Requirements 1 |
    | App 2 | Description text 2. | None |

    To format tables easily, you can install a plugin or extension in your editor as below:

    Use links instead of summarizing to help preserve a single source of truth in Pulsar documentation.

    Headings generate anchor links when rendered. For example:

    ## This is an example generates the anchor #this-is-an-example.

    • Avoid cross-reference docs to headings unless you need to link to a specific section of the document. This avoids breaking anchors in the future in case the heading is changed.
    • If possible, avoid changing headings, because they're not only linked internally. There are various links to Pulsar documentation on the Internet, such as tutorials, presentations, StackOverflow posts, and other sources.

    Internal refers to documentation in the same Pulsar project.

    General rules:

    • Use relative links rather than absolute URLs.
    • Do not prepend ./ or ../../ to links to files or directories.


    Cross-reference to other markdown file (/path/xx/ is not needed)[Function overview](
  • [Function overview](functions-overview)
  • [Function overview](
  • [Function overview](../../
  • Cross-reference to other chapters in the same markdown file (# and - are needed)[Install builtin connectors (optional)](#install-builtin-connectors-optional)N/A

    Read more about how to write Markdown links at Markdown links.

    When describing interactions with external software, it's often helpful to include links to external documentation. When possible, make sure that you're linking to an authoritative source.

    For example, if you're describing a feature in Microsoft's Active Directory, include a link to the official Microsoft documentation.

    Use a permalink when linking to a specific line in a file to ensure users land on the line you're referring to though lines of code change over time.


    Authoritative sources

    When citing external information, use sources that are written by the people who created the item or product in question. These sources are the most likely to be accurate and remain up to date.

    • ✅ Authoritative sources include the following:

      • Official documentation for a product.

        For example, if you're setting up an interface with the Google OAuth 2 authorization server, include a link to Google's documentation.

      • Official documentation for a project.

        For example, if you're citing NodeJS functionality, refer directly to NodeJS documentation.

      • Books from an authoritative publisher.

    • ❌ Authoritative sources do not include the following:

      • Personal blog posts.
      • Documentation from a company that describes another company's product.
      • Non-trustworthy articles.
      • Discussions on forums such as Stack Overflow.

    While many of these sources to avoid can help you learn skills and or features, they can become obsolete quickly. Nobody is obliged to maintain any of these sites. Therefore, you should avoid using them as reference literature.

    Non-authoritative sources are acceptable only if there is no equivalent authoritative source. Even then, focus on non-authoritative sources that are extensively cited or peer-reviewed.


    Escape < and > with back-quote or HTML escape characters.


    • Each documentation page begins with a level 2 heading (##). This becomes the <h1> element when the page is rendered to HTML.
    • Do not skip a level.
    • Leave one blank line before and after the heading.
    • Do not use links as part of heading text.
    • When you change the heading text, the anchor link changes. To avoid broken links:
      • Do not use step numbers in headings.
      • When possible, do not use words that might change in the future.