Hinode logo
  • About 
  • Docs 
  • Components 
  • Guides 
  • Releases 
  •  
Docs
  • Getting Started
    • Introduction
    • Commands
    • Hosting and Deployment
    • Upgrading
    • Private Modules and Packages
    • Contribute
    • Troubleshooting
  • Content
    • Content Management
    • Content Organization
    • Typography
    • Links and Cross-References
    • Images and Figures
    • Tables
    • Icons
  • Configuration
    • Layout
    • Colors
    • Color Modes
    • Fonts
    • Languages
    • Navigation
    • Documentation
    • Analytics
    • Modules
    • Cookie Consent
    • Digital Asset Managers
  • Components
    • Abbr
    • Accordion
    • Alert
    • Animation
    • Args
    • Badge
    • Breadcrumb
    • Button
    • Button Group
    • Card
    • Card Group
    • Carousel
    • Collapse
    • Command Prompt
    • Docs
    • Example
    • File
    • Icon
    • Image
    • Ins
    • Kbd
    • Link
    • Map
    • Mark
    • Navbar
    • Navs and Tabs
    • Persona
    • Release
    • Spinner
    • Sub
    • Sup
    • Table
    • Timeline
    • Toast
    • Tooltip
    • Video
  • Advanced Settings
    • Overview
    • Styles
    • Scripts
    • Icons
    • Partial Development
    • Module Development
    • Server Headers
    • Server-Side Redirection
  • About
    • Credits
    • License
  • Getting Started
    • Introduction
    • Commands
    • Hosting and Deployment
    • Upgrading
    • Private Modules and Packages
    • Contribute
    • Troubleshooting
  • Content
    • Content Management
    • Content Organization
    • Typography
    • Links and Cross-References
    • Images and Figures
    • Tables
    • Icons
  • Configuration
    • Layout
    • Colors
    • Color Modes
    • Fonts
    • Languages
    • Navigation
    • Documentation
    • Analytics
    • Modules
    • Cookie Consent
    • Digital Asset Managers
  • Components
    • Abbr
    • Accordion
    • Alert
    • Animation
    • Args
    • Badge
    • Breadcrumb
    • Button
    • Button Group
    • Card
    • Card Group
    • Carousel
    • Collapse
    • Command Prompt
    • Docs
    • Example
    • File
    • Icon
    • Image
    • Ins
    • Kbd
    • Link
    • Map
    • Mark
    • Navbar
    • Navs and Tabs
    • Persona
    • Release
    • Spinner
    • Sub
    • Sup
    • Table
    • Timeline
    • Toast
    • Tooltip
    • Video
  • Advanced Settings
    • Overview
    • Styles
    • Scripts
    • Icons
    • Partial Development
    • Module Development
    • Server Headers
    • Server-Side Redirection
  • About
    • Credits
    • License

Layout

Share via
Hinode
Link copied to clipboard

Hinode uses a grid-based, responsive design for the home page, single pages and list pages.

On this page
Base Layout   Example   Configuration   Home Page   Example   Configuration   List Pages   Example   Configuration   Single Pages   Default Layout   Documentation Layout   Minimal Layout   Configuration   Page Sections   Card Layout   List Layout   Nav Layout   Configuration  

Hinode uses Bootstrap’s Grid System  and Breakpoints  to create a responsive layout across devices or viewport sizes. All pages follow the same base layout, which includes headers and footers. The next paragraphs explain the layout styles in more detail.

Base Layout  

The base layout defines a page skeleton of which all other pages are derived. It consists of four major sections, being a header, body, social footer, and bottom footer. It also loads sytlesheets, scripts, and generates the metadata. The header includes the Main Navigation and can be optionally fixed to the top. The width of the base layout is maximized to 1320 pixels (see the container-xxl setting of the Bootstrap Containers  ). The height is set to a least 100% of the viewport, to ensure the footer is always aligned to the bottom on the page.

Example  

The following diagram illustrates the conceptual base design:

Header .col-12 (optionally fixed)

Body .col-12 .flex-fill

vertically expands to fill viewport

Social .col-12
Footer .col-12

Configuration  

Hinode uses several settings from Hugo’s Main Configuration  . Several extensions are defined in the Custom Site Parameters  and Language-Specific Configuration  .

Main Configuration  

The base layout uses the Main Configuration  of Hugo. The settings below are actively used by Hinode:

Setting Default Description
title - Title of the website, joined with the separator and title of the current page.
copyright - Copyright notice added to the page footer.
enableGitInfo - Enables git information, which is used by Documentation Pages.
Setting Default
title -
Title of the website, joined with the separator and title of the current page.
copyright -
Copyright notice added to the page footer.
enableGitInfo -
Enables git information, which is used by Documentation Pages.

The below configuration shows the default configuration set in config/_default/hugo.toml.

  • config/_default/hugo.toml
title = "Hinode"
copyright = "Copyright © 2022 - 2025 Mark Dumay."
enableGitInfo = true
...

Extended Configuration  

  Important

The --minify flag of hugo purges HTML whitespace by default. Unfortunately, this also removes the spacing behind the visual cue of external links. When setting externalLinks.cue to true, be sure to add the following configuration to your main configuration to suppress the removal of whitespace:

[minify]
  [minify.tdewolff.html]
    keepWhitespace = true

Hinode uses the following extended settings in the main section of the site parameters:

Setting Default Description
separator “-” Separator to join the website title and page title.
description - Short description of the website that is added to the page metadata.
enableDarkMode true Enables switcher for Light Mode and Dark Mode.
modes [“light”, “dark”] Supported color modes, used as identifier for color-mode aware images.
endorse true By default, the theme adds a link to Hinode in the page’s footer. You can disable it by setting endorse to false, but we would appreciate it if you leave it enabled.
enableLanguageSelectionStorage false If set, stores the last selected language in the site’s local storage. Pages are automatically redirected to the related page translation, if available.
footerBelowFold false If set, pushes the footer including social links to below the page fold.
loading “eager” v0.21.0      Sets the default loading behavior of images below the page fold. Supported values are either “eager” (default) or “lazy”. In practice, Hinode can only determine if an image is below the page fold when fullCover is set to true and the current page is a list page or the homepage. The Image Shortcode Documentation provides more details.
canonifyAssetsURLs false If set, makes permalinks to site assets (favicons, images, scripts, and stylesheets) absolute instead of relative.
breakpoint “md” v0.21.7      Breakpoint for single pages and list pages to start showing the sidebar navigation and table of content panel. Card groups use the same breakpoint to decide how many columns to display in the current viewport.
titleCase false v0.29.0      If set, applies title case to headers and other select elements. Configure the title style in the site configuration  .
internalLinks.validate true If set, validates if internal links reference a valid page.
internalLinks.pretty false v0.27.19      If set, adds a trailing slash to rendered links.
externalLinks.cue false If set, adds a visual cue as suffix to Managed External Links.
externalLinks.tab false If set, opens Managed External Links in a new browser tab using the HTML attributes target="_blank" rel= "noopener noreferrer".
build.transpiler “libsass” v0.20.0      Defines the Sass transpiler to be used, either “libsass” (default) or “dartsass”. The Dart Sass transpiler requires Installation of a Separate Binary on Your Machine  . This includes any production servers used for CI/CD automation and deployment.
build.silenceDeprecations false v0.27.9      Silences any deprecation warnings raised by the Dart Sass transpiler.
Setting Default
separator “-”
Separator to join the website title and page title.
description -
Short description of the website that is added to the page metadata.
enableDarkMode true
Enables switcher for Light Mode and Dark Mode.
modes [“light”, “dark”]
Supported color modes, used as identifier for color-mode aware images.
endorse true
By default, the theme adds a link to Hinode in the page’s footer. You can disable it by setting endorse to false, but we would appreciate it if you leave it enabled.
enableLanguageSelectionStorage false
If set, stores the last selected language in the site’s local storage. Pages are automatically redirected to the related page translation, if available.
footerBelowFold false
If set, pushes the footer including social links to below the page fold.
loading “eager”
v0.21.0      Sets the default loading behavior of images below the page fold. Supported values are either “eager” (default) or “lazy”. In practice, Hinode can only determine if an image is below the page fold when fullCover is set to true and the current page is a list page or the homepage. The Image Shortcode Documentation provides more details.
canonifyAssetsURLs false
If set, makes permalinks to site assets (favicons, images, scripts, and stylesheets) absolute instead of relative.
breakpoint “md”
v0.21.7      Breakpoint for single pages and list pages to start showing the sidebar navigation and table of content panel. Card groups use the same breakpoint to decide how many columns to display in the current viewport.
titleCase false
v0.29.0      If set, applies title case to headers and other select elements. Configure the title style in the site configuration  .
internalLinks.validate true
If set, validates if internal links reference a valid page.
internalLinks.pretty false
v0.27.19      If set, adds a trailing slash to rendered links.
externalLinks.cue false
If set, adds a visual cue as suffix to Managed External Links.
externalLinks.tab false
If set, opens Managed External Links in a new browser tab using the HTML attributes target="_blank" rel= "noopener noreferrer".
build.transpiler “libsass”
v0.20.0      Defines the Sass transpiler to be used, either “libsass” (default) or “dartsass”. The Dart Sass transpiler requires Installation of a Separate Binary on Your Machine  . This includes any production servers used for CI/CD automation and deployment.
build.silenceDeprecations false
v0.27.9      Silences any deprecation warnings raised by the Dart Sass transpiler.

The below configuration shows the default configuration set in config/_default/params.toml.

  • config/_default/params.toml
[main]
    separator = "-"
    description = "Hinode is a clean documentation and blog theme for your Hugo site based on Bootstrap 5."
    enableDarkMode = true
    enableLanguageSelectionStorage = false
    modes = ["light", "dark"]
    canonifyAssetsURLs = false
    endorse = true
    footerBelowFold = false
    loading = "lazy"
    breakpoint = "md"
    titleCase = false
    [main.internalLinks]
        validate = true
        pretty = false
    [main.externalLinks]
        cue = false
        tab = false
    [main.build]
        transpiler = "libsass"
...

Message Configuration  

Added in v0.14.4   

You can show informative messages using the Toast Shortcode. By default, toast messages are displayed in the bottom right of the viewport. Hinode vertically stacks multiple toast messages automatically. Adjust the configuration by adjusting messages in the site parameters. The following arguments are supported:

Setting Default Description
placement “bottom-right” Optional position of the toast messages relative to the viewport: “top-left”, “top-center”,“top-right”, “middle-left”, “middle-center”, “middle-right”, “bottom-left”, “bottom-center”, or “bottom-right” (default).
Setting Default
placement “bottom-right”
Optional position of the toast messages relative to the viewport: “top-left”, “top-center”,“top-right”, “middle-left”, “middle-center”, “middle-right”, “bottom-left”, “bottom-center”, or “bottom-right” (default).

The below configuration shows the default configuration set in config/_default/params.toml.

  • config/_default/params.toml
[messages]
    placement = "bottom-right"
...

Social Sharing Configuration  

Added in v0.14.3   

Hinode can optionally add buttons to share a post via available social media. Use the following extended settings in the sharing section of the site parameters to configure these buttons:

Setting Default Description
enabled false Define if social sharing should be enabled for all single pages. You can override this setting by adding sharing: false to the individual page’s frontmatter.
sort “weight” Sorting key to be used, either name or weight. You can also reference a custom key defined in the provider configuration.
reverse false Flag to indicate if the sorting of the social sharing buttons should be reversed, defaults to false.
webshare false Flag to indicate if native sharing provided by the Operating System should be enabled (via the web share API). If set and Supported by the Browser  , an additional button is added.
Setting Default
enabled false
Define if social sharing should be enabled for all single pages. You can override this setting by adding sharing: false to the individual page’s frontmatter.
sort “weight”
Sorting key to be used, either name or weight. You can also reference a custom key defined in the provider configuration.
reverse false
Flag to indicate if the sorting of the social sharing buttons should be reversed, defaults to false.
webshare false
Flag to indicate if native sharing provided by the Operating System should be enabled (via the web share API). If set and Supported by the Browser  , an additional button is added.

Add each available provider to [[sharing.providers]]. The providers support the following arguments:

Setting Default Description
name - Name of the provider, added as assistive title to improve accessibility.
url - Parameterized URL of the social media provider. The url supports the parameters {url} and {title}. The {url} is replaced with the page’s permalink, and {title} with the page’s title.
icon - Shorthand notation of the Font Awesome Icon to be used as button, e.g. fab linkedin.
weight - Weight of the social sharing button, to be used as sorting key.
clipboard false If set, the defined url is copied to the clipboard instead of being opened. A Toast Message is shown to inform the user.
Setting Default
name -
Name of the provider, added as assistive title to improve accessibility.
url -
Parameterized URL of the social media provider. The url supports the parameters {url} and {title}. The {url} is replaced with the page’s permalink, and {title} with the page’s title.
icon -
Shorthand notation of the Font Awesome Icon to be used as button, e.g. fab linkedin.
weight -
Weight of the social sharing button, to be used as sorting key.
clipboard false
If set, the defined url is copied to the clipboard instead of being opened. A Toast Message is shown to inform the user.

The below configuration shows the default configuration set in config/_default/params.toml.

  • config/_default/params.toml
[sharing]
    enabled = true
    sort = "weight"
    reverse = false
    webshare = true

[[sharing.providers]]
    name = "LinkedIn"
    url = "https://www.linkedin.com/sharing/share-offsite/?url={url}"
    icon = "fab linkedin"
    weight = 10

[[sharing.providers]]
    name = "Twitter"
    url = "https://twitter.com/home?status={url}"
    icon = "fab x-twitter"
    weight = 20

[[sharing.providers]]
    name = "Facebook"
    url = "https://www.facebook.com/sharer.php?u={url}"
    icon = "fab facebook"
    weight = 30

[[sharing.providers]]
    name = "WhatsApp"
    url = "whatsapp://send?text={title}%20{url}"
    icon = "fab whatsapp"
    weight = 40

[[sharing.providers]]
    name = "email"
    url = "{url}"
    icon = "fas link"
    weight = 50
    clipboard = true
...

Language-Specific Configuration  

Hinode supports Multilingual Content  . The following parameters are used in the site’s footer, header, and meta data. Refer to the Languages section to review the various configuration options to enable multilingual content.

Section Setting Default Description
head tagline - Tagline used on the site’s title for the home page.
feature link - v0.18.0      Modify content/{LANG}/_index.md directly ({LANG} is optional, pending on your Language Settings).
feature caption “About” v0.18.0      See feature.link.
social title - Title displayed in the site’s social footer.
social caption - Caption displayed in the site’s social footer.
footer license - License displayed on the site’s footer.
footer socialTitle - v0.18.0      Use social.title instead.
footer socialCaption - v0.18.0      Use social.caption instead.
Section Setting Default
head tagline -
Tagline used on the site’s title for the home page.
feature link -
v0.18.0      Modify content/{LANG}/_index.md directly ({LANG} is optional, pending on your Language Settings).
feature caption “About”
v0.18.0      See feature.link.
social title -
Title displayed in the site’s social footer.
social caption -
Caption displayed in the site’s social footer.
footer license -
License displayed on the site’s footer.
footer socialTitle -
v0.18.0      Use social.title instead.
footer socialCaption -
v0.18.0      Use social.caption instead.

The below configuration shows the default configuration set in config/_default/languages.toml for the English language.

  • config/_default/languages.toml
    [en.params.head]
        tagline = "A Hugo Theme"
    [en.params.social]
        title = "Follow me"
        caption = "I work on everything coding and tweet developer memes"
    [en.params.footer]
        # license = "Licensed under Creative Commons (<a href='https://creativecommons.org/licenses/by-nc-sa/4.0/' class='link-secondary' target='_blank' rel='noopener noreferrer nofollow'>CC BY-NC-SA 4.0</a>)."
...

Home Page  

The home page introduces a feature section and several Configurable Sections. The default home page of Hinode displays the three most recent blog posts and projects, each rendered as cards in a separate section. A button that links to the related list page is added below each group. The feature section can optionally cover the entire viewscreen.

Example  

The following diagram illustrates the conceptual layout of the home page:

Header .col-12

Feature .col-12 .flex-fill

vertically expands to fill viewport

Section 1 .col-12
Section 2 .col-12
Section … .col-12
Social .col-12
Footer .col-12

Configuration  

The configuration of the home page is set in the home section of the site parameters. The following settings are supported:

Setting Default Description
sections All root sections Sections to include on the home page, e.g. ["blog", "projects"] - defaults to All Root Sections. 
featurePhoto - v0.18.0      Use thumbnail of the homepage (e.g. content/_index.md) instead.
fullCover false Flag to indicate if the feature element should cover the entire front page.
style - Optional class attributes to add to the main <div> element of the base page. Applies to the homepage only.
feature.orientation “stacked” v0.21.0      Orientation of the featured section, either “stacked” (default) or “horizontal”.
feature.color - v0.21.0      Optional background color of the featured section, used in conjunction with style.themeOpacity in the site’s parameters.
feature.width 6 v0.21.0      Optional column width of the main featured section, supported values are 1 - 12.
Setting Default
sections All root sections
Sections to include on the home page, e.g. ["blog", "projects"] - defaults to All Root Sections. 
featurePhoto -
v0.18.0      Use thumbnail of the homepage (e.g. content/_index.md) instead.
fullCover false
Flag to indicate if the feature element should cover the entire front page.
style -
Optional class attributes to add to the main <div> element of the base page. Applies to the homepage only.
feature.orientation “stacked”
v0.21.0      Orientation of the featured section, either “stacked” (default) or “horizontal”.
feature.color -
v0.21.0      Optional background color of the featured section, used in conjunction with style.themeOpacity in the site’s parameters.
feature.width 6
v0.21.0      Optional column width of the main featured section, supported values are 1 - 12.

The below configuration shows the default configuration set in config/_default/params.toml. The sections are commented out, meaning all root sections are enabled by default.

  • config/_default/params.toml
[home]
    # sections = ["posts"]
    fullCover = false
    centerHeadline = false
    style = ""
    [home.feature]
        orientation = "horizontal"
        color = "primary"
        width = 4
        align = "start"
...

List Pages  

  Note

List pages support Content View Templates  since release v0.21.0  . Set the type in the page’s frontmatter.

List pages define one Configurable Section for the available content within the page bundle. By default, list pages display the most recent nine items as card group. If the section contains more items, a paginator is added below the card group. Adjust the setting pagerSize in the Main Configuration  as needed.

Example  

The following diagram illustrates the conceptual layout of a list page:

Header .col-12

Section .col-12

optional paginator

Social .col-12
Footer .col-12

Configuration  

The list page uses the Configuration of a Single Section.

Single Pages  

  Important

Single pages support Content View Templates  since release v0.21.0  . Set the type in the page’s frontmatter. The type parameter replaces the previous layout parameter.

Single pages follow the base layout but introduce two columns next to the body content. The left column shows a Sidebar Navigation if applicable and is left empty otherwise. The right column shows a Table of Contents for the current page if applicable. On smaller viewscreens, the sidebar navigation folds into an offcanvas element, whilst the table of contents is hidden. On medium-sized screens the sidebar navigation takes precedence over the table of contents. The following diagram illustrates the base layout (note: this may best be viewed on a larger screen).

Header .col-12

Sidebar

sticky

Body .col-8 .flex-fill

expands to fill viewport

TOC

sticky

Social .col-12
Footer .col-12

Single pages support three optional layout types, which can be configured in the page’s frontmatter. The next paragraphs describe each layout type in more detail. These layout types apply to the body section of the base layout.

Default Layout  

By default, single pages, such as a blog page, include multiple elements, such as a rich header, thumbnail, body, and footer. The following diagram illustrates the default layout of a single page.

Page header

Metadata

Tags

Description

  Thumbnail

Page content

Page footer

Navigation links

Documentation Layout  

Documentation pages use a more straightforward, simplified layout compared to the default layout. Configure the following setting to the page’s frontmatter to apply the documentation layout:

---
type: docs
---

The following diagram illustrates the documentation layout of a single page.

Page header

Description

Page content

Page footer

Git metadata

Minimal Layout  

Pages with a minimal layout are similar to documentation pages, but do not include a footer at all. Configure the following setting to the page’s frontmatter to apply the minimal layout:

---
type: minimal
---

The following diagram illustrates the minimal layout of a single page.

Page header

Description

Page content

Configuration  

Please refer to the Content Management Section to review the elements available in the page’s frontmatter. You can also set the default behavior by page type in the pages section of the site parameters. For example, the following configuration hides the modification date of all news articles, unless overridden in the page’s frontmatter.

[pages]
    [pages.news]
        metadata = "original"
Setting Default Description
metadata “full” v0.21.2      Defines the metadata to include in the header of a single page type. Supported values are “full” (default), “original”, and “none”. In the default configuration, the header includes metadata elements for the original publication date, modification date (if applicable), reading time, and word count. When set to original, the modification date is always omitted. Set metadata to none to suppress all metadata elements.
sharing true v0.21.2      Optional flag to indicate if a single page should include sharing options (when the Social Sharing Configuration is enabled).
Setting Default
metadata “full”
v0.21.2      Defines the metadata to include in the header of a single page type. Supported values are “full” (default), “original”, and “none”. In the default configuration, the header includes metadata elements for the original publication date, modification date (if applicable), reading time, and word count. When set to original, the modification date is always omitted. Set metadata to none to suppress all metadata elements.
sharing true
v0.21.2      Optional flag to indicate if a single page should include sharing options (when the Social Sharing Configuration is enabled).

The configuration of the documentation pages is set in the docs section of the site parameters. The following settings are supported:

Setting Default Description
version - Default version to use in documentation links.
basePath - Base path to use for file references.
github - Repository URL for the docs site, overrides schema/github in config/_default/params.toml.
release - Release url for the docs site, e.g. https://github.com/gethinode/hinode/releases/tag/. This setting is used by the Release Shortcode.
Setting Default
version -
Default version to use in documentation links.
basePath -
Base path to use for file references.
github -
Repository URL for the docs site, overrides schema/github in config/_default/params.toml.
release -
Release url for the docs site, e.g. https://github.com/gethinode/hinode/releases/tag/. This setting is used by the Release Shortcode.

The below configuration shows the default configuration set in config/_default/params.toml.

  • config/_default/params.toml
[docs]
    basePath = "_vendor/github.com/gethinode/hinode"
    github = "https://github.com/gethinode/docs"
    release = "https://github.com/gethinode/hinode/releases/tag/"
...

Page Sections  

Both the home page and the list page use one or more page sections to display a sorted list of items. The lists can contain either Regular Pages or Page Snippets. The next paragraphs describe the three available layout types.

Card Layout  

The card layout displays a group of cards in a grid. The default setting is to show nine items at a time. You can adjust these settings in the Page Section Configuration, including the style of the cards themselves. Refer to the Card Shortcode Documentation to review the available card styles. The next diagram illustrates a typical card layout.

Item 1
Item 2
Item 3
Item 4
Item 5
Item 6
Item 7
Item 8
Item 9

List Layout  

The list layout shows the page bundle’s items as a vertical list. The thumbnail alternates between being left-aligned and right-aligned for each row. Remove the description from the page’s frontmatter to display the full content instead of the description. The content of the item is displayed next to the thumbnail.

 
Item 1
Item 2
 
 
Item 3

Nav Layout  

The nav layout shows a nav element where each tab pane represents a single item of the page bundle. Remove the description from the page’s frontmatter to display the full content instead of the description. The tab pane shows the content of the selected item.

Item 1 | Item 2 | Item 3
Content .col-12

Configuration  

The configuration of each section is set in the sections setting of the site parameters. The entire configuration is fully optional and uses default settings if omitted. The following settings are supported per section:

Setting Default Description
title "" Title of the section on the home page. It overrides the title of the page bundle. On list pages, the title defined in the page bundle’s frontmatter is used instead. When using a multi-lingual site, make sure to properly translate this setting.
reference “More {{section}}” v0.18.0      Caption of the button that links to the section’s associated list page (if applicable). By default, the title is set to “More {{section}}”, where {{section}} is the section title in plural. When using a multi-lingual site, make sure to properly translate this setting.
layout “card” Layout of the section, either “card” (default), “list”, or “nav”.
sort “date” Sorting key to be used, based on a frontmatter parameter. Examples are “date” (default), “lastmod”, “weight”, or “title”. You can also use custom parameters, as long as they are defined in the page’s frontmatter.
reverse true Flag to indicate the sorting of the section content should be reversed, defaults to true.
nested true Flag to indicate the content should be listed recursively for the entire Section  . You can override this setting for individual branch bundles by adding nested to the page’s frontmatter.
background - Theme color of the section background, either “primary”, “secondary”, “success”, “danger”, “warning”, “info”, “light”, “dark”, “white”, “black”, “body”, or “body-tertiary”. By default, no color is specified. The background expands across the entire viewport (thus is not constrained to the page’s maximum width of 1320 pixels).
color - Theme color of the section elements, either “primary”, “secondary”, “success”, “danger”, “warning”, “info”, “light”, “dark”, “white”, “black”, “body”, or “body-tertiary”. By default, no color is specified.
style “border-0 card-zoom” Optional styling attributes added to selection elements, e.g. “border-0” to remove the borders.
wrap false v0.21.0      Optional flag to enable word wrapping of tab titles, defaults to false.
Setting Default
title ""
Title of the section on the home page. It overrides the title of the page bundle. On list pages, the title defined in the page bundle’s frontmatter is used instead. When using a multi-lingual site, make sure to properly translate this setting.
reference “More {{section}}”
v0.18.0      Caption of the button that links to the section’s associated list page (if applicable). By default, the title is set to “More {{section}}”, where {{section}} is the section title in plural. When using a multi-lingual site, make sure to properly translate this setting.
layout “card”
Layout of the section, either “card” (default), “list”, or “nav”.
sort “date”
Sorting key to be used, based on a frontmatter parameter. Examples are “date” (default), “lastmod”, “weight”, or “title”. You can also use custom parameters, as long as they are defined in the page’s frontmatter.
reverse true
Flag to indicate the sorting of the section content should be reversed, defaults to true.
nested true
Flag to indicate the content should be listed recursively for the entire Section  . You can override this setting for individual branch bundles by adding nested to the page’s frontmatter.
background -
Theme color of the section background, either “primary”, “secondary”, “success”, “danger”, “warning”, “info”, “light”, “dark”, “white”, “black”, “body”, or “body-tertiary”. By default, no color is specified. The background expands across the entire viewport (thus is not constrained to the page’s maximum width of 1320 pixels).
color -
Theme color of the section elements, either “primary”, “secondary”, “success”, “danger”, “warning”, “info”, “light”, “dark”, “white”, “black”, “body”, or “body-tertiary”. By default, no color is specified.
style “border-0 card-zoom”
Optional styling attributes added to selection elements, e.g. “border-0” to remove the borders.
wrap false
v0.21.0      Optional flag to enable word wrapping of tab titles, defaults to false.

The card layout supports the following additional arguments:

Setting Default Description
cols 3 Number of columns to display in the card group, should be a value between 1 and 5. The default value is 3.
padding “auto” Padding of the content, either “0”, “1”, “2”, “3”, “4”, “5”, or “auto” (default).
header “full” Header components of the card, displayed in small caps. Supported values are “full” (default), “publication”, “tags”, and “none”.
footer “none” Footer components of the card, displayed in small caps. Supported values are “full”, “publication”, “tags”, and “none” (default).
orientation “stacked” Placement of the thumbnail, either “stacked” (default), “horizontal”, or “none”.
homepage 3 Maximum number of items to display on the home page (if defined in the Configuration), defaults to 3.
separator false Flag to indicate a horizontal line should be added between items on small screens.
Setting Default
cols 3
Number of columns to display in the card group, should be a value between 1 and 5. The default value is 3.
padding “auto”
Padding of the content, either “0”, “1”, “2”, “3”, “4”, “5”, or “auto” (default).
header “full”
Header components of the card, displayed in small caps. Supported values are “full” (default), “publication”, “tags”, and “none”.
footer “none”
Footer components of the card, displayed in small caps. Supported values are “full”, “publication”, “tags”, and “none” (default).
orientation “stacked”
Placement of the thumbnail, either “stacked” (default), “horizontal”, or “none”.
homepage 3
Maximum number of items to display on the home page (if defined in the Configuration), defaults to 3.
separator false
Flag to indicate a horizontal line should be added between items on small screens.

The nav layout supports the following additional arguments:

Setting Default Description
type “pills” Optional type of the tab group, either “tabs”, “pills” (default), or “underline”.
vertical “false” Optional flag to show vertical tabs instead of horizontal tabs (default).
class "" Optional class attribute of the tab group, e.g. “nav-fill”.
pane “none” Optional style of the panes, either “none” (default) or “persona”.
width 100 Optional responsive width of the tab group, either 50 or 100 (default).
Setting Default
type “pills”
Optional type of the tab group, either “tabs”, “pills” (default), or “underline”.
vertical “false”
Optional flag to show vertical tabs instead of horizontal tabs (default).
class ""
Optional class attribute of the tab group, e.g. “nav-fill”.
pane “none”
Optional style of the panes, either “none” (default) or “persona”.
width 100
Optional responsive width of the tab group, either 50 or 100 (default).

The below configuration shows an example configuration of the Guides Available on This Site. The configuration is set in config/_default/params.toml.

  • config/_default/params.toml
[sections]
    [sections.guides]
        title = "Check our guides to get you started"
        layout = "card"
        sort = "date"
        reverse = true
        background = ""
        color = "body-tertiary"
        style = "border-0 shadow card-zoom card-body-margin"
        cols = 3
        padding = "3"
        header = "full"
        footer = "none"
        orientation = "stacked"
        homepage = 3
...
• Fix linting rules (86641b4)
On this page:
Base Layout   Example   Configuration   Home Page   Example   Configuration   List Pages   Example   Configuration   Single Pages   Default Layout   Documentation Layout   Minimal Layout   Configuration   Page Sections   Card Layout   List Layout   Nav Layout   Configuration  
Layout
Layout
Hinode is a clean documentation and blog theme for your Hugo site based on Bootstrap 5.
Code licensed MIT, docs CC BY-NC 4.0
Currently v0.29.3
Privacy | Cookies
 
Links
Home 
About 
Docs 
Components 
Releases 
Guides
Getting Started 
Developing Modules 
Optimization 
Versioning 
Community
Issues   
Discussions   
Contribute 
Hinode
Code copied to clipboard