@redpanda-data/docs-extensions-and-macros

= Antora Extensions and Macros for Redpanda Docs :url-org: https://github.com/redpanda-data :url-project: {url-org}/docs-extensions-and-macros :url-playbook: {url-org}/docs-site :url-git: https://git-scm.com :url-git-dl: {url-git}/downloads :url-nodejs: https://nodejs.org :url-nodejs-releases: https://github.com/nodejs/Release#release-schedule :url-nvm-install: {url-nvm}#installation :idprefix: :idseparator: - ifdef::env-github[] :important-caption: :exclamation: :note-caption: :paperclip: endif::[] :toc: :toc-title: Contents

toc::[]

This library provides https://docs.antora.org/antora/latest/extend/extensions/[Antora extensions] and https://docs.asciidoctor.org/asciidoctor.js/latest/extend/extensions/register/[Asciidoc macros] developed for Redpanda documentation.

== Prerequisites

To use this library, you must have {url-nodejs}[Node.js] 16 or higher installed on your machine.

[,bash]

node --version

If this command fails with an error, you don't have Node.js installed.

When you have Node.js installed, use the following command to install the antora-extensions-and-macros package in your project:

[,bash]

npm i @redpanda-data/docs-extensions-and-macros

To use the development version, refer to the <<development-quickstart,Development Quickstart>>.

== Antora Extensions

This section documents the Antora extensions provided by this library and how to configure them.

IMPORTANT: Ensure you register each extension under the antora.extensions key in the playbook, not the asciidoc.extensions key.

=== Algolia indexer

This extension generates an Algolia index for each version of each component. The index entries are then saved to Algolia using the saveObjects() method, and also saved as JSON files in the site catalog. JSON files are published to the site root using the template algolia-<component>-<version>.json.

NOTE: Only pages that include an <article> element with the doc class are indexed.

==== Environment variables

• ALGOLIA_ADMIN_API_KEY (required)
• ALGOLIA_APP_ID (required)
• ALGOLIA_INDEX_NAME (required)

==== Configuration options

The extension accepts the following configuration options:

excludes (optional):: Any elements, classes, or IDs that you want to exclude from the index. index-latest-only (optional):: Whether to index all versions or just the latest version of a component.

==== Registration example

antora:
  extensions:
  - require: '@redpanda-data/docs-extensions-and-macros/extensions/algolia-indexer/index'
    excludes: ['.thumbs','script', '.page-versions','.feedback-section','.banner-container']
    index-latest-only: true

=== Component category aggregator

This extension maps Redpanda Connect component data into a structured format:

• Maps original component names to common names.
• Populates connectCategoriesData and flatComponentsData attributes.
• Skips deprecated components.

==== Environment variables

This extension does not require any environment variables.

==== Configuration options

There are no configurable options for this extension.

==== Registration Example

antora:
  extensions:
    - require: '@redpanda-data/docs-extensions-and-macros/extensions/generate-rp-connect-categories'

=== Redpanda Connect tag modifier

This extension updates the playbook to use the latest release tag for the Redpanda Connect documentation. It ensures that the Redpanda Connect documentation is always pulled from the latest release tag available on GitHub.

==== Environment variables

• REDPANDA_GITHUB_TOKEN (optional): A Personal access token (PAT) that has repo permissions for the redpanda-data GitHub organization.

NOTE: If you don't set the environment variable, the latest version of Redpanda Connect may not be fetched. When the environment variable is not set, the extension sends unauthenticated requests to GitHub. Unauthenticated requests may result in hitting the API rate limit and cause GitHub to reject the request. In this case the fallback version is used. This version is defined in the playbook where the extension is registered.

==== Configuration options

There are no configurable options for this extension.

==== Registration Example

antora:
  extensions:
    - require: '@redpanda-data/docs-extensions-and-macros/extensions/modify-connect-tag-playbook'

=== Version fetcher

This extension fetches the latest release versions from GitHub.

The following attributes are available to all versions of all Antora components:

latest-console-version: The latest release version of Redpanda Console. latest-connect-version: The latest release version of Redpanda Connect. redpanda-beta-version: The latest RC version of Redpanda. redpanda-beta-commit: The commit hash for the latest RC version of Redpanda.

The following attributes are available to the latest version of the ROOT component (Redpanda docs):

full-version: The latest release version of Redpanda. latest-release-commit: The commit hash for the latest release version of Redpanda. latest-operator-version: The latest release version of the Redpanda Operator. latest-redpanda-helm-chart-version: The latest release version of the Redpanda Helm chart.

==== Environment variables

• REDPANDA_GITHUB_TOKEN (optional): A Personal access token (PAT) that has repo permissions for the redpanda-data GitHub organization.

NOTE: If you don't set the environment variable, the latest versions may not be fetched. When the environment variable is not set, the extension sends unauthenticated requests to GitHub. Unauthenticated requests may result in hitting the API rate limit and cause GitHub to reject the request.

==== Registration example

antora:
  extensions:
  - '@redpanda-data/docs-extensions-and-macros/extensions/version-fetcher/set-latest-version'

=== Validate attributes

This extension ensures the consistency and validity of page attributes, focusing on validating page categories against a predefined list of valid categories and subcategories. It automatically adds missing parent categories for any specified subcategories and removes any specified categories that are invalid. Additionally, it processes specific environment attributes, setting corresponding page-level attributes when environment conditions are met.

==== Environment variables

This extension does not require any environment variables.

==== Configuration options

There are no configurable options for this extension. It operates based on site attributes defined in add-global-attributes.js to determine valid categories and subcategories.

==== Registration example

Register the validate-attributes extension in the Antora playbook under the antora.extensions key like so:

[source,yaml]

antora: extensions: - require: '@redpanda-data/docs-extensions-and-macros/extensions/validate-attributes.js'

=== Related docs

This extension enhances the connectivity between lab exercises and relevant documentation by dynamically identifying and linking related documentation pages and other lab exercises based on shared categories and deployment types.

==== Environment variables

This extension operates without requiring any specific environment variables.

==== Configuration options

This extension does not offer configurable options. It uses the inherent attributes of pages to determine relationships based on page-categories and deployment types (env-kubernetes, env-linux, env-docker, page-cloud).

==== Registration example

To integrate the related-docs-extension into your Antora playbook, add it under the antora.extensions key as demonstrated below:

[source,yaml]

antora: extensions: - require: '@redpanda-data/docs-extensions-and-macros/extensions/related-docs-extension.js'

=== Related labs

This extension enriches documentation pages with links to related lab exercises, facilitating a deeper understanding of the content through practical application. It dynamically assigns related labs to each documentation page based on shared categories and deployment types.

==== Environment variables

This extension does not require any environment variables.

==== Configuration options

The extension operates without explicit configuration options. It automatically processes documentation pages to identify and link related labs based on shared page-categories attributes and deployment types (env-kubernetes, env-linux, env-docker, page-cloud).

==== Registration example

Include the related-labs-extension in the Antora playbook under the antora.extensions key as follows:

[source,yaml]

antora: extensions: - require: '@redpanda-data/docs-extensions-and-macros/extensions/related-labs-extension.js'

=== Global attributes

This extension collects Asciidoc attributes from the {url-playbook}[shared component] or a local YAML file and makes them available to all component versions. Having global attributes is useful for consistent configuration of local and production builds.

==== Environment variables

This extension does not require any environment variables.

==== Configuration options

The extension accepts the following configuration options:

attributespath (optional):: Specifies the path to a local YAML file that contains global attributes. If this is provided, the extension will load attributes from this file first. If this path is not provided or no valid attributes are found in the file, the extension will fall back to loading attributes from the shared component.

==== Registration example

antora:
  extensions:
  - require: '@redpanda-data/docs-extensions-and-macros/extensions/add-global-attributes'
    attributespath: './local-attributes.yml'

In this example, the attributespath option points to a local YAML file (./local-attributes.yml), which contains the global attributes. The extension will load attributes from this file first before falling back to the shared component.

=== Produce redirects (customization of core Antora)

This extension replaces the default https://gitlab.com/antora/antora/-/tree/v3.1.x/packages/redirect-producer[`produceRedirects()` function] in Antora to handle redirect loops caused by https://docs.antora.org/antora/latest/page/page-aliases/[page aliases]. Normally, page aliases in Antora are used to resolve outdated links without causing issues. However, with https://docs.antora.org/antora/latest/playbook/urls-html-extension-style/#html-extension-style-key[`indexify`], the same URL may inadvertently be used for both the source and target of a redirect, leading to loops. This problem is https://antora.zulipchat.com/#narrow/stream/282400-users/topic/Redirect.20Loop.20Issue.20with.20Page.20Renaming.20and.20Indexify/near/433691700[recognized as a bug] in core Antora. For example, creating a page alias for modules/manage/security/authorization.adoc to point to modules/manage/security/authorization/index.adoc' can lead to a redirect loop where manage/security/authorization/points tomanage/security/authorization/. Furthermore, omitting the alias would lead to xref not found` errors because Antora relies on the alias to resolve the old xrefs. This extension is necessary until such behaviors are natively supported or fixed in Antora core.

==== Environment variables

This extension does not require any environment variables.

==== Configuration options

There are no configurable options for this extension.

==== Registration example

antora:
  extensions:
  - '@redpanda-data/docs-extensions-and-macros/extensions/modify-redirects'

=== Replace attributes in attachments

This extension replaces AsciiDoc attribute placeholders with their respective values in attachment files, such as CSS, HTML, and YAML.

[IMPORTANT]

• This extension processes attachments only if the component version includes the attribute replace-attributes-in-attachments: true.
• The @ character is removed from attribute values to prevent potential issues with CSS or HTML syntax.
• If the same attribute placeholder is used multiple times within a file, all instances will be replaced with the attribute's value. ====

==== Environment variables

This extension does not require any environment variables.

==== Configuration options

There are no configurable options for this extension.

==== Registration example

antora:
  extensions:
  - '@redpanda-data/docs-extensions-and-macros/extensions/replace-attributes-in-attachments'

=== Aggregate terms

This extension aggregates all term pages from the {url-playbook}[shared component] and does the following:

• Makes all term-name, hover-text, and link attributes available to the <<glossterm-macro,glossterm macro>>.
• Looks for glossary pages named reference:glossary.adoc in all versions of all components and appends the contents of each term file to the glossary in alphabetical order.
• If a glossary page is found, sets the glossary-page attribute of the <<glossterm, glossterm macro>> to reference:glossary.adoc so that terms can be linked to the glossary page.

==== Environment variables

This extension does not require any environment variables.

==== Configuration options

The extension accepts the following configuration options:

termspath (optional):: Specifies the path to a local directory containing term files (in .adoc format). If this path is provided, the extension will attempt to load terms from this directory first. If this path is not provided or no valid terms are found in the specified directory, the extension will fall back to loading terms from the shared component.

Term files should follow the following structure:

:category: Documentation
:hover-text: This is a description of the term.
:link: https://example.com

== Term Title

This is the detailed description of the term.

==== Registration example

antora:
  extensions:
  - require: '@redpanda-data/docs-extensions-and-macros/extensions/aggregate-terms'
    termspath: './local-terms/'

In this example, the termspath option points to a local directory (./local-terms/), where the term files are stored. The extension will load terms from this directory first before falling back to the shared component.

=== Unlisted pages

This extension identifies and logs any pages that aren't listed in the navigation (nav) file of each version of each component. It then optionally adds these unlisted pages to the end of the navigation tree under a configurable heading.

IMPORTANT: By default, this extension excludes components named 'api'. This behavior is hardcoded and cannot be changed in the configuration.

==== Environment variables

This extension does not require any environment variables.

==== Configuration options

This extension accepts the following configuration options:

addToNavigation (optional):: Whether to add unlisted pages to the navigation. The default is false (unlisted pages are not added).

unlistedPagesHeading (optional):: The heading under which to list the unlisted pages in the navigation. The default is 'Unlisted Pages'.

==== Registration example

antora:
  extensions:
  - require: '@redpanda-data/docs-extensions-and-macros/extensions/unlisted-pages'
    addToNavigation: true
    unlistedPagesHeading: 'Additional Resources'

== Asciidoc Extensions

This section documents the Asciidoc extensions that are provided by this library and how to configure them.

IMPORTANT: Be sure to register each extension under the asciidoc.extensions key in the playbook, not the antora.extensions key.

=== Add line numbers and highlights

This extension adds the necessary classes to make line numbers and line highlighting work with Prism.js.

==== Registration example

antora:
  extensions:
  - '@redpanda-data/docs-extensions-and-macros/asciidoc-extensions/add-line-numbers-highlights'

== Macros

This section documents the Asciidoc macros that are provided by this library and how to configure them.

IMPORTANT: Be sure to register each extension under the asciidoc.extensions key in the playbook, not the antora.extensions key.

=== config_ref

This inline macro is used to generate a reference to a configuration value in the Redpanda documentation. The macro's parameters allow for control over the generated reference's format and the type of output produced.

==== Usage

The config_ref macro is used in an AsciiDoc document as follows:

[,asciidoc]

config_ref:configRef,isLink,path[]

The config_ref macro takes three parameters:

configRef:: This is the configuration reference, which is also used to generate the anchor link if isLink is true.

isLink:: Whether the output should be a link. If isLink is set to true, the output will be a cross-reference (xref) to the relevant configuration value.

path:: This is the path to the document where the configuration value is defined. This parameter is used to to generate the link if isLink is true.

IMPORTANT: The path must be the name of a document at the root of the reference module.

NOTE: The config_ref macro is environment-aware. It checks if the document it is being used in is part of a Kubernetes environment by checking if the env-kubernetes attribute is set in the document's attributes. Depending on this check, it either prepends storage.tieredConfig. to the configRef or just uses the configRef as is.

For example:

[,asciidoc]

config_ref:example_config,true,tunable-properties[]

==== Registration example

[,yaml]

asciidoc: extensions: - '@redpanda-data/docs-extensions-and-macros/macros/config-ref'

=== glossterm

The glossterm inline macro provides a way to define and reference glossary terms in your AsciiDoc documents.

NOTE: This macro is a customized version of https://gitlab.com/djencks/asciidoctor-glossary[`asciidoctor-glossary`].

==== Usage

Use the glossterm inline macro to reference a term within the text of the document:

[,asciidoc]

glossterm:my term[myDefinition]

It takes two parameters:

term:: The term to be defined.

definition (optional):: The definition of the term. If the term is defined in the {url-playbook}[shared component] or the local-terms object of the antora.yml file, you can omit the definition as it will always be replaced by those definitions.

==== Configuration options

glossary-log-terms (optional):: Whether to log a textual representation of a definition list item to the console.

glossary-term-role (optional):: Role to assign each term. By default, glossary terms are assigned the glossary-term role, which gives them the class glossary-term in generated html.

glossary-links (optional):: Whether to generate links to glossary entries. By default, links to the glossary entries are generated from the glossary terms. To avoid this, set the attribute to false as either asciidoctor configuration or a header attribute.

glossary-page (optional):: Target page for glossary links. By default, links are generated to the same page as the glossary term. To specify the target page, set this attribute to the resource ID of a page where the glossary block macro is used.

glossary-tooltip (optional):: Whether to enable tooltips for the defined terms. Valid values are:

• title: This uses the browser built-in title attribute to display the definition.

• true: This inserts the definition as the value of the attribute data-glossary-tooltip.

• data-​: This inserts the definition as the value of the supplied attribute name, which must start with data.

The last two options are intended to support js/css tooltip solutions such as tippy.js.

==== Registration example

[,yaml]

asciidoc: extensions: - '@redpanda-data/docs-extensions-and-macros/macros/glossary'

=== helm_ref

This is an inline macro to create links to a Helm values.yaml file on ArtifactHub.

==== Usage

In an AsciiDoc document, use the helm_ref macro as follows:

[,asciidoc]

helm_ref:[]

Where <helmRef> is the Helm configuration value you want to reference in the values.yaml file.

For example:

Given a Helm reference value of myConfigValue, you would use the macro like this:

[,asciidoc]

helm_ref:myConfigValue[]

This will generate the following output:

[,asciidoc]

For default values and documentation for configuration options, see the https://artifacthub.io/packages/helm/redpanda-data/redpanda?modal=values&path=myConfigValue[values.yaml] file.

If you do not specify a Helm reference value, the macro generates a link without specifying a path.

==== Registration example

[,yaml]

asciidoc: extensions: - '@redpanda-data/docs-extensions-and-macros/macros/helm-ref'

=== components_by_category

This macro generates a tabbed interface to display Redpanda Connect components by category.

The categories are fetched from the connectCategoriesData that's generated in the <> extension.

==== Usage

components_by_category::[<type>]

==== Registration example

asciidoc:
  extensions:
    - '@redpanda-data/docs-extensions-and-macros/macros/rp-connect-components'

=== component_table

This macro generates a searchable table of all Redpanda Connect components with filters for support and type.

The types are fetched from the flatComponentsData that's generated in the <> extension.

==== Usage

component_table::[]

==== Registration example

asciidoc:
  extensions:
    - '@redpanda-data/docs-extensions-and-macros/macros/rp-connect-components'

=== component_type_dropdown

This macro generates a dropdown of other supported types for a particular component, allowing users to switch between different types.

The types are fetched from the flatComponentsData that's generated in the <> extension.

==== Usage

component_type_dropdown::[]

==== Registration example

asciidoc:
  extensions:
    - '@redpanda-data/docs-extensions-and-macros/macros/rp-connect-components'

== Development quickstart

This section provides information on how to develop this project.

=== Prerequisites

To build this project, you need the following software installed on your computer:

• {url-git}[git] (command: git)
• {url-nodejs}[Node.js] (commands: node, npm, and npx)

==== git

Make sure you have git installed.

[,bash]

git --version

If not, {url-git-dl}[download and install] the git package for your system.

==== Node.js

Make sure that you have Node.js installed (which also provides npm and npx).

[,bash]

node --version

If this command fails with an error, you don't have Node.js installed.

Now that you have git and Node.js installed, you're ready to start developing on this project.

=== Clone the project

Clone the project using git:

[,bash,subs=attributes+]

git clone {url-project}

Change into the project directory and stay in this directory when running all subsequent commands.

=== Install dependencies

Use npm to install the project's dependencies inside the project. In your terminal, run the following command:

[,bash]

npm ci

This command installs the dependencies listed in package-lock.json into the node_modules/ directory inside the project. This directory should not be committed to the source control repository.

=== Use your local project

If you want to use the project locally before it is published, you can specify the path to the extensions in the local-antora-playbook.yml file.

[,yaml]

asciidoc: attributes: extensions:

• '/docs-extensions-and-macros/extensions/'

---