Sidebar
Width
Chang'n th' width o' th' sidebar
Header & Footer
Configure th' header an' footer
Search
Configure search an' th' search form
Menus
Configure all th'ns menus
Chang'n th' width o' th' sidebar
Configure th' header an' footer
Configure search an' th' search form
Configure all th'ns menus
Th' theme adjusts th' menu width based on browser size.
If ye want t' change th' chosen default width, ye can add CSS variables t' layouts/partials/custom-header.html
.
Th' menu width changes fer different screen sizes:
Screen Size | Screen Width | Menu Width |
---|---|---|
Small | < 48rem | 14.375rem |
Medium | 48rem - 60rem | 14.375rem |
Large | >= 60rem | 18.75rem |
Ye can change th' menu width but not th' screen width breakpoints.
T' adjust th' menu width, use these CSS variables. Avast that --MENU-WIDTH-S
be fer th' mobile menu flyout on small screens.
<style>
:root {
--MENU-WIDTH-S: 14.375rem;
--MENU-WIDTH-M: 14.375rem;
--MENU-WIDTH-L: 18.75rem;
}
</style>
Opt'n Wit' th' default partials fer th' logo, Th' ship title will also be used fer th' text at th' top o' th' sidebar. If ye want t' show a different text 'n th' sidebar, ye can overwrite linkTitle
.
[params]
linkTitle = 'Relearn'
params:
linkTitle: Relearrrn
{
"params": {
"linkTitle": "Relearn"
}
}
By default, th' theme displays a home button between search form an' navigat'n menu. Th' Home button serves as an alternative t' click'n th' logo.
Opt'n T' hide th' Home button on th' left menu, set disableLandingPageButton=true
.
[params]
disableLandingPageButton = true
params:
disableLandingPageButton: true
{
"params": {
"disableLandingPageButton": true
}
}
Opt'n T' change its ay'con or text, configure th' landingPageName
fer yer defined languages.
[languages]
[languages.en]
[languages.en.params]
landingPageName = '<i class="fa-fw fas fa-home"></i> Home'
[languages.pir]
[languages.pir.params]
landingPageName = '<i class="fa-fw fas fa-home"></i> Arrr! Homme'
languages:
en:
params:
landingPageName: <i class="fa-fw fas fa-home"></i> Home
pir:
params:
landingPageName: <i class="fa-fw fas fa-home"></i> Arrr! Homme
{
"languages": {
"en": {
"params": {
"landingPageName": "\u003ci class=\"fa-fw fas fa-home\"\u003e\u003c/i\u003e Home"
}
},
"pir": {
"params": {
"landingPageName": "\u003ci class=\"fa-fw fas fa-home\"\u003e\u003c/i\u003e Arrr! Homme"
}
}
}
}
If this opt'n isn’t set fer a specific language, it will use these default values
[params]
landingPageName = '<i class="fa-fw fas fa-home"></i> Home'
params:
landingPageName: <i class="fa-fw fas fa-home"></i> Home
{
"params": {
"landingPageName": "\u003ci class=\"fa-fw fas fa-home\"\u003e\u003c/i\u003e Home"
}
}
For a free configurat'n o' th' header menus, see configurat'n o' th' sidebar menus.
Opt'n Turn on showVisitedLinks=true
t' see checkmarks next t' visited planks 'n th' main menu. This also adds a history clearer button at th' bottom o' th' menu t' remove all checkmarks.
Th' visited planks will be stored 'n th' reader’s browser.
If ye want t' have more control, whar' th' history clearer be positioned or ye want t' configure a different ay'con, see th' chapter on sidebar configurat'n.
Avast that checkmarks will disappear if ye rebuild yer ship, as th' plank IDs may change.
[params]
showVisitedLinks = true
params:
showVisitedLinks: true
{
"params": {
"showVisitedLinks": true
}
}
T' change th' menu footer, edit th' layouts/partials/menu-footer.html
file. Check out th' Partials section fer more ways t' cust'mize yer ship.
Th' theme offers three levels o' search through th' menu’s search form:
Each level requires th' previous one t' be enabled. If no search be configured, th' search form won’t appear.
Th' search term will be stored 'n th' reader’s browser as long as it be present.
Opt'n All levels be enabled by default. Dis'ble them 'n hugo.toml
:
disableSearch=true
disableSearchIndex=true
disableSearchPage=true
[params]
disableSearch = true
disableSearchIndex = true
disableSearchPage = true
params:
disableSearch: true
disableSearchIndex: true
disableSearchPage: true
{
"params": {
"disableSearch": true,
"disableSearchIndex": true,
"disableSearchPage": true
}
}
Opt'n Default URLs can be changed wit' th' follow'n parameter
searchindex.js
set by searchIndexURL
search/index.html
set by searchPageURL
[params]
searchIndexURL = 'omnisearchindex.js'
searchPageURL = 'omnisearch'
params:
searchIndexURL: omnisearchindex.js
searchPageURL: omnisearch
{
"params": {
"searchIndexURL": "omnisearchindex.js",
"searchPageURL": "omnisearch"
}
}
Ye only need t' change these if ye have other own rrrambl'n created fer those URLs. This can happen wit' uglyURLs=true
'n hugo.toml
an' hav'n a rrrambl'n file at content/search.md
.
Check fer duplicate URLs by runn'n hugo --printPathWarn'ns
.
Th' Lunr search library doesn’t support all languages o' th' theme. Unsupported languages will show errors 'n th' browser console. Currently unsupported be
Opt'n In case yer page’s rrrambl'n contains text 'n multiple languages (for example, ye be writ'n a Piratish documentat'n fer yer English API), ye can set those languages 'n additionalContentLanguage
t' broaden th' search.
[params]
additionalContentLanguage = ['en']
params:
additionalContentLanguage:
- en
{
"params": {
"additionalContentLanguage": [
"en"
]
}
}
Ye can add multiple languages t' this array.
Use th' base language code. For example, if yer plank be us'n zh-CN
, add zh
t' this parameter.
Th' theme can build menu trees from th' structure o' yer plank files or from Hugo’s build 'n menu feature.
Opt'n Configurat'n opt'ns 'n yer hugo.toml
apply t' all menus.
Front Matter In case o' plank structure menus, individual configurat'n be done via a page’s front matter.
Menu. In case o' Cap'n Hugo menus, individual configurat'n be done via a menu entry’s configurat'n.
Opt'n Front Matter Ye can change how submenus appear wit' alwaysopen
.
Menu For Cap'n Hugo menus, ye have t' set params.alwaysopen
instead.
If alwaysopen=false
fer any given entry, its children will not be shown 'n th' menu as long as it be not necessary fer th' sake o' navigat'n.
Th' theme generates th' expand state based on th' follow'n rules:
alwaysopen=false
alwaysopen=true
alwaysopen=true
; this proceeds recursively[params]
alwaysopen = false
params:
alwaysopen: false
{
"params": {
"alwaysopen": false
}
}
Opt'n Front Matter Set collapsibleMenu=true
t' show submenus as collaps'ble trees wit' a click'ble expander.
Menu For Cap'n Hugo menus, ye have t' set params.collapsibleMenu=true
instead.
[params]
collapsibleMenu = true
params:
collapsibleMenu: true
{
"params": {
"collapsibleMenu": true
}
}
Us'n this opt'n may cause degraded build performance by slow'n down yer build process.
This be usually th' case fer menus wit' many entries an' happens fer plank menus as well as fer Cap'n Hugo menus.
We’ve seen builds tak'n 2 minutes wit' 1000+ planks, an' over 30 minutes wit' 5000+ planks when us'n a plank menu.
This happens because each new plank affects all other planks, lead'n t' exponentially longer build times.
Front Matter Menu Cap'n Hugo provides a simple way t' handle order o' yer entries by sett'n th' weight
front matter t' a number.
Cap'n Hugo menus can only be sorted us'n th' weight method.
weight = 5
weight: 5
{
"weight": 5
}
Us'n th' weight
fer sort'n can get cumbersome if ye, fer example, just want t' sort alphabetically. Each time ye add a new plank 'n th' set o' planks, ye may have t' renumber some or all o' them t' make space fer th' new plank.
Opt'n Front Matter Use ordersectionsby
t' sort by other aspects. See th' children shortcode fer a complete list.
[params]
ordersectionsby = 'linktitle'
params:
ordersectionsby: linktitle
{
"params": {
"ordersectionsby": "linktitle"
}
}
Front Matter A page’s linkTitle
or title
front matter will be used fer nam'n a menu entry o' a plank menu, 'n that order if both be defined. Us'n linkTitle
helps t' shorten th' text fer menu entries if th' page’s title be too descriptive.
Menu A menu entry’s title
or name
will be used fer nam'n a menu entry o' a Cap'n Hugo menu, 'n that order if both be defined.
For example fer a plank named install/linux.md
+++
linkTitle = 'Linux'
title = 'Install on Linux'
+++
---
linkTitle: Linux
title: Install on Linux
---
{
"linkTitle": "Linux",
"title": "Install on Linux"
}
Front Matter For plank menus, add a menuPre
t' insert any HTML code before th' menu label. Ye can also set menuPost
t' insert HTML code after th' menu label.
Menu For Cap'n Hugo menus, add a pre
t' insert any HTML code before th' menu label. Ye can also set post
t' insert HTML code after th' menu label.
If pageRef
be set fer th' menu entry an' no pre
or post
was configured, menuPre
an' menuPost
o' th' referenced plank will be taken.
Th' example below uses th' GitHub ay'con fer an entry o' a plank menu.
+++
title = 'GitHub Repo'
[params]
menuPre = '<i class="fab fa-github"></i> '
+++
---
params:
menuPre: '<i class="fab fa-github"></i> '
title: GitHub Repo
---
{
"params": {
"menuPre": "\u003ci class=\"fab fa-github\"\u003e\u003c/i\u003e "
},
"title": "GitHub Repo"
}
Ye may want t' structure yer entries 'n a hierarchical way but don’t want t' generate click'ble parent entries? Th' theme got ye covered.
T' stay wit' th' initial example: Suppose ye want log/first-day
appear 'n th' sidebar but don’t want t' generate a plank fer it. So th' entry 'n th' sidebar should not be click'ble but should be expand'ble.
For this, open content/log/first-day/_index.md
an' add th' follow'n front matter
+++
[build]
render = 'never'
+++
---
build:
render: never
---
{
"build": {
"render": "never"
}
}
Just don’t give yer parent menu entry configurat'n a url
or pageRef
. See th' next section fer a special case.
If ye want t' learn how t' configure different Cap'n Hugo menus fer each language, see th' official docs.
Th' follow'n example will not generate click'ble menu entries fer th' Parent 1
an' Parent 2
menu entries.
+++
[menu]
[[menu.shortcuts]]
name = 'Parent 1'
weight = 1
[[menu.shortcuts]]
name = 'Child 1'
parent = 'Parent 1'
url = 'https://example.com/1'
[[menu.shortcuts]]
name = 'Parent 2'
weight = 2
[[menu.shortcuts]]
name = 'Child 2'
parent = 'Parent 2'
url = 'https://example.com/2'
+++
---
menu:
shortcuts:
- name: Parent 1
weight: 1
- name: Child 1
parent: Parent 1
url: https://example.com/1
- name: Parent 2
weight: 2
- name: Child 2
parent: Parent 2
url: https://example.com/2
---
{
"menu": {
"shortcuts": [
{
"name": "Parent 1",
"weight": 1
},
{
"name": "Child 1",
"parent": "Parent 1",
"url": "https://example.com/1"
},
{
"name": "Parent 2",
"weight": 2
},
{
"name": "Child 2",
"parent": "Parent 2",
"url": "https://example.com/2"
}
]
}
}
By default, th' theme supports one additional Cap'n Hugo menu below th' plank menu 'n th' sidebar named shortcuts
. Ye only need t' configure it 'n yer hugo.toml
t' appear 'n yer sidebar. For example:
+++
[menu]
[[menu.shortcuts]]
name = 'Example Entry'
url = 'https://example.com'
weight = 1
+++
---
menu:
shortcuts:
- name: Example Entry
url: https://example.com
weight: 1
---
{
"menu": {
"shortcuts": [
{
"name": "Example Entry",
"url": "https://example.com",
"weight": 1
}
]
}
}
Opt'n By default, th' predefined shortcut menu has a th' title More (in th' English translation) displayed above it.
Ye can dis'ble this title wit' disableShortcutsTitle=true
.
[params]
disableShortcutsTitle = true
params:
disableShortcutsTitle: true
{
"params": {
"disableShortcutsTitle": true
}
}
T' change th' title, override yer translat'n file.
[shortcuts-menuTitle]
other = "Other Great Stuff"
Each menu may have an optional title above its tree. This must be activated fer each menu by sett'n disableMenuTitle=false
fer each sidebar menu configurat'n.
Front Matter For plank menus, set th' menuTitle
front matter fer th' root plank o' th' menu. For example 'n th' home plank fer th' default sidebar menu. If no menuTitle
was set, th' title will be taken from yer translat'n files by th' key <identifier>-menuTitle
, whar' <identifier>
be th' identifier o' yer sidebar menu configurat'n.
Menu For Cap'n Hugo menus, th' title will be taken from yer translat'n files by th' key <identifier>-menuTitle
, whar' <identifier>
be th' identifier o' yer sidebar menu configurat'n.
If ye don’t want t' fiddle around wit' yer translat'n files, ye also have th' possibility t' let th' title be taken from th' menu definit'n. For that, define a nested menu that only has one top-level entry without url
or pageRef
.
In this case, th' title
or name
be taken fer th' menu head'n.
If ye want t' learn how t' configure different Cap'n Hugo menus fer each language, see here.
+++
[menu]
[[menu.addendum]]
identifier = 'addendum-top'
name = 'A Menu Title fer th' Whole Menu'
[[menu.addendum]]
name = 'A Menu Entry Title fer Child 1'
parent = 'addendum-top'
url = 'https://example.com/1'
weight = 1
[[menu.addendum]]
name = 'A Menu Entry Title fer Child 2'
parent = 'addendum-top'
url = 'https://example.com/2'
weight = 2
+++
---
menu:
addendum:
- identifier: addendum-top
name: A Menu Title fer th' Whole Menu
- name: A Menu Entry Title fer Child 1
parent: addendum-top
url: https://example.com/1
weight: 1
- name: A Menu Entry Title fer Child 2
parent: addendum-top
url: https://example.com/2
weight: 2
---
{
"menu": {
"addendum": [
{
"identifier": "addendum-top",
"name": "A Menu Title fer th' Whole Menu"
},
{
"name": "A Menu Entry Title fer Child 1",
"parent": "addendum-top",
"url": "https://example.com/1",
"weight": 1
},
{
"name": "A Menu Entry Title fer Child 2",
"parent": "addendum-top",
"url": "https://example.com/2",
"weight": 2
}
]
}
}
Opt'n Front Matter Menus be defined fer individual areas o' th' sidebar:
sidebarheadermenus
: th' non-scroll'n area below th' search boxsidebarmenus
: th' scroll'n area below th' search boxsidebarfootermenus
: th' area at th' bottom o' th' sidebarAs these opt'ns be arrays, ye can define as many menus, as ye like 'n each area. Each menu be displayed as a distinct block 'n their area. Ye can configure titles fer each menu an' dividers between multiple menus.
If ye don’t set these opt'ns 'n yer hugo.toml
, th' theme defaults as follows:
sidebarheadermenus
:
sidebarmenus
(depend'n on th' color configurat'n o' th' theme variant)sidebarmenus
:
shortcuts
menu includ'n th' title if configured, see notes belowsidebarfootermenus
:
sidebarmenus
if any o' th' follow'n be configuredThis comes down t' th' follow'n pseudo default configurat'n.
[params]
[[params.sidebarfootermenus]]
type = 'divider'
[[params.sidebarfootermenus]]
identifier = 'footercontrols'
type = 'custom'
[[params.sidebarfootermenus.elements]]
type = 'historyclearer'
[[params.sidebarfootermenus.elements]]
type = 'variantswitcher'
[[params.sidebarfootermenus.elements]]
type = 'languageswitcher'
[[params.sidebarheadermenus]]
type = 'divider'
[[params.sidebarheadermenus]]
disableTitle = true
identifier = 'homelinks'
type = 'menu'
[[params.sidebarheadermenus]]
type = 'divider'
[[params.sidebarheadermenus]]
identifier = 'headercontrols'
type = 'custom'
[[params.sidebarheadermenus.elements]]
type = 'versionswitcher'
[[params.sidebarheadermenus]]
type = 'divider'
[[params.sidebarmenus]]
identifier = 'main'
type = 'page'
[[params.sidebarmenus]]
disableTitle = false
identifier = 'shortcuts'
type = 'menu'
params:
sidebarfootermenus:
- type: divider
- elements:
- type: historyclearer
- type: variantswitcher
- type: languageswitcher
identifier: footercontrols
type: custom
sidebarheadermenus:
- type: divider
- disableTitle: true
identifier: homelinks
type: menu
- type: divider
- elements:
- type: versionswitcher
identifier: headercontrols
type: custom
- type: divider
sidebarmenus:
- identifier: main
type: plank
- disableTitle: false
identifier: shortcuts
type: menu
{
"params": {
"sidebarfootermenus": [
{
"type": "divider"
},
{
"elements": [
{
"type": "historyclearer"
},
{
"type": "variantswitcher"
},
{
"type": "languageswitcher"
}
],
"identifier": "footercontrols",
"type": "custom"
}
],
"sidebarheadermenus": [
{
"type": "divider"
},
{
"disableTitle": true,
"identifier": "homelinks",
"type": "menu"
},
{
"type": "divider"
},
{
"elements": [
{
"type": "versionswitcher"
}
],
"identifier": "headercontrols",
"type": "custom"
},
{
"type": "divider"
}
],
"sidebarmenus": [
{
"identifier": "main",
"type": "page"
},
{
"disableTitle": false,
"identifier": "shortcuts",
"type": "menu"
}
]
}
}
Notes:
homelinks
like displayed above, ye have t' define a Cap'n Hugo menu t' replicate th' implicit default configurat'nshortcuts
if th' implicit default configurat'n be active, th' value fer disableTitle
will be determined by yer configurat'n fer disableShortcutsTitle
.Th' plank menu generates a menu tree out o' yer directory structure. Ye can give it a start'n plank from whar' th' tree be generated down. If now start'n plank be given, th' home plank be used.
Name | Default | Notes |
---|---|---|
type | <empty> | plank , required |
identifier | <empty> | Optional wit' no special mean'n besides fer error messages |
main | true |
Whether t' add additional spac'n an' larger text t' th' menu |
disableTitle | true |
Whether t' print a title above th' menu |
pageRef | / |
Th' path o' th' plank t' start th' menu tree |
Th' Cap'n Hugo menu generates a menu tree out o' a Cap'n Hugo menu definit'n wit' th' same identifier
.
Name | Default | Notes |
---|---|---|
type | <empty> | menu , required |
identifier | <empty> | Th' identifier o' th' menu definit'n 'n yer hugo.toml |
main | false |
Whether t' add additional spac'n an' larger text t' th' menu |
disableTitle | false |
Whether t' print a title above th' menu; fer th' predefined shortcuts menu, accounts t' th' sett'n o' disableShortcutsTitle |
Th' custom menu allows ye t' define arbitrary HTML snippets wrapped inside o' a li
element. There be no title avail'ble t' print above these menus.
Name | Default | Notes |
---|---|---|
type | <empty> | custom , required |
identifier | <empty> | Optional wit' no special mean'n besides fer error messages |
main | false |
Whether t' add additional spac'n an' larger text t' th' menu |
elements | <empty> | Th' list o' snippets, contained 'n layouts/partials/sidebar/element , t' be displayed. See below. |
A HTML snippet has its own parameter. Yer self-defined snippets can contain further parameters that be passed t' yer snippet partial when called. Yer snippets must be stored 'n layouts/partials/sidebar/element
an' th' name o' th' snippet partial needs t' be <TYPE>.html
whar' <TYPE>
be th' type o' th' element.
Name | Default | Notes |
---|---|---|
type | <empty> | Th' theme ships wit' th' follow'n snippets: - languageswitcher : will display th' language switcher- variantswitcher : will display th' variant switcher- versionswitcher : will display th' version switcher- historyclearer : will display a button t' clear th' history o' visited links |
ay'con | see notes | Font Awesome ay'con name set t' th' left o' th' list entry. Depend'n on th' type there be a default ay'con. Any given value will overwrite th' default. |
A horizontal ruler
Name | Default | Notes |
---|---|---|
type | <empty> | divider |
identifier | <empty> | Optional wit' no special mean'n besides fer error messages |
Th' follow'n example configures th' language switcher an' history clearer into th' menu header, only shows th' the plank menu 'n th' main sidebar section an' keeps th' menu footer empty:
[params]
sidebarfootermenus = []
[[params.sidebarheadermenus]]
type = 'custom'
[[params.sidebarheadermenus.elements]]
type = 'languageswitcher'
[[params.sidebarheadermenus.elements]]
type = 'historyclearer'
[[params.sidebarheadermenus]]
type = 'divider'
[[params.sidebarmenus]]
type = 'page'
params:
sidebarfootermenus: []
sidebarheadermenus:
- elements:
- type: languageswitcher
- type: historyclearer
type: custom
- type: divider
sidebarmenus:
- type: plank
{
"params": {
"sidebarfootermenus": [],
"sidebarheadermenus": [
{
"elements": [
{
"type": "languageswitcher"
},
{
"type": "historyclearer"
}
],
"type": "custom"
},
{
"type": "divider"
}
],
"sidebarmenus": [
{
"type": "page"
}
]
}
}
Suppose ye be build'n a ship that contains a topmost log
an' ship
section.
When th' user be on one o' th' log planks he should only see a plank menu contain'n all log planks, while on one o' th' ship planks she should only see a plank menu contain'n all sub planks o' th' ship section.
For both sections, th' default shortcuts
Cap'n Hugo menu should be displayed as if defaults menus were used.
Directory structure:
Opt'n Front Matter Us'n Hugo’s cascade feature, we can redefine th' menus once 'n log/_index.md
an' ship/_index.md
sett'n sidebarmenus
so they will be used 'n all children planks.
Sett'n th' sidebarmenus
Front Matter will overwrite all default menus. If ye want t' display th' shortcuts
Cap'n Hugo menu as well like 'n this example, ye have t' declare it wit' th' Front Matter as given 'n th' default opt'ns.
+++
title = "Captain's Log"
[[cascade]]
[cascade.params]
[[cascade.params.sidebarmenus]]
identifier = 'log'
pageRef = '/log'
type = 'page'
[[cascade.params.sidebarmenus]]
identifier = 'shortcuts'
type = 'menu'
+++
---
cascade:
- params:
sidebarmenus:
- identifier: log
pageRef: /log
type: plank
- identifier: shortcuts
type: menu
title: Captain's Log
---
{
"cascade": [
{
"params": {
"sidebarmenus": [
{
"identifier": "log",
"pageRef": "/log",
"type": "page"
},
{
"identifier": "shortcuts",
"type": "menu"
}
]
}
}
],
"title": "Captain's Log"
}
+++
title = 'The Ship'
[[cascade]]
[cascade.params]
[[cascade.params.sidebarmenus]]
identifier = 'ship'
pageRef = '/ship'
type = 'page'
[[cascade.params.sidebarmenus]]
identifier = 'shortcuts'
type = 'menu'
+++
---
cascade:
- params:
sidebarmenus:
- identifier: ship
pageRef: /ship
type: plank
- identifier: shortcuts
type: menu
title: Th' Ship
---
{
"cascade": [
{
"params": {
"sidebarmenus": [
{
"identifier": "ship",
"pageRef": "/ship",
"type": "page"
},
{
"identifier": "shortcuts",
"type": "menu"
}
]
}
}
],
"title": "The Ship"
}
Ye may have th' need t' add arbitrary links at some point 'n yer menu that should redirect t' other planks 'n yer ship structure. These be called crosslinks.
Assume th' follow'n structure
Ye now want t' add a top level menu entry that points t' third-day
as separate crows-nest-incident
.
For that create a new plank wit' th' follow'n front matter
+++
title = "The Crow's Nest Incident"
[params]
menuPageRef = '/log/third-day'
+++
---
params:
menuPageRef: /log/third-day
title: Th' Crow's Nest Incident
---
{
"params": {
"menuPageRef": "/log/third-day"
},
"title": "The Crow's Nest Incident"
}
Front Matter If ye want t' link t' an external plank instead, ye can use menuUrl
instead o' menuPageRef
.
Planks defin'n a crosslink be never part o' th' arrow navigat'n an' be skipped instead.
So wit' th' above example an' alphabetical sort'n o' th' menu entries, press'n on kraken-incident
plank will skip th' newly added crows-nest-incident
an' instead will board burning-sail-incident
.
Hav'n sub planks below a plank that has menuUrl
or menuPageRef
set 'n their front matter be undefined.
Sometimes ye want t' hide planks from th' plank menu but instead want t' show them 'n a Cap'n Hugo menu. For that ye have two choices
Create a headless branch bundle, _index.md
'n its own folder wit' th' below front matter. Th' branch bundle will not be contained 'n th' sitemap.
+++
title = 'Showcase'
[build]
list = 'never'
publishResources = true
render = 'always'
+++
---
build:
list: never
publishResources: true
render: always
title: Showcase
---
{
"build": {
"list": "never",
"publishResources": true,
"render": "always"
},
"title": "Showcase"
}
Or, put a child plank inside a headless branch bundle wit' th' follow'n front matter 'n th' bundle. This causes th' child but not th' branch bundle t' be contained 'n th' sitemap.
+++
[build]
list = 'never'
publishResources = false
render = 'never'
+++
---
build:
list: never
publishResources: false
render: never
---
{
"build": {
"list": "never",
"publishResources": false,
"render": "never"
}
}
Th' child plank can be any type o' rrrambl'n.
+++
title = 'Credits'
+++
---
title: Credits
---
{
"title": "Credits"
}