Newsletter
Join the Community
Subscribe to our newsletter for the latest news and updates
Legacy API documentation template for Jekyll with three-column layout, full-text search, and CloudCannon-optimized editing.
Aviator is a legacy API documentation template for Jekyll, created by CloudCannon, that generates a responsive three-column documentation site with full-text search and auto-generated navigation.
Aviator is an API documentation template built on Jekyll 3.7.2 by CloudCannon, the company behind the CloudCannon Academy Jekyll tutorials. It takes documentation pages organized into Jekyll collections and outputs a static website with a three-column layout, full-text search, and navigation automatically generated from collection categories. The repository explicitly labels the template as legacy and no longer maintained, but it remains functional and deployable either locally or through CloudCannon.
excluded_in_search: true to front matter.position_number field controlling content order.bundle exec jekyll serve workflows.position_number in the collection configuration inside _config.yml.position_number in each document's front matter to determine the order pages appear within a collection.excluded_in_search: true to a page's front matter to keep it out of search results.Aviator runs as a standard Jekyll site. After adding site and author details to _config.yml, you start the site locally with bundle exec jekyll serve or connect the repository to CloudCannon for a hosted workflow. The template reads Jekyll collections, applies the position_number ordering, and outputs a static site with the pre-styled three-column layout.
No. The repository description marks Aviator as a legacy template that is no longer maintained. It can still be used as a starting point, but there will be no official updates or support.
Add excluded_in_search: true to the page's front matter. This per-page flag removes the document from the site's full-text search index.
Set the position_number field in the front matter of each document. The order of collections themselves is controlled by a position_number field set in the collection configuration in _config.yml.
