Go to file
Billy Tat f8ded00fb2
Merge pull request #191 from rancher/dependabot/submodules/product-docs-common-abe50ce
Bump product-docs-common from `a14d458` to `abe50ce`
2025-10-23 07:58:19 -07:00
.github Revert "Don't deploy to GitHub pages" 2025-09-05 11:13:46 -07:00
dsc-style-bundle@58597dae23 Bump dsc-style-bundle from `92cf9c0` to `58597da` 2025-10-17 11:27:16 +00:00
product-docs-common@abe50cebe1 Bump product-docs-common from `a14d458` to `abe50ce` 2025-10-23 11:15:10 +00:00
.gitignore Add zh search dependency + other small refinements 2024-09-10 15:18:06 -07:00
.gitmodules Bump dsc style package for shared header. 2025-09-24 17:17:32 +02:00
CODEOWNERS Add CODEOWNERS file 2024-08-30 16:36:24 -07:00
CONTRIBUTING.md added README.md and CONTRIBUTING.md files 2024-09-10 13:10:47 -07:00
Makefile Use npm ci for consistent builds 2024-12-16 09:56:02 -08:00
README.md Use npm ci in README 2024-12-16 11:08:28 -08:00
articles-listing.conf updating after review 2025-10-20 15:44:47 -07:00
package-lock.json Bump sha.js from 2.4.11 to 2.4.12 2025-09-01 14:41:21 +00:00
package.json Change to the dsc style package and use antora 3.1.10 2025-02-03 17:04:49 +01:00
product-docs-playbook-local.yml correct stackstate versions 2025-10-10 09:44:48 +02:00
product-docs-playbook-remote.yml added latest in the remote playbook 2025-10-13 16:30:15 +05:30

README.md

Antora Playbook for SUSE Rancher Product Docs

The repository is for the Antora playbook, which combines and generates the Product Documentation for SUSE Rancher's portfolio. The playbook combines documentation from the below listed repositories.

rancher/rancher-product-docs

rancher/harvester-product-docs

rancher/longhorn-product-docs

rancher/rke2-product-docs

rancher/k3s-product-docs

rancher/neuvector-product-docs

rancher/turtles-product-docs

rancher/fleet-product-docs

rancher/elemental-product-docs

rancher/kubewarden-product-docs

rancher/product-docs-playbook

Build the Documentation site

The repository uses Antora Playbook to combine and build the AsciiDoc content from multiple GitHub repositories into a static website.

Prerequisites

git

You need git to get the source code of this repository. Run the command below to check whether git is installed on your machine.

git --version

If you don't have git installed on your machine, download and install it for your operating system from the git downloads page.

Node.js

Antora requires an active long term support (LTS) release of Node.js. Run the command below to check if you have Node.js installed, and which version. This command should return an active Node.js LTS version number

node -v

If you don't have Node.js installed on your machine, install it, preferably via nvm

Clone the Playbook repository

Run the git command to clone this repository.

git clone https://github.com/rancher/product-docs-playbook.git

This playbook repository uses a git submodule to get the custom Antora supplemental files that provide custom GUI theme for the documentation website. Run the command below to get the submodule.

git submodule update --init

Install node modules

Open a terminal at the root of the git repository. Run the command below.

npm ci

Run Antora to build the static website

Run the command below.

npx antora --fetch product-docs-playbook-remote.yml

Navigate to the ./build/site directory and open the index.html file in your browser to view and navigate the documentation site.

Run Antora to build the static website using the local documentation content

The command provided in the previous section fetches documentation content of the products from thier respective remote GitHub respositories. If you want the playbook to use the documentation content from your local machine instead you can do so with product-docs-playbook-local.yml.

Clone all the individual product documentation Github repositories one level above the current playbook repository.

Run the command below to use the product-docs-playbook-local.yml file.

npx antora --fetch product-docs-playbook-local.yml

If you are a SUSE Rancher Customer

It is recommended to report the issue via. the SUSE Customer Center

If you are a SUSE Internal Employee

It is recommended to file a Jira ticket. If you do not have access to Jira then you can file a GitHub ticket on the respective product documentation repository.