48a16b0b4b
The deprecated badge (which should really be called version banner or something, given that it's not really a "badge" and appears for non-deprecated releases too) is a simple div with some text, a close button, and a Bootstrap dropdowns [1] to switch between versions. This div has three classes, 'deprecated-badge', 'fixed', and 'deprecated-badge-X', where 'X' is the series status (i.e. 'deprecated-badge-current'). We were setting the background color of the div using the '.deprecated-badge' selector and then overriding this using the version-specific class selector. This background color was inherited by the dropdown. This had the end result of giving a unique color to the overall div for different releases but the dropdown, which wasn't being overridden on a per-version basis, stayed the same, yielding a consistent blue dropdown regardless of the background. We fix this by setting the background-color attributes on the dropdown buttons explicitly, removing the background-color from the 'deprecated-badge' class. While we're at it, we also fix the text color for the main div, so that we're not trying to read dark blue text on a dark red background. [1] https://getbootstrap.com/docs/4.0/components/dropdowns/ Change-Id: I8dbf54ff90164b2c2945ba74fee4bcf51eaecabb Signed-off-by: Stephen Finucane <sfinucan@redhat.com> |
||
---|---|---|
doc | ||
playbooks/build-manuals-tox | ||
releasenotes/source | ||
tools | ||
www | ||
.gitignore | ||
.gitreview | ||
.pydevproject | ||
.zuul.yaml | ||
CONTRIBUTING.rst | ||
LICENSE | ||
README.rst | ||
bindep.txt | ||
doc-tools-check-languages.conf | ||
projects.txt | ||
test-requirements.txt | ||
tox.ini |
README.rst
Team and repository tags
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 checkbuild
- to actually build the manual; this also generates a directorypublish-docs
that contains the built files for inspectiontox -e checklang
- to build translated manualstox -e linters
- to run the niceness tests, for example, to see extra whitespacestox -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.