This site uses Hugo. In Hugo, content organization is a core concept.
Note: Hugo Tip: Start Hugo withhugo server --navigateToChanged
for content edit-sessions.
The documentation side menu, the documentation page browser etc. are listed using Hugo’s default sort order, which sorts by weight (from 1), date (newest first), and finally by the link title.
Given that, if you want to move a page or a section up, set a weight in the page’s front matter:
title: My Page
weight: 10
Note: For page weights, it can be smart not to use 1, 2, 3 …, but some other interval, say 10, 20, 30… This allows you to insert pages where you want later.
The Documentation
main menu is built from the sections below docs/
with the main_menu
flag set in front matter of the _index.md
section content file:
main_menu: true
Note that the link title is fetched from the page’s linkTitle
, so if you want it to be something different than the title, change it in the content file:
main_menu: true
title: Page Title
linkTitle: Title used in links
Note: The above needs to be done per language. If you don’t see your section in the menu, it is probably because it is not identified as a section by Hugo. Create a_index.md
content file in the section folder.
The documentation side-bar menu is built from the current section tree starting below docs/
.
It will show all sections and their pages.
If you don’t want to list a section or page, set the toc_hide
flag to true
in front matter:
toc_hide: true
When you navigate to a section that has content, the specific section or page (e.g. _index.md
) is shown. Else, the first page inside that section is shown.
The page browser on the documentation home page is built using all the sections and pages that are directly below the docs section
.
If you don’t want to list a section or page, set the toc_hide
flag to true
in front matter:
toc_hide: true
The site links in the top-right menu – and also in the footer – are built by page-lookups. This is to make sure that the page actually exists. So, if the case-studies
section does not exist in a site (language), it will not be linked to.
In addition to standalone content pages (Markdown files), Hugo supports Page Bundles.
One example is Custom Hugo Shortcodes. It is considered a leaf bundle
. Everything below the directory, including the index.md
, will be part of the bundle. This also includes page-relative links, images that can be processed etc.:
en/docs/home/contribute/includes
├── example1.md
├── example2.md
├── index.md
└── podtemplate.json
Another widely used example is the includes
bundle. It sets headless: true
in front matter, which means that it does not get its own URL. It is only used in other pages.
en/includes
├── default-storage-class-prereqs.md
├── federated-task-tutorial-prereqs.md
├── federation-content-moved.md
├── index.md
├── partner-script.js
├── partner-style.css
├── task-tutorial-prereqs.md
├── user-guide-content-moved.md
└── user-guide-migration-notice.md
Some important notes to the files in the bundles:
Resources
and you can provide metadata per language, such as parameters and title, even if it does not supports front matter (YAML files etc.). See Page Resources Metadata..RelPermalink
of a Resource
is page-relative. See Permalinks.The SASS
source of the stylesheets for this site is stored below src/sass
and can be built with make sass
(note that Hugo will get SASS
support soon, see https://github.com/gohugoio/hugo/issues/4243).
Was this page helpful?
Thanks for the feedback. If you have a specific, answerable question about how to use Kubernetes, ask it on Stack Overflow. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement.