Where to place specifications
- Create a subfolder under the
contentfolder with a short name for your specification. This folder will be used in the url, so make it lowercase, short and representative. - Create an
_index.mdfile with the full name of the specificationcontent/sample/_index.md md1 2 3--- title: "Sample Specification" ---
Front-matter tags in specifications
title: Shown before any other content in an H1 tagversion: A Semantic Versioning 2.0.0 compliant version number. Shown directly below the title in an H2 taglatest: true or false (default). Used to determine the specification shown when navigating to the specification main URL. At least one specification should be marked aslatest, usually the latest release version of the specification
content/sample/1.0.0/index.md
md
| |
Translations
- Check
hugo.tomlfile to see if the language is present in the[languages]section, else add it. - Note the language abbreviation. Lets say its
xyz - Check if
i18n/xyz.yamlis available (subsitute the language abbreviation forxyz) - Translate the content of
i18n/xyz.yamlbased oni18n/en.yaml - Locate the specification file to translate, say
content/sample/1.0.0/index.mdand copy it tocontent/sample/1.0.0/index.xyz.md(again substitute language abbreviation forxyz)