This repository contains the official source of the CF metadata conventions.
The source files are built into HTML automatically when changes are merged into this repository.
The latest build of the specification is held in the gh-pages
branch and can be seen here.
For the official web site please visit: https://cfconventions.org and the corresponding GitHub organisation.
The CF Conventions are changed by changing the source files in this repository. The rules for doing this are set forth on the CF website. Their implementation in GitHub is described in this repository's CONTRIBUTING.md file.
The following steps outline how to build the CF Conventions documentation into HTML and/or PDF format using AsciiDoc:
- Ensure you have Ruby installed. (e.g.
sudo apt install ruby
) - Ensure you have a recent version of Asciidoctor installed (e.g.
gem install asciidoctor
) - Ensure you have Make installed. (e.g.
sudo apt install make
) - Clone the repository containing the AsciiDoc files. (e.g.
git clone git@github.com:cf-convention/cf-conventions.git
) - There are different options to make the conventions and conformance documents:
- (Default: Build all formats) HTML and PDF conventions and conformance documents:
make
ormake all
- HTML conventions and conformance documents:
make html
- PDF conventions and conformance documents:
make pdf
- Conventions documents (HTML and PDF):
make conventions
- Conformance documents (HTML and PDF):
make conformance
- Remove built documents and clean build directories:
make clean
- Build with the FINAL tag and a date stamp. Ensure you have manually updated the version in the
version.adoc
file before running this command:make CF_FINAL=True
- (Default: Build all formats) HTML and PDF conventions and conformance documents:
Both HTML documents will have images embedded within .html
file.
The built documents will be rendered in the build
directory with the resulting paths:
build/cf-conventions.html
build/cf-conventions.pdf
build/conformance.html
build/conformance.pdf
Ensure the built documents meet your requirements before publishing.
See the GitHub help pages and many other git/GitHub guides for more details on how to work with repos, forks, pull requests, etc.
Whenever a pull request is merged, a travis-ci build generates the latest specification draft and adds it to the gh-pages branch here. The gh-pages branch is deployed to github pages at the following documents:
- https://cfconventions.org/cf-conventions/cf-conventions.html
- https://cfconventions.org/cf-conventions/cf-conventions.pdf
- https://cfconventions.org/cf-conventions/conformance.html
- https://cfconventions.org/cf-conventions/conformance.pdf
These documents are linked in the cf-conventions web site. source here which is published to: https://cfconventions.org/. The latest spec documents are linked from those web pages here: https://cfconventions.org/latest.html.