The repository uses Antora Playbooks to locally or remotely build the AsciiDoc content into a static website.
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.
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
Run the git command to clone this repository.
git clone https://github.com/rancher/fleet-product-docs.git
This playbook repository uses a git submodule to get the custom Antora supplemental files that provide a custom GUI theme for the documentation website. Run the command below to get the submodule.
git submodule update --init
Open a terminal at the root of the git repository. Run the command below.
npm install
As a local example, run the command below to build the site:
npx antora --fetch fleet-local-playbook.yml
Navigate to the ./build/site
directory and open the index.html file in your browser to view and navigate the documentation site.
Alternatively, run the below command first and then open http://127.0.0.1:8080/
in your browser for a web server preview:
make preview
The command provided in the previous section fetches documentation content of the products from their respective remote GitHub repositories. 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.
As an example, run the command below to use the local fleet-local-playbook.yml
file.
npx antora --fetch fleet-local-playbook.yml
The Makefile can also be used to set up your environment, build the local and remote static site, and clean your build output directory.
It is recommended to report the issue via the SUSE Customer Center
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.