This is primarily a Jekyll site, with some tools to collect and pre-process documentation from multiple sources.
In general:
- Fork this repo
- Create a feature branch
- Submit a pull request
The site content has different sources.
Directory | Contents |
---|---|
dest | where the site is built locally |
exe | Command line tool (Thor) |
lib | Ruby code for CLI, processing docs, etc. |
site | Site content |
test | Tests for Ruby code |
The documentation for ManageIQ comes from several sources which are continuously improved. Contributions are welcome to each of these, here's where you can help:
Docs in the getting started group are part of this repo, find them under site/docs/get-started
The user reference docs are hosted at https://github.com/ManageIQ/manageiq-documentation. They are written in Asciidoc and organized in AsciiBinder By default they are built in a temp directory and copied (rsync) to /site/docs/reference/latest
.
The API Docs are hosted in the same repo as the User Reference, under the api directory
These guides describe how to work with and contribute to the source code of ManageIQ itself. They are found in this repo: https://github.com/ManageIQ/guides.
Before the Jekyll site is built, YAML front matter is added to each page of the guides, if that page does not already have it.
Currently this is included as a Git submodule.
Peter McGowan is working on a book covering the Automation features of ManageIQ. You can find the source for that book here: https://github.com/pemcg/mastering-automation-in-cloudforms-and-manageiq. However, this content is hosted on Gitbook and only linked to from the site.
$ exe/miq
miq build <all|guides|site|reference> # Build or process an aspect of the site
miq help [COMMAND] # Describe available commands or one specific command
miq reset <all|guides|site|reference> # Reset repo(s) to clean state
miq serve # Does Jekyll serve with appropriate args
miq update <all|guides|site|reference> # Pull changes from origin repos
Images (img) in documents and blog posts should be "responsive" by default, that is their width should not exceed the width of their container. Add the .large_img
class to give large images zoomability.