Kristi Nikolla 86b1b7ff11 Attempt at fixing broken docs
This patch attempts to fix the broken docs by having the series
name match the branch name (2023.1 instead of 2023.1.antelope)

A patch was previously merged and reverted[0]. It changed the
name of the series, but missed updating the directory names
under the www directory.

I did test this locally, and it did correctly pupulate the pages
with links for the various projects, but I do not know if it
fully resolves the issue.

Additionally adds redirects for /2023.1.antelope to /2023.1
and 2023.2.bobcat to 2023.2.

[0]. https://review.opendev.org/c/openstack/openstack-manuals/+/880060

Change-Id: I39e0740e57502fd96299fea79409e55e49c10367
2023-05-16 19:41:16 +00:00
2023-05-16 19:41:16 +00:00
2023-05-16 19:41:16 +00:00
2019-04-19 19:41:34 +00:00
2020-06-18 13:13:12 +02:00
2022-11-07 11:01:36 +01:00
2021-05-26 19:23:31 +02:00
2019-08-16 16:19:56 +02:00
2023-01-04 20:01:46 +01:00

Team and repository tags

image

OpenStack Manuals

This repository contains documentation for the OpenStack project.

For more details, see the OpenStack Documentation Contributor Guide.

It includes these manuals:

  • Architecture Design Guide
  • Documentation Contributor Guide
  • High Availability Guide
  • Installation Guide
  • Virtual Machine Image Guide

In addition to the guides, this repository contains:

  • docs.openstack.org contents: www

Building

Various manuals are in subdirectories of the doc/ directory.

Guides

Some pre-requisites are needed to build the guides. If you are using a Linux operating system you can generate a report of missing local requirements with the bindep command:

$ tox -e bindep

All guides are in the RST format. You can use tox to prepare virtual environment and build all guides (HTML only):

$ tox -e docs

You can also build a specific guide.

For example, to build OpenStack Virtual Machine Image Guide, use the following command:

$ tox -e build -- image-guide

You can find the root of the generated HTML documentation at:

doc/image-guide/build/html/index.html

To build a specific guide with a PDF file, add a -pdf option like:

$ tox -e build -- image-guide --pdf

The generated PDF file will be copied to the root directory of the generated HTML documentation.

PDF builds are accomplished using LaTeX as an intermediate format. Currently, you can generate a PDF file for a limited number of guides. The supported list is maintained in the tools/build-all-rst.sh file.

If you get the error message make: xelatex: No such file or directory, it means your local environment does not have LaTeX installed. Read Getting LaTeX and Install dependencies for building documentation for instructions.

Testing of changes and building of all manuals

Install the Python tox package and run tox from the top-level directory to use the same tests that are done as part of the OpenStack CI jobs.

If you like to run individual tests, run:

  • tox -e publishdocs - to actually build the manual; this also generates a directory publish-docs that contains the built files for inspection
  • tox -e publishlang - to build translated manuals
  • tox -e linters - to run the niceness tests, for example, to see extra whitespaces
  • tox -e linkcheck - to run the tests for working remote URLs

The tox command uses the openstack-doc-tools package to run the tests.

Generated files

Some documentation files are generated using tools. These files include a do not edit header and should not be modified by hand. Please see Generated files.

Bugs

Bugs should be filed on Launchpad, not GitHub:

https://bugs.launchpad.net/openstack-manuals

Release Notes

https://docs.openstack.org/releasenotes/openstack-manuals

Installing

Refer to https://docs.openstack.org to see where these documents are published and to learn more about the OpenStack project.

Description
OpenStack Manuals
Readme 476 MiB
Languages
HTML 78.4%
CSS 12.2%
Python 4.8%
JavaScript 3.3%
Shell 1.3%