##Rackspace doc templates
Use these templates to create developer and user documentation that is compatible with the Rackspace documentation build and deploy platform.
###Sphinx templates
Documentation is authored and built locally using the Sphinx documentation generator with source files in restructured text format.
User Guide template
Sphinx documentation projects to create a User Guide for a Rackspace service or product offering, or for a group of related products and services, or for a subset of a product's features.
-
Audience: Service consumers who want to use the product, group of products, or product feature, or who want to decide whether the product is suitable for their use case.
-
Contents: Multi-page HTML content architecture for several types of User Guides:
- product-family to introduce a group of related products
- product-plus-prereqs to introduce a product and its supporting cast
- single-product to introduce one product
- product-feature to introduce one feature of one product
Developer Guide template
Sphinx documentation project to create a Developer Guide for a a service API like the Cloud CDN API documentation.
-
Audience: Application developers, operations, advanced users who want to use API services by submitting API requests from the command line or by using CLI technologies.
-
Contents: A single-page HTML content architecture with the following sections:
- Developer Guide
- Getting Started with the API (cURL or CLI)
- API Reference
- Release Notes
Release Notes template
-
Release Notes published within a Developer Guide follow the Release Notes portion of the Developer Guide template.
-
Release Notes published as a standalone document follow the standalone Release Notes template.
###Jekyll templates
The Rackspace build and deploy platform also supports Jekyll projects for other types of documentation content. For sample projects, see the following repositories:
##Build and deploy Sphinx project
You can build deliverables based on these templates using any of the following options:
-
Local builds with default Sphinx template. Use the Sphinx build make utility to get output rendered with the default Sphinx templates and interface.
-
Local preview with Rackspace branding and UX. Install and use the Deconst local client.
-
For server builds and production deployment, contact the Developer documentation team for information on build integration options and how to wire content into the Docs landing page on developer.rackspace.com.
Required resources for production builds
-
_deconst.json
file that defines the contentID for the project. (Example: Cloud Files _deconst.json) -
build configuration script (Example: Cloud files cibuild)
-
Build integration script for Travis or another CI tool. (Example: Cloud Files Travis yml script)
-
Configure content and routes in the Control Repository config directory. This step also specifies the templates to apply to the content.
-
Update the docs landing page to add new content. (Source: docs-quickstart repo)
-
####Docbook templates (Deprecated)
Documentation is authored and build locally using DocBook, Oxygen editor, and the maven Jenkins tool chain.
You can install DocBook templates by using the Python project in the DocBook folder to create the DocBook source and build files for authoring and delivering the content. The project provides resources for a full set of Rackspace API service documentation including a Getting Started Guide, Release Notes, and Developer Guide.
The resulting project can be built and deployed to docs.rackspace.com or docs-internal.rackspace.com.