This documentation is for airshipcms.io. You can also view it, along with additional illustrations and better navigation, at airshipcms.io/documentation/view/introduction.

• Introduction-to-Airship.md
• Quickstart-Guide.md
• Schema-Setup-Guide.md
• Development-Guide.md
• Project-Directory.md
• Boilerplates-and-Examples.md
• How-Airship-CLI-Works.md
• Install-Airship-CLI-Tools.md
• Airship-CLI-Commands.md
• Airship-CLI-Troubleshooting.md
• Using-Layouts-and-Templates.md
• Layouts.md
• Page-Templates.md
• Collection-Templates.md
• Collection-Index-Template.md
• Collection-Show-Template.md
• Collection-Categories-Template.md
• Collection-Category-Template.md
• Airmail-Email-Templates.md
• Airmail-Public-Make-Template.md
• Page-Properties.md
• Collection-Item-Properties.md
• Datafields.md
• Related-Items.md
• Propeller-Helpers.md
• Partials.md
• Content-Blocks.md
• HandlebarsJS.md
• Introduction-to-Airship-API.md
• Introduction-to-Airship-CMS.md
• Schema-and-Data-Model.md
• Pages.md
• Collections.md
• Categories.md
• Relationships.md
• Users.md
• Making-Your-Site-Live.md

Conventions for /properties examples:

If a property is specific to a certain template, notate it as [template--property_name], e.g. [categories--has_categories]

Properties notated as single or each are general exapmles that are usable among various templates.

When creating in AirshipCMS:

the field notation should be just the notations listed in repo pages, e.g. [categories--has_categories]

the permalink should match the notation

the property_name should be just the property name, without the notation, e.g. has_categories