Merge pull request #161 from gethinode/develop

Separator

.eslintignore

@@ -1,3 +1,4 @@
+assets/js/color.js
 assets/js/flexsearch.js
 assets/js/vendor
 node_modules

.stylelintignore

@@ -1,5 +1,8 @@
 assets/scss/common/_variables.scss
-assets/scss/components/_syntax.scss
+assets/scss/components/_syntax-dark.scss
+assets/scss/components/_syntax-light.scss
+assets/scss/hotfix
 assets/scss/vendor
+assets/scss/fonts.scss
 assets/scss/app.scss
 node_modules

README.md

@@ -11,8 +11,8 @@
     <a href="https://gohugo.io" alt="Hugo website">
         <img src="https://img.shields.io/badge/generator-hugo-brightgreen" />
     </a>
-    <a href="https://app.netlify.com/sites/hinode-demo/deploys" alt="Netlify Status">
-        <img src="https://img.shields.io/netlify/151e88a3-d161-4045-856d-778fea43fc2f" />
+    <a href="https://app.netlify.com/sites/gethinode-demo/deploys" alt="Netlify Status">
+        <img src="https://img.shields.io/netlify/0ad42e3e-fdfa-4d37-8e26-58badd429a67" />
     </a>
     <a href="https://stats.uptimerobot.com/xyGVYhLJmV" alt="UptimeRobot Status">
         <img src="https://img.shields.io/uptimerobot/status/m791334689-73d9dfc82030f4f955b2d6bb" />
@@ -54,17 +54,16 @@ Hinode is a clean documentation and blog theme for [Hugo][hugo], an open-source
 
 Additional features include:
 
-- Comments
-- Social links
-- Blog pagination
-- Code highlighting
-- Command prompt
-- Color customization
-- Language switcher
+- Switching between light mode and dark mode
+- Support for multiple languages
+- Reusable Bootstrap components through configurable shortcodes and partials
+- Embedded comments through light-weight integration with GitHub via [utteranc.es][utterances]
+- Integrated sidebar navigation for content-heavy sections, such as documentation pages
+- Reponsive image handling for multiple screen sizes and resolutions
+- Optimized search results, scoring 100 points for SEO on [PageSpeed Insights][pagespeed]
+- Secure by default, scoring A+ on [Mozilla Observatory test][observatory]
 
-<!-- TODO: add tutorial deep-link 
-Detailed background information is available on the author's [personal blog][blog].
--->
+Detailed information about Hinode is available on the [official website][website].
 
 ## Prerequisites
 
@@ -74,56 +73,39 @@ Hinode requires Git, Node.js and npm for local development and testing. Download
 
 Start a new Hinode project in three steps:
 
-### 1. Create a new site
+1. Create a new site
 
-Hinode is available as a [child theme][repository_child], and a [main theme][repository]. The child theme uses [npm][npm] to link to the latest available version of Hinode. As such, it is less applicable if you plan to customize a lot. Vice versa, the main theme allows for heavy customization, but is not synchronized with the latest available Hinode theme automatically.
+    Hinode is available as a [child theme][repository_child], and a [main theme][repository]. The child theme uses [npm][npm] to link to the latest available version of Hinode. Unless you plan to customize a lot, it is recommended to use the child theme:
 
-Not quite sure? Use the Hinode child theme.
+    ```bash
+    git clone https://github.com/gethinode/child.git my-hinode-site && cd my-hinode-site
+    ```
 
-#### Hinode child theme
+    Use the main theme if you intend to customize the base code:
 
-```bash
-git clone https://github.com/gethinode/child.git my-hinode-site && cd my-hinode-site
-```
+    ```bash
+    git clone https://github.com/gethinode/hinode.git my-hinode-site && cd my-hinode-site
+    ```
 
-#### Hinode main theme
+1. Install dependencies
 
-```bash
-git clone https://github.com/gethinode/hinode.git my-hinode-site && cd my-hinode-site
-```
+    ```bash
+    npm install
+    ```
 
-### 2. Install dependencies
+1. Start development server
 
-```bash
-npm install
-```
-
-### 3. Start development server
-
-```bash
-npm run start
-```
+    ```bash
+    npm run start
+    ```
 
 ## Configuration
 
-The main site configuration is available in `./config/_default`. Some remarks:
-
-- **Menu items** - `menus/menus.en.toml` contains language-specific items for the navigation bar and social media links for the home page's footer.
-- **Content** - Ensure the `mainSections` in `config.toml` is synchronized with the `content` folder, default values are `["blog", "projects"]`.
-- **Theme style** - Update `primary` and `themeOpacity` within the `[style]` section of `params.toml` to update the site's primary color and opacity. Bootstrap's other key colors can be changed too. You can use the [WCAG Color Contrast Checker][contrast_checker] to validate the contrast ratio of your color to improve accessibility. Additionally, set `themeFont` and `themeFontPath` to override the default font.
-- **Comments** - Comments are powered by [utterances][utterances], a lightweight comments widget built on GitHub issues. Update the `repo`  of the `[comments]` section of `params.toml`.
-- **Security policy** - The theme uses rather strict security policies by default. Be sure to include references to external sources in the header configuration to avoid broken links. The settings of the local development server are defined in `server.toml`. Similar settings are defined in the `netlify.toml` file provided in the repository's root when deploying to [Netlify][netlify].
+See the [official documentation][getstarted] on how to configure your site.
 
 ## Contributing
 
-1. Clone the repository and create a new branch
-
-    ```console
-    git checkout https://github.com/gethinode/hinode.git -b name_for_new_branch
-    ```
-
-2. Make and test the changes
-3. Submit a Pull Request with a comprehensive description of the changes
+See the [official documentation][contribute] on how to contribute to the open-source development of Hinode.
 
 ## Credits
 
@@ -138,13 +120,12 @@ Hinode is inspired by the following themes:
 
 ## License
 
-The `hugo-theme-hinode` and `hugo-theme-hinode-child` codebase is released under the [MIT license][license]. The documentation (including the "README") is licensed under the Creative Commons ([CC BY-NC 4.0)][cc-by-nc-4.0] license.
+The `hinode` and `child` codebase is released under the [MIT license][license]. The documentation (including the "README" and `docs` codebase) is licensed under the Creative Commons ([CC BY-NC 4.0)][cc-by-nc-4.0] license.
 
 <!-- MARKDOWN PUBLIC LINKS -->
 [blist]: https://github.com/apvarun/blist-hugo-theme
 [bootstrap]: https://getbootstrap.com
 [cc-by-nc-4.0]: https://creativecommons.org/licenses/by-nc/4.0/
-[contrast_checker]: https://accessibleweb.com/color-contrast-checker/
 [doks]: https://github.com/h-enk/doks
 [flexsearch]: https://github.com/nextapps-de/flexsearch
 [git_download]: https://git-scm.com
@@ -157,11 +138,10 @@ The `hugo-theme-hinode` and `hugo-theme-hinode-child` codebase is released under
 [utterances]: https://utteranc.es
 
 <!-- MARKDOWN MAINTAINED LINKS -->
-<!-- TODO: add blog link
-[blog]: https://markdumay.com
-[blog]: https://github.com/markdumay
--->
+[contribute]: https://gethinode.com/contribute
+[getstarted]: https://gethinode.com/docs
 [demo]: https://demo.gethinode.com/
 [license]: https://github.com/gethinode/hinode/blob/main/LICENSE
 [repository]: https://github.com/gethinode/hinode.git
 [repository_child]: https://github.com/gethinode/child.git
+[website]: https://gethinode.com/

assets/icons/accordion-button-active-icon-dark.svg

@@ -0,0 +1,3 @@
+<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16' fill='{{ .accordion_icon_active_color_dark }}'>
+    <path fill-rule='evenodd' d='M1.646 4.646a.5.5 0 0 1 .708 0L8 10.293l5.646-5.647a.5.5 0 0 1 .708.708l-6 6a.5.5 0 0 1-.708 0l-6-6a.5.5 0 0 1 0-.708z'/>
+</svg>

assets/icons/accordion-button-icon-dark.svg

@@ -0,0 +1,3 @@
+<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16' fill='{{ .accordion_icon_color_dark }}'>
+    <path fill-rule='evenodd' d='M1.646 4.646a.5.5 0 0 1 .708 0L8 10.293l5.646-5.647a.5.5 0 0 1 .708.708l-6 6a.5.5 0 0 1-.708 0l-6-6a.5.5 0 0 1 0-.708z'/>
+</svg>

assets/icons/btn-toggle-dark.svg

@@ -0,0 +1,3 @@
+<svg xmlns='http://www.w3.org/2000/svg' width='16' height='16' viewBox='0 0 320 512' fill='{{ .btn_toggle_color_dark }}'>
+    <path d="M278.6 233.4c12.5 12.5 12.5 32.8 0 45.3l-160 160c-12.5 12.5-32.8 12.5-45.3 0s-12.5-32.8 0-45.3L210.7 256 73.4 118.6c-12.5-12.5-12.5-32.8 0-45.3s32.8-12.5 45.3 0l160 160z"/>
+</svg>

assets/icons/carousel-control-next-icon-bg.svg

@@ -1,3 +1,3 @@
-<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16' fill='{{ .carousel_control_color }} '>
+<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16' fill='{{ .carousel_control_color }}'>
     <path d='M4.646 1.646a.5.5 0 0 1 .708 0l6 6a.5.5 0 0 1 0 .708l-6 6a.5.5 0 0 1-.708-.708L10.293 8 4.646 2.354a.5.5 0 0 1 0-.708z'/>
 </svg>

assets/icons/form-select-indicator-dark.svg

@@ -0,0 +1,3 @@
+<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16'>
+    <path fill='none' stroke='{{ .form_select_indicator_color_dark }}' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' d='m2 5 6 6 6-6'/>
+</svg>

assets/icons/form-switch-bg-image-dark.svg

@@ -0,0 +1,3 @@
+<svg xmlns='http://www.w3.org/2000/svg' viewBox='-4 -4 8 8'>
+    <circle r='3' fill='{{ .form_switch_color_dark }}' />
+</svg>

assets/js/color.js

@@ -0,0 +1,67 @@
+/*!
+ * Color mode toggler for Bootstrap's docs (https://getbootstrap.com/)
+ * Copyright 2011-2022 The Bootstrap Authors
+ * Licensed under the Creative Commons Attribution 3.0 Unported License.
+ */
+
+{{ if site.Params.main.enableDarkMode }}
+
+(() => {
+  'use strict'
+
+  const storedTheme = localStorage.getItem('theme')
+
+  const getPreferredTheme = () => {
+    if (storedTheme) {
+      return storedTheme
+    }
+
+    return window.matchMedia('(prefers-color-scheme: dark)').matches ? 'dark' : 'light'
+  }
+
+  const setTheme = function (theme) {
+    if (theme === 'auto' && window.matchMedia('(prefers-color-scheme: dark)').matches) {
+      document.documentElement.setAttribute('data-bs-theme', 'dark')
+    } else {
+      document.documentElement.setAttribute('data-bs-theme', theme)
+    }
+  }
+
+  setTheme(getPreferredTheme())
+
+  const showActiveTheme = theme => {
+    const activeSelector = document.querySelector('.theme-icon-active')
+    const activeButton = document.querySelector(`[data-bs-theme-value="${theme}"]`)
+    const activeIcon = activeButton.querySelector('i')
+
+    document.querySelectorAll('[data-bs-theme-value]').forEach(element => {
+      element.classList.remove('active')
+    })
+
+    activeSelector.className = activeIcon.className
+    activeSelector.className = activeSelector.className.replace('theme-icon', 'theme-icon-active')
+    activeButton.classList.add('active')
+  }
+
+  window.matchMedia('(prefers-color-scheme: dark)').addEventListener('change', () => {
+    if (storedTheme !== 'light' || storedTheme !== 'dark') {
+      setTheme(getPreferredTheme())
+    }
+  })
+
+  window.addEventListener('DOMContentLoaded', () => {
+    showActiveTheme(getPreferredTheme())
+
+    document.querySelectorAll('[data-bs-theme-value]')
+      .forEach(toggle => {
+        toggle.addEventListener('click', () => {
+          const theme = toggle.getAttribute('data-bs-theme-value')
+          localStorage.setItem('theme', theme)
+          setTheme(theme)
+          showActiveTheme(theme)
+        })
+      })
+  })
+})()
+
+{{ end }}

assets/js/navbar.js

@@ -0,0 +1,16 @@
+const navbar = document.querySelector('.navbar')
+const toggler = document.getElementById('main-nav-toggler')
+
+// set the navbar background color to opaque when scrolling past a breakpoint
+window.onscroll = () => {
+  if (window.scrollY > 75) {
+    navbar.classList.add('nav-active')
+  } else {
+    navbar.classList.remove('nav-active')
+  }
+}
+
+// set the navbar background color to opaque when expanded
+toggler.onclick = () => {
+  navbar.classList.toggle('navbar-expanded')
+}

assets/scss/app.scss

@@ -1,7 +1,6 @@
 // Define template variables
 // TODO: optimize, see https://discourse.gohugo.io/t/initialize-sass-variables-from-hugo-templates/42053
 //       requires installation of dart-sass, no cross-platform installation available yet
-$themeColor:                    {{ site.Params.style.themeColor | default "#007bff" }};
 $themeFont:                     {{ site.Params.style.themeFont | default "Inter" }};
 $primary:                       {{ site.Params.style.primary | default "#007bff" }};
 $secondary:                     {{ site.Params.style.secondary | default "#6c757d" }};
@@ -12,6 +11,8 @@ $danger:                        {{ site.Params.style.danger | default "#dc3545"
 $light:                         {{ site.Params.style.light | default "#f8f9fa" }};
 $dark:                          {{ site.Params.style.dark | default "#212529" }};
 $navbar-offset:                 {{ if site.Params.navigation.fixed }}{{ site.Params.navigation.offset | default "4em" }}{{ else }}0em{{ end }};
+$enable-dark-mode:              {{ site.Params.main.enableDarkMode | default true }} !default;
+$enable-important-utilities:    true !default;
 
 // Include default variable overrides
 @import "common/variables.scss";
@@ -23,13 +24,14 @@ $navbar-offset:                 {{ if site.Params.navigation.fixed }}{{ site.Par
 @import "bootstrap/scss/functions";
 
 // Import Bootstrap configuration
-@import "bootstrap/scss/variables";
-@import "bootstrap/scss/maps";
+@import "hotfix/variables";
+@import "hotfix/variables-dark.scss";
+@import "hotfix/maps";
 @import "bootstrap/scss/mixins";
 @import "bootstrap/scss/utilities";
 
 // Import Bootstrap layout & components
-@import "bootstrap/scss/root";
+@import "hotfix/root";
 @import "bootstrap/scss/reboot";
 @import "bootstrap/scss/type";
 @import "bootstrap/scss/images";
@@ -96,3 +98,11 @@ $navbar-offset:                 {{ if site.Params.navigation.fixed }}{{ site.Par
 @import "layouts/type.scss";
 @import "common/export.scss";
 @import "helpers/colored-links.scss";
+@import "helpers/display.scss";
+
+{{- if not (hasPrefix (lower site.Params.style.themeFontPath) "http") -}}
+@import "fonts.scss";
+{{- end -}}
+
+// Import theme placeholder
+@import "theme.scss";

assets/scss/common/_export.scss

@@ -3,20 +3,26 @@
 // scss-docs-start export
 :hinode-theme {
     --accordion-icon-active-color: #{$accordion-icon-active-color};
+    --accordion-icon-active-color-dark: #{$gray-300};
     --accordion-icon-color: #{$accordion-icon-color};
+    --accordion-icon-color-dark: #{$gray-600};
     --btn-close-color: #{$btn-close-color};
     --btn-toggle-color: #{$btn-toggle-color};
+    --btn-toggle-color-dark: #{$gray-600};
     --carousel-control-color: #{$carousel-control-color};
     --form-check-input-checked-color: #{$form-check-input-checked-color};
     --form-check-input-indeterminate-color: #{$form-check-input-indeterminate-color};
     --form-feedback-icon-invalid-color: #{$form-feedback-icon-invalid-color};
     --form-feedback-icon-valid-color: #{$form-feedback-icon-valid-color};
     --form-select-indicator-color: #{$form-select-indicator-color};
+    --form-select-indicator-color-dark: #{$form-select-indicator-color-dark};
     --form-switch-checked-color: #{$form-switch-checked-color};
     --form-switch-color: #{$form-switch-color};
+    --form-switch-color-dark: #{$form-switch-color-dark};
     --form-switch-focus-color: #{$form-switch-focus-color};
     --navbar-dark-color: #{$navbar-dark-color};
     --navbar-light-icon-color: rgba($body-color, 0.75); // TODO: See https://github.com/twbs/bootstrap/pull/37720
 }
 
 // scss-docs-end export
+// stylelint-enable selector-pseudo-class-no-unknown

assets/scss/common/_icons.scss

@@ -3,18 +3,23 @@ $form-check-input-checked-bg-image:             url("icons/form-check-input-chec
 $form-check-radio-checked-bg-image:             url("icons/form-check-radio-checked-bg-image.svg") !default;
 $form-check-input-indeterminate-bg-image:       url("icons/form-check-input-indeterminate-bg-image.svg") !default;
 $form-switch-bg-image:                          url("icons/form-switch-bg-image.svg") !default;
+$form-switch-bg-image-dark:                     url("icons/form-switch-bg-image-dark.svg") !default;
 $form-switch-focus-bg-image:                    url("icons/form-switch-focus-bg-image.svg") !default;
 $form-switch-checked-bg-image:                  url("icons/form-switch-checked-bg-image.svg") !default;
 $form-select-indicator:                         url("icons/form-select-indicator.svg") !default;
+$form-select-indicator-dark:                    url("icons/form-select-indicator-dark.svg") !default;
 $form-feedback-icon-valid:                      url("icons/form-feedback-icon-valid.svg") !default;
 $form-feedback-icon-invalid:                    url("icons/form-feedback-icon-invalid.svg") !default;
 $navbar-light-toggler-icon-bg:                  url("icons/navbar-light-toggler-icon-bg.svg") !default;
 $navbar-dark-toggler-icon-bg:                   url("icons/navbar-dark-toggler-icon-bg.svg") !default;
 $accordion-button-icon:                         url("icons/accordion-button-icon.svg") !default;
+$accordion-button-icon-dark:                    url("icons/accordion-button-icon-dark.svg") !default;
 $accordion-button-active-icon:                  url("icons/accordion-button-active-icon.svg") !default;
+$accordion-button-active-icon-dark:             url("icons/accordion-button-active-icon-dark.svg") !default;
 $carousel-control-prev-icon-bg:                 url("icons/carousel-control-prev-icon-bg.svg") !default;
 $carousel-control-next-icon-bg:                 url("icons/carousel-control-next-icon-bg.svg") !default;
 $btn-close-bg:                                  url("icons/btn-close-bg.svg") !default;
 $btn-toggle:                                    url("icons/btn-toggle.svg") !default;
+$btn-toggle-dark:                               url("icons/btn-toggle-dark.svg") !default;
 
 // scss-docs-end icons

assets/scss/common/_variables.scss

@@ -17,9 +17,13 @@ $font-weight-bold:              600 !default;
 $font-weight-bolder:            bolder !default;
 
 strong {
-    font-weight:                600 !important;
+    font-weight:                600 if($enable-important-utilities, !important, null);
 }
 // scss-docs-end font
 
 $black:                       #000 !default;
-$btn-toggle-color:              $black !default;
+$btn-toggle-color:              $black !default;
+
+$carousel-dark-indicator-active-bg:  #ffffff !default;
+$carousel-dark-caption-color:        #ffffff !default;
+$carousel-dark-control-icon-filter:  invert(0) grayscale(100) !default;

assets/scss/components/_buttons.scss

@@ -4,5 +4,5 @@
 .btn-primary:active,
 .btn-primary.active,
 .open > .dropdown-toggle.btn-primary {
-    color: #fff !important;
+    color: #fff if($enable-important-utilities, !important, null);
 }

assets/scss/components/_card.scss

@@ -6,7 +6,16 @@
     position: relative;
 }
 
-.card-img-wrap::after {
+.card-zoom {
+    cursor: pointer;
+}
+
+.card-img-wrap img {
+    transition: transform 0.25s ease;
+    width: 100%;
+}
+
+.card-zoom::after .card-img-wrap img {
     content: "";
     position: absolute;
     top: 0;
@@ -18,16 +27,12 @@
     transition: opacity 0.25s;
 }
 
-.card-img-wrap img {
-    transition: transform 0.25s ease;
-    width: 100%;
-}
-
-.card-img-wrap:hover img {
+.card-zoom:hover .card-img-wrap img {
     transform: scale(1.1);
+    opacity: 0.5;
 }
 
-.card-img-wrap:hover::after {
+.card-zoom:hover::after .card-img-wrap img {
     opacity: 1;
 }
 
@@ -40,3 +45,32 @@
     transform: scale(1.01);
     box-shadow: 0 10px 20px rgba(0, 0, 0, 0.12), 0 4px 8px rgba(0, 0, 0, 0.06);
 }
+
+// stylelint-disable annotation-no-unknown
+.card-body-link {
+    color: $body-color if($enable-important-utilities, !important, null);
+}
+
+@if $enable-dark-mode {
+    @include color-mode(dark) {
+        .card-body-link {
+            color: $gray-500 if($enable-important-utilities, !important, null);
+        }
+    }
+}
+
+.card-zoom card-body-link,
+.card-body-link {
+    &:hover,
+    &:focus {
+        color: shade-color($primary, $link-shade-percentage) if($enable-important-utilities, !important, null);
+    }
+}
+
+// stylelint-enable annotation-no-unknown
+
+// make tag-link clickable on top of the stretched-link.
+.card .tag-link {
+    z-index: 2;
+    position: relative;
+}

assets/scss/components/_navbar.scss

@@ -1,16 +1,27 @@
+// stylelint-disable annotation-no-unknown
+
 // Source: https://jsfiddle.net/njhgr40m/
 
+.navbar {
+    transition: 0.5s ease-in-out;
+    background-color: none;
+}
+
+.nav-active, .navbar-expanded {
+    background-color: var(--bs-body-bg);
+}
+
 /* Remove border from toggler */
 .navbar-toggler {
-    border: 0 !important;
+    border: 0 if($enable-important-utilities, !important, null);
 }
 
 .navbar-toggler:focus,
 .navbar-toggler:active,
 .navbar-toggler-icon:focus {
-    outline: none !important;
-    box-shadow: none !important;
-    border: 0 !important;
+    outline: none if($enable-important-utilities, !important, null);
+    box-shadow: none if($enable-important-utilities, !important, null);
+    border: 0 if($enable-important-utilities, !important, null);
 }
 
 /* Lines of the Toggler */
@@ -65,3 +76,17 @@
 .navbar-toggler.collapsed .toggler-icon {
     background-color: #777;
 }
+
+.emphasis {
+    background-color: $black if($enable-important-utilities, !important, null);
+}
+
+@if $enable-dark-mode {
+    @include color-mode(dark) {
+        .emphasis {
+            background-color: $white if($enable-important-utilities, !important, null);
+        }
+    }
+}
+
+// stylelint-enable annotation-no-unknown

assets/scss/components/_search.scss

@@ -11,7 +11,7 @@
 .form-control.is-search {
     padding-right: 4rem;
     border: 1px solid transparent;
-    background: $gray-100;
+    background: var(--bs-tertiary-bg);
 }
 
 .form-control.is-search:focus {
@@ -29,9 +29,9 @@
     padding-right: 0.3125rem;
     padding-left: 0.3125rem;
     font-size: $font-size-base * 0.75;
-    color: $gray-700;
+    color: var(--bs-secondary-color);
     content: "Ctrl + /";
-    border: 1px solid $gray-300;
+    border: 1px solid var(--bs-border-color);
     border-radius: 0.25rem;
 }
 
@@ -59,12 +59,12 @@
 }
 
 #suggestions a:focus {
-    background: $gray-100;
+    background-color: var(--bs-tertiary-bg);
     outline: 0;
 }
 
 #suggestions div:not(:first-child) {
-    border-top: 1px dashed $gray-200;
+    border-top: 1px dashed var(--bs-border-color);
 }
 
 #suggestions div:first-child {
@@ -76,7 +76,7 @@
 }
 
 #suggestions a:hover {
-    background: $gray-100;
+    background-color: var(--bs-tertiary-bg);
 }
 
 #suggestions span {
@@ -86,12 +86,11 @@
 
 .suggestion__title {
     font-weight: $headings-font-weight;
-    color: $black;
 }
 
 .suggestion__description,
 .suggestion__no-results {
-    color: $gray-700;
+    color: var(--bs-secondary-color);
 }
 
 @include media-breakpoint-up(sm) {
@@ -106,7 +105,7 @@
     .suggestion__title {
         width: 9rem;
         padding-right: 1rem;
-        border-right: 1px solid $gray-200;
+        border-right: 1px solid var(--bs-border-color);
         display: inline-block;
         text-align: right;
     }

assets/scss/components/_sidebar.scss

@@ -3,6 +3,10 @@
     top: $navbar-offset;
 }
 
+.sidebar-item {
+    color: black;
+}
+
 .btn-toggle {
     padding: 0.25rem 0.5rem;
     font-weight: 600;
@@ -11,7 +15,7 @@
 
     &:hover,
     &:focus {
-        color: rgba(0, 0, 0, 0.85);
+        color: black;
         background-color: tint-color($primary, 90%);
     }
 
@@ -24,10 +28,8 @@
     }
 }
 
-// scss-docs-end sidebar
-
 .btn-toggle[aria-expanded="true"] {
-    color: rgba(0, 0, 0, 0.85);
+    color: black;
 
     &::before {
         transform: rotate(90deg);
@@ -49,6 +51,50 @@
     }
 }
 
+@if $enable-dark-mode {
+    @include color-mode(dark) {
+        .sidebar-item {
+            color: var(--bs-tertiary-color);
+        }
+
+        .btn-toggle {
+            color: var(--bs-tertiary-color);
+        
+            &:hover,
+            &:focus {
+                color: $secondary;
+                background-color: tint-color($primary, 90%);
+            }
+        
+            &::before {
+                content: $btn-toggle-dark;
+            }
+        }
+
+        .btn-toggle[aria-expanded="true"] {
+            color: var(--bs-secondary-color);
+        }
+
+        .btn-toggle-nav a {
+            padding: 0.1875rem 0.5rem;
+            margin-top: 0.125rem;
+            margin-left: 1.25rem;
+
+            &:hover,
+            &:focus {
+                color: $secondary;
+                background-color: tint-color($primary, 90%);
+            }
+
+            &.active {
+                font-weight: bold;
+            }
+        }
+    }
+}
+
+// scss-docs-end sidebar
+
 .dropdown-toggle {
     outline: 0;
 }

assets/scss/components/_syntax-dark.scss

@@ -0,0 +1,86 @@
+/* Background */ .bg { color: #c9d1d9; background-color: #0d1117; }
+/* PreWrapper */ .chroma { color: #c9d1d9; background-color: #0d1117; }
+/* Other */ .chroma .x {  }
+/* Error */ .chroma .err { color: #f85149 }
+/* CodeLine */ .chroma .cl {  }
+/* LineLink */ .chroma .lnlinks { outline: none; text-decoration: none; color: inherit }
+/* LineTableTD */ .chroma .lntd { vertical-align: top; padding: 0; margin: 0; border: 0; }
+/* LineTable */ .chroma .lntable { border-spacing: 0; padding: 0; margin: 0; border: 0; }
+/* LineHighlight */ .chroma .hl { background-color: #ffffcc }
+/* LineNumbersTable */ .chroma .lnt { white-space: pre; user-select: none; margin-right: 0.4em; padding: 0 0.4em 0 0.4em;color: #64686c }
+/* LineNumbers */ .chroma .ln { white-space: pre; user-select: none; margin-right: 0.4em; padding: 0 0.4em 0 0.4em;color: #6e7681 }
+/* Line */ .chroma .line { display: flex; }
+/* Keyword */ .chroma .k { color: #ff7b72 }
+/* KeywordConstant */ .chroma .kc { color: #79c0ff }
+/* KeywordDeclaration */ .chroma .kd { color: #ff7b72 }
+/* KeywordNamespace */ .chroma .kn { color: #ff7b72 }
+/* KeywordPseudo */ .chroma .kp { color: #79c0ff }
+/* KeywordReserved */ .chroma .kr { color: #ff7b72 }
+/* KeywordType */ .chroma .kt { color: #ff7b72 }
+/* Name */ .chroma .n {  }
+/* NameAttribute */ .chroma .na {  }
+/* NameBuiltin */ .chroma .nb {  }
+/* NameBuiltinPseudo */ .chroma .bp {  }
+/* NameClass */ .chroma .nc { color: #f0883e; font-weight: bold }
+/* NameConstant */ .chroma .no { color: #79c0ff; font-weight: bold }
+/* NameDecorator */ .chroma .nd { color: #d2a8ff; font-weight: bold }
+/* NameEntity */ .chroma .ni { color: #ffa657 }
+/* NameException */ .chroma .ne { color: #f0883e; font-weight: bold }
+/* NameFunction */ .chroma .nf { color: #d2a8ff; font-weight: bold }
+/* NameFunctionMagic */ .chroma .fm {  }
+/* NameLabel */ .chroma .nl { color: #79c0ff; font-weight: bold }
+/* NameNamespace */ .chroma .nn { color: #ff7b72 }
+/* NameOther */ .chroma .nx {  }
+/* NameProperty */ .chroma .py { color: #79c0ff }
+/* NameTag */ .chroma .nt { color: #7ee787 }
+/* NameVariable */ .chroma .nv { color: #79c0ff }
+/* NameVariableClass */ .chroma .vc {  }
+/* NameVariableGlobal */ .chroma .vg {  }
+/* NameVariableInstance */ .chroma .vi {  }
+/* NameVariableMagic */ .chroma .vm {  }
+/* Literal */ .chroma .l { color: #a5d6ff }
+/* LiteralDate */ .chroma .ld { color: #79c0ff }
+/* LiteralString */ .chroma .s { color: #a5d6ff }
+/* LiteralStringAffix */ .chroma .sa { color: #79c0ff }
+/* LiteralStringBacktick */ .chroma .sb { color: #a5d6ff }
+/* LiteralStringChar */ .chroma .sc { color: #a5d6ff }
+/* LiteralStringDelimiter */ .chroma .dl { color: #79c0ff }
+/* LiteralStringDoc */ .chroma .sd { color: #a5d6ff }
+/* LiteralStringDouble */ .chroma .s2 { color: #a5d6ff }
+/* LiteralStringEscape */ .chroma .se { color: #79c0ff }
+/* LiteralStringHeredoc */ .chroma .sh { color: #79c0ff }
+/* LiteralStringInterpol */ .chroma .si { color: #a5d6ff }
+/* LiteralStringOther */ .chroma .sx { color: #a5d6ff }
+/* LiteralStringRegex */ .chroma .sr { color: #79c0ff }
+/* LiteralStringSingle */ .chroma .s1 { color: #a5d6ff }
+/* LiteralStringSymbol */ .chroma .ss { color: #a5d6ff }
+/* LiteralNumber */ .chroma .m { color: #a5d6ff }
+/* LiteralNumberBin */ .chroma .mb { color: #a5d6ff }
+/* LiteralNumberFloat */ .chroma .mf { color: #a5d6ff }
+/* LiteralNumberHex */ .chroma .mh { color: #a5d6ff }
+/* LiteralNumberInteger */ .chroma .mi { color: #a5d6ff }
+/* LiteralNumberIntegerLong */ .chroma .il { color: #a5d6ff }
+/* LiteralNumberOct */ .chroma .mo { color: #a5d6ff }
+/* Operator */ .chroma .o { color: #ff7b72; font-weight: bold }
+/* OperatorWord */ .chroma .ow { color: #ff7b72; font-weight: bold }
+/* Punctuation */ .chroma .p {  }
+/* Comment */ .chroma .c { color: #8b949e; font-style: italic }
+/* CommentHashbang */ .chroma .ch { color: #8b949e; font-style: italic }
+/* CommentMultiline */ .chroma .cm { color: #8b949e; font-style: italic }
+/* CommentSingle */ .chroma .c1 { color: #8b949e; font-style: italic }
+/* CommentSpecial */ .chroma .cs { color: #8b949e; font-weight: bold; font-style: italic }
+/* CommentPreproc */ .chroma .cp { color: #8b949e; font-weight: bold; font-style: italic }
+/* CommentPreprocFile */ .chroma .cpf { color: #8b949e; font-weight: bold; font-style: italic }
+/* Generic */ .chroma .g {  }
+/* GenericDeleted */ .chroma .gd { color: #ffa198; background-color: #490202 }
+/* GenericEmph */ .chroma .ge { font-style: italic }
+/* GenericError */ .chroma .gr { color: #ffa198 }
+/* GenericHeading */ .chroma .gh { color: #79c0ff; font-weight: bold }
+/* GenericInserted */ .chroma .gi { color: #56d364; background-color: #0f5323 }
+/* GenericOutput */ .chroma .go { color: #8b949e }
+/* GenericPrompt */ .chroma .gp { color: #8b949e }
+/* GenericStrong */ .chroma .gs { font-weight: bold }
+/* GenericSubheading */ .chroma .gu { color: #79c0ff }
+/* GenericTraceback */ .chroma .gt { color: #ff7b72 }
+/* GenericUnderline */ .chroma .gl { text-decoration: underline }
+/* TextWhitespace */ .chroma .w { color: #6e7681 }

assets/scss/components/_syntax-light.scss

@@ -0,0 +1,86 @@
+/* Background */ .bg { background-color: #ffffff; }
+/* PreWrapper */ .chroma { background-color: #ffffff; }
+/* Other */ .chroma .x {  }
+/* Error */ .chroma .err { color: #a61717; background-color: #e3d2d2 }
+/* CodeLine */ .chroma .cl {  }
+/* LineLink */ .chroma .lnlinks { outline: none; text-decoration: none; color: inherit }
+/* LineTableTD */ .chroma .lntd { vertical-align: top; padding: 0; margin: 0; border: 0; }
+/* LineTable */ .chroma .lntable { border-spacing: 0; padding: 0; margin: 0; border: 0; }
+/* LineHighlight */ .chroma .hl { background-color: #ffffcc }
+/* LineNumbersTable */ .chroma .lnt { white-space: pre; user-select: none; margin-right: 0.4em; padding: 0 0.4em 0 0.4em;color: #7f7f7f }
+/* LineNumbers */ .chroma .ln { white-space: pre; user-select: none; margin-right: 0.4em; padding: 0 0.4em 0 0.4em;color: #7f7f7f }
+/* Line */ .chroma .line { display: flex; }
+/* Keyword */ .chroma .k { color: #000000; font-weight: bold }
+/* KeywordConstant */ .chroma .kc { color: #000000; font-weight: bold }
+/* KeywordDeclaration */ .chroma .kd { color: #000000; font-weight: bold }
+/* KeywordNamespace */ .chroma .kn { color: #000000; font-weight: bold }
+/* KeywordPseudo */ .chroma .kp { color: #000000; font-weight: bold }
+/* KeywordReserved */ .chroma .kr { color: #000000; font-weight: bold }
+/* KeywordType */ .chroma .kt { color: #445588; font-weight: bold }
+/* Name */ .chroma .n {  }
+/* NameAttribute */ .chroma .na { color: #008080 }
+/* NameBuiltin */ .chroma .nb { color: #0086b3 }
+/* NameBuiltinPseudo */ .chroma .bp { color: #999999 }
+/* NameClass */ .chroma .nc { color: #445588; font-weight: bold }
+/* NameConstant */ .chroma .no { color: #008080 }
+/* NameDecorator */ .chroma .nd { color: #3c5d5d; font-weight: bold }
+/* NameEntity */ .chroma .ni { color: #800080 }
+/* NameException */ .chroma .ne { color: #990000; font-weight: bold }
+/* NameFunction */ .chroma .nf { color: #990000; font-weight: bold }
+/* NameFunctionMagic */ .chroma .fm {  }
+/* NameLabel */ .chroma .nl { color: #990000; font-weight: bold }
+/* NameNamespace */ .chroma .nn { color: #555555 }
+/* NameOther */ .chroma .nx {  }
+/* NameProperty */ .chroma .py {  }
+/* NameTag */ .chroma .nt { color: #000080 }
+/* NameVariable */ .chroma .nv { color: #008080 }
+/* NameVariableClass */ .chroma .vc { color: #008080 }
+/* NameVariableGlobal */ .chroma .vg { color: #008080 }
+/* NameVariableInstance */ .chroma .vi { color: #008080 }
+/* NameVariableMagic */ .chroma .vm {  }
+/* Literal */ .chroma .l {  }
+/* LiteralDate */ .chroma .ld {  }
+/* LiteralString */ .chroma .s { color: #dd1144 }
+/* LiteralStringAffix */ .chroma .sa { color: #dd1144 }
+/* LiteralStringBacktick */ .chroma .sb { color: #dd1144 }
+/* LiteralStringChar */ .chroma .sc { color: #dd1144 }
+/* LiteralStringDelimiter */ .chroma .dl { color: #dd1144 }
+/* LiteralStringDoc */ .chroma .sd { color: #dd1144 }
+/* LiteralStringDouble */ .chroma .s2 { color: #dd1144 }
+/* LiteralStringEscape */ .chroma .se { color: #dd1144 }
+/* LiteralStringHeredoc */ .chroma .sh { color: #dd1144 }
+/* LiteralStringInterpol */ .chroma .si { color: #dd1144 }
+/* LiteralStringOther */ .chroma .sx { color: #dd1144 }
+/* LiteralStringRegex */ .chroma .sr { color: #009926 }
+/* LiteralStringSingle */ .chroma .s1 { color: #dd1144 }
+/* LiteralStringSymbol */ .chroma .ss { color: #990073 }
+/* LiteralNumber */ .chroma .m { color: #009999 }
+/* LiteralNumberBin */ .chroma .mb { color: #009999 }
+/* LiteralNumberFloat */ .chroma .mf { color: #009999 }
+/* LiteralNumberHex */ .chroma .mh { color: #009999 }
+/* LiteralNumberInteger */ .chroma .mi { color: #009999 }
+/* LiteralNumberIntegerLong */ .chroma .il { color: #009999 }
+/* LiteralNumberOct */ .chroma .mo { color: #009999 }
+/* Operator */ .chroma .o { color: #000000; font-weight: bold }
+/* OperatorWord */ .chroma .ow { color: #000000; font-weight: bold }
+/* Punctuation */ .chroma .p {  }
+/* Comment */ .chroma .c { color: #999988; font-style: italic }
+/* CommentHashbang */ .chroma .ch { color: #999988; font-style: italic }
+/* CommentMultiline */ .chroma .cm { color: #999988; font-style: italic }
+/* CommentSingle */ .chroma .c1 { color: #999988; font-style: italic }
+/* CommentSpecial */ .chroma .cs { color: #999999; font-weight: bold; font-style: italic }
+/* CommentPreproc */ .chroma .cp { color: #999999; font-weight: bold; font-style: italic }
+/* CommentPreprocFile */ .chroma .cpf { color: #999999; font-weight: bold; font-style: italic }
+/* Generic */ .chroma .g {  }
+/* GenericDeleted */ .chroma .gd { color: #000000; background-color: #ffdddd }
+/* GenericEmph */ .chroma .ge { color: #000000; font-style: italic }
+/* GenericError */ .chroma .gr { color: #aa0000 }
+/* GenericHeading */ .chroma .gh { color: #999999 }
+/* GenericInserted */ .chroma .gi { color: #000000; background-color: #ddffdd }
+/* GenericOutput */ .chroma .go { color: #888888 }
+/* GenericPrompt */ .chroma .gp { color: #555555 }
+/* GenericStrong */ .chroma .gs { font-weight: bold }
+/* GenericSubheading */ .chroma .gu { color: #aaaaaa }
+/* GenericTraceback */ .chroma .gt { color: #aa0000 }
+/* GenericUnderline */ .chroma .gl { text-decoration: underline }
+/* TextWhitespace */ .chroma .w { color: #bbbbbb }

assets/scss/components/_syntax.scss

@@ -1,86 +1,40 @@
-/* Background */ .bg { color: #272822; }
-/* PreWrapper */ .chroma { color: #272822 }
-/* Other */ .chroma .x {  }
-/* Error */ .chroma .err { color: #960050 }
-/* CodeLine */ .chroma .cl {  }
-/* LineLink */ .chroma .lnlinks { outline: none; text-decoration: none; color: inherit }
-/* LineTableTD */ .chroma .lntd { vertical-align: top; padding: 0; margin: 0; border: 0; }
-/* LineTable */ .chroma .lntable { border-spacing: 0; padding: 0; margin: 0; border: 0; }
-/* LineHighlight */ .chroma .hl { background-color: #ffffcc }
-/* LineNumbersTable */ .chroma .lnt { white-space: pre; user-select: none; margin-right: 0.4em; padding: 0 0.4em 0 0.4em;color: #7f7f7f }
-/* LineNumbers */ .chroma .ln { white-space: pre; user-select: none; margin-right: 0.4em; padding: 0 0.4em 0 0.4em;color: #7f7f7f }
-/* Line */ .chroma .line { display: flex; }
-/* Keyword */ .chroma .k { color: #00a8c8 }
-/* KeywordConstant */ .chroma .kc { color: #00a8c8 }
-/* KeywordDeclaration */ .chroma .kd { color: #00a8c8 }
-/* KeywordNamespace */ .chroma .kn { color: #f92672 }
-/* KeywordPseudo */ .chroma .kp { color: #00a8c8 }
-/* KeywordReserved */ .chroma .kr { color: #00a8c8 }
-/* KeywordType */ .chroma .kt { color: #00a8c8 }
-/* Name */ .chroma .n { color: #111111 }
-/* NameAttribute */ .chroma .na { color: #75af00 }
-/* NameBuiltin */ .chroma .nb { color: #111111 }
-/* NameBuiltinPseudo */ .chroma .bp { color: #111111 }
-/* NameClass */ .chroma .nc { color: #75af00 }
-/* NameConstant */ .chroma .no { color: #00a8c8 }
-/* NameDecorator */ .chroma .nd { color: #75af00 }
-/* NameEntity */ .chroma .ni { color: #111111 }
-/* NameException */ .chroma .ne { color: #75af00 }
-/* NameFunction */ .chroma .nf { color: #75af00 }
-/* NameFunctionMagic */ .chroma .fm { color: #111111 }
-/* NameLabel */ .chroma .nl { color: #111111 }
-/* NameNamespace */ .chroma .nn { color: #111111 }
-/* NameOther */ .chroma .nx { color: #75af00 }
-/* NameProperty */ .chroma .py { color: #111111 }
-/* NameTag */ .chroma .nt { color: #f92672 }
-/* NameVariable */ .chroma .nv { color: #111111 }
-/* NameVariableClass */ .chroma .vc { color: #111111 }
-/* NameVariableGlobal */ .chroma .vg { color: #111111 }
-/* NameVariableInstance */ .chroma .vi { color: #111111 }
-/* NameVariableMagic */ .chroma .vm { color: #111111 }
-/* Literal */ .chroma .l { color: #ae81ff }
-/* LiteralDate */ .chroma .ld { color: #d88200 }
-/* LiteralString */ .chroma .s { color: #d88200 }
-/* LiteralStringAffix */ .chroma .sa { color: #d88200 }
-/* LiteralStringBacktick */ .chroma .sb { color: #d88200 }
-/* LiteralStringChar */ .chroma .sc { color: #d88200 }
-/* LiteralStringDelimiter */ .chroma .dl { color: #d88200 }
-/* LiteralStringDoc */ .chroma .sd { color: #d88200 }
-/* LiteralStringDouble */ .chroma .s2 { color: #d88200 }
-/* LiteralStringEscape */ .chroma .se { color: #8045ff }
-/* LiteralStringHeredoc */ .chroma .sh { color: #d88200 }
-/* LiteralStringInterpol */ .chroma .si { color: #d88200 }
-/* LiteralStringOther */ .chroma .sx { color: #d88200 }
-/* LiteralStringRegex */ .chroma .sr { color: #d88200 }
-/* LiteralStringSingle */ .chroma .s1 { color: #d88200 }
-/* LiteralStringSymbol */ .chroma .ss { color: #d88200 }
-/* LiteralNumber */ .chroma .m { color: #ae81ff }
-/* LiteralNumberBin */ .chroma .mb { color: #ae81ff }
-/* LiteralNumberFloat */ .chroma .mf { color: #ae81ff }
-/* LiteralNumberHex */ .chroma .mh { color: #ae81ff }
-/* LiteralNumberInteger */ .chroma .mi { color: #ae81ff }
-/* LiteralNumberIntegerLong */ .chroma .il { color: #ae81ff }
-/* LiteralNumberOct */ .chroma .mo { color: #ae81ff }
-/* Operator */ .chroma .o { color: #f92672 }
-/* OperatorWord */ .chroma .ow { color: #f92672 }
-/* Punctuation */ .chroma .p { color: #111111 }
-/* Comment */ .chroma .c { color: #75715e }
-/* CommentHashbang */ .chroma .ch { color: #75715e }
-/* CommentMultiline */ .chroma .cm { color: #75715e }
-/* CommentSingle */ .chroma .c1 { color: #75715e }
-/* CommentSpecial */ .chroma .cs { color: #75715e }
-/* CommentPreproc */ .chroma .cp { color: #75715e }
-/* CommentPreprocFile */ .chroma .cpf { color: #75715e }
-/* Generic */ .chroma .g {  }
-/* GenericDeleted */ .chroma .gd {  }
-/* GenericEmph */ .chroma .ge { font-style: italic }
-/* GenericError */ .chroma .gr {  }
-/* GenericHeading */ .chroma .gh {  }
-/* GenericInserted */ .chroma .gi {  }
-/* GenericOutput */ .chroma .go {  }
-/* GenericPrompt */ .chroma .gp {  }
-/* GenericStrong */ .chroma .gs { font-weight: bold }
-/* GenericSubheading */ .chroma .gu {  }
-/* GenericTraceback */ .chroma .gt {  }
-/* GenericUnderline */ .chroma .gl {  }
-/* TextWhitespace */ .chroma .w {  }
+// stylelint-disable annotation-no-unknown
+@import "syntax-light";
+
+.bg,
+.chroma,
+.chroma .err {
+    // set to transparent background to avoid rendering issues with example shortcode
+    background-color: transparent if($enable-important-utilities, !important, null);
+}
+
+.syntax-highlight {
+    background-color: var(--bs-light) if($enable-important-utilities, !important, null);
+}
+
+.preview-background {
+    background-color: var(--bs-secondary-bg) if($enable-important-utilities, !important, null);
+}
+
+@if $enable-dark-mode {
+    [data-bs-theme="dark"] {
+        @import "syntax-dark"; // stylelint-disable-line no-invalid-position-at-import-rule
+
+        .bg,
+        .chroma,
+        .chroma .err {
+            // set to transparent background to avoid rendering issues with example shortcode
+            background-color: transparent if($enable-important-utilities, !important, null);
+        }
+
+        .syntax-highlight {
+            background-color: var(--bs-tertiary-bg) if($enable-important-utilities, !important, null);
+        }
+
+        .bg,
+        .chroma {
+            color: #c9d1d9 if($enable-important-utilities, !important, null);
+        }
+    }
+}
+// stylelint-enable annotation-no-unknown

assets/scss/fonts.scss

@@ -0,0 +1,62 @@
+/*!
+ * Copyright (c) 2016-2020 The Inter Project Authors.
+ * "Inter" is trademark of Rasmus Andersson.
+ * https://github.com/rsms/inter
+
+ * This Font Software is licensed under the SIL Open Font License, Version 1.1.
+ * This license is copied below, and is also available with a FAQ at:
+ * http://scripts.sil.org/OFL
+ */
+
+/* inter-200 - latin */
+@font-face {
+    font-display: swap; /* Check https://developer.mozilla.org/en-US/docs/Web/CSS/@font-face/font-display for other options. */
+    font-family: 'Inter';
+    font-style: normal;
+    font-weight: 200;
+    src: url('../fonts/inter-v12-latin-200.eot'); /* IE9 Compat Modes */
+    src: url('../fonts/inter-v12-latin-200.eot?#iefix') format('embedded-opentype'), /* IE6-IE8 */
+         url('../fonts/inter-v12-latin-200.woff2') format('woff2'), /* Super Modern Browsers */
+         url('../fonts/inter-v12-latin-200.woff') format('woff'), /* Modern Browsers */
+         url('../fonts/inter-v12-latin-200.ttf') format('truetype'), /* Safari, Android, iOS */
+         url('../fonts/inter-v12-latin-200.svg#Inter') format('svg'); /* Legacy iOS */
+  }
+  /* inter-300 - latin */
+  @font-face {
+    font-display: swap; /* Check https://developer.mozilla.org/en-US/docs/Web/CSS/@font-face/font-display for other options. */
+    font-family: 'Inter';
+    font-style: normal;
+    font-weight: 300;
+    src: url('../fonts/inter-v12-latin-300.eot'); /* IE9 Compat Modes */
+    src: url('../fonts/inter-v12-latin-300.eot?#iefix') format('embedded-opentype'), /* IE6-IE8 */
+         url('../fonts/inter-v12-latin-300.woff2') format('woff2'), /* Super Modern Browsers */
+         url('../fonts/inter-v12-latin-300.woff') format('woff'), /* Modern Browsers */
+         url('../fonts/inter-v12-latin-300.ttf') format('truetype'), /* Safari, Android, iOS */
+         url('../fonts/inter-v12-latin-300.svg#Inter') format('svg'); /* Legacy iOS */
+  }
+  /* inter-regular - latin */
+  @font-face {
+    font-display: swap; /* Check https://developer.mozilla.org/en-US/docs/Web/CSS/@font-face/font-display for other options. */
+    font-family: 'Inter';
+    font-style: normal;
+    font-weight: 400;
+    src: url('../fonts/inter-v12-latin-regular.eot'); /* IE9 Compat Modes */
+    src: url('../fonts/inter-v12-latin-regular.eot?#iefix') format('embedded-opentype'), /* IE6-IE8 */
+         url('../fonts/inter-v12-latin-regular.woff2') format('woff2'), /* Super Modern Browsers */
+         url('../fonts/inter-v12-latin-regular.woff') format('woff'), /* Modern Browsers */
+         url('../fonts/inter-v12-latin-regular.ttf') format('truetype'), /* Safari, Android, iOS */
+         url('../fonts/inter-v12-latin-regular.svg#Inter') format('svg'); /* Legacy iOS */
+  }
+  /* inter-600 - latin */
+  @font-face {
+    font-display: swap; /* Check https://developer.mozilla.org/en-US/docs/Web/CSS/@font-face/font-display for other options. */
+    font-family: 'Inter';
+    font-style: normal;
+    font-weight: 600;
+    src: url('../fonts/inter-v12-latin-600.eot'); /* IE9 Compat Modes */
+    src: url('../fonts/inter-v12-latin-600.eot?#iefix') format('embedded-opentype'), /* IE6-IE8 */
+         url('../fonts/inter-v12-latin-600.woff2') format('woff2'), /* Super Modern Browsers */
+         url('../fonts/inter-v12-latin-600.woff') format('woff'), /* Modern Browsers */
+         url('../fonts/inter-v12-latin-600.ttf') format('truetype'), /* Safari, Android, iOS */
+         url('../fonts/inter-v12-latin-600.svg#Inter') format('svg'); /* Legacy iOS */
+  }

assets/scss/helpers/_colored-links.scss

@@ -1,4 +1,4 @@
-// stylelint-disable function-name-case
+// stylelint-disable function-name-case, declaration-no-important
 
 // scss-docs-start colored-links
 @each $color, $value in $theme-colors {
@@ -6,16 +6,20 @@
     $color-rgb: to-rgb($value);
 
     .link-bg-#{$color} {
-        color: $contrast-color !important; // stylelint-disable-line declaration-no-important
-        background-color: RGBA($color-rgb, var(--#{$prefix}bg-opacity, 1)) if($enable-important-utilities, !important, null); // stylelint-disable-line annotation-no-unknown
+        color: $contrast-color if($enable-important-utilities, !important, null); 
+        background-color: RGBA($color-rgb, var(--#{$prefix}bg-opacity, 1)) if($enable-important-utilities, !important, null);
 
         @if $link-shade-percentage != 0 {
             &:hover,
             &:focus {
-                color: if($contrast-color == $color-contrast-light, shade-color($contrast-color, $link-shade-percentage), tint-color($contrast-color, $link-shade-percentage)) !important; // stylelint-disable-line declaration-no-important
+                color: if($contrast-color == $color-contrast-light, 
+                shade-color($contrast-color, $link-shade-percentage),
+                tint-color($contrast-color, $link-shade-percentage))
+                    if($enable-important-utilities, !important, null);
             }
         }
     }
 }
 
 // scss-docs-end colored-links
+// stylelint-enable function-name-case, declaration-no-important

assets/scss/helpers/_display.scss

@@ -0,0 +1,30 @@
+.hidden {
+    display: none;
+}
+
+// stylelint-disable annotation-no-unknown
+
+// scss-docs-start display-color
+.d-none-light {
+    display: none if($enable-important-utilities, !important, null); 
+}
+
+.d-none-dark {
+    display: block if($enable-important-utilities, !important, null);
+}
+
+@if $enable-dark-mode {
+    @include color-mode(dark) {
+        .d-none-light {
+            display: block if($enable-important-utilities, !important, null);
+        }
+
+        .d-none-dark {
+            display: none if($enable-important-utilities, !important, null);
+        }
+    }
+}
+
+// scss-docs-end display-color
+
+// stylelint-enable annotation-no-unknown

assets/scss/hotfix/_maps.scss

@@ -0,0 +1,176 @@
+// Copied from https://github.com/twbs/bootstrap/commit/15744ee1d04bcca03155c3bb37ee7e65a7b011c6
+//
+// Re-assigned maps
+//
+// Placed here so that others can override the default Sass maps and see automatic updates to utilities and more.
+
+// scss-docs-start theme-colors-rgb
+$theme-colors-rgb: map-loop($theme-colors, to-rgb, "$value") !default;
+// scss-docs-end theme-colors-rgb
+
+// scss-docs-start theme-text-map
+$theme-colors-text: (
+  "primary": $primary-text-emphasis,
+  "secondary": $secondary-text-emphasis,
+  "success": $success-text-emphasis,
+  "info": $info-text-emphasis,
+  "warning": $warning-text-emphasis,
+  "danger": $danger-text-emphasis,
+  "light": $light-text-emphasis,
+  "dark": $dark-text-emphasis,
+) !default;
+// scss-docs-end theme-text-map
+
+// scss-docs-start theme-bg-subtle-map
+$theme-colors-bg-subtle: (
+  "primary": $primary-bg-subtle,
+  "secondary": $secondary-bg-subtle,
+  "success": $success-bg-subtle,
+  "info": $info-bg-subtle,
+  "warning": $warning-bg-subtle,
+  "danger": $danger-bg-subtle,
+  "light": $light-bg-subtle,
+  "dark": $dark-bg-subtle,
+) !default;
+// scss-docs-end theme-bg-subtle-map
+
+// scss-docs-start theme-border-subtle-map
+$theme-colors-border-subtle: (
+  "primary": $primary-border-subtle,
+  "secondary": $secondary-border-subtle,
+  "success": $success-border-subtle,
+  "info": $info-border-subtle,
+  "warning": $warning-border-subtle,
+  "danger": $danger-border-subtle,
+  "light": $light-border-subtle,
+  "dark": $dark-border-subtle,
+) !default;
+// scss-docs-end theme-border-subtle-map
+
+$theme-colors-text-dark: null !default;
+$theme-colors-bg-subtle-dark: null !default;
+$theme-colors-border-subtle-dark: null !default;
+
+@if $enable-dark-mode {
+  // scss-docs-start theme-text-dark-map
+  $theme-colors-text-dark: (
+    "primary": $primary-text-emphasis-dark,
+    "secondary": $secondary-text-emphasis-dark,
+    "success": $success-text-emphasis-dark,
+    "info": $info-text-emphasis-dark,
+    "warning": $warning-text-emphasis-dark,
+    "danger": $danger-text-emphasis-dark,
+    "light": $light-text-emphasis-dark,
+    "dark": $dark-text-emphasis-dark,
+  ) !default;
+  // scss-docs-end theme-text-dark-map
+
+  // scss-docs-start theme-bg-subtle-dark-map
+  $theme-colors-bg-subtle-dark: (
+    "primary": $primary-bg-subtle-dark,
+    "secondary": $secondary-bg-subtle-dark,
+    "success": $success-bg-subtle-dark,
+    "info": $info-bg-subtle-dark,
+    "warning": $warning-bg-subtle-dark,
+    "danger": $danger-bg-subtle-dark,
+    "light": $light-bg-subtle-dark,
+    "dark": $dark-bg-subtle-dark,
+  ) !default;
+  // scss-docs-end theme-bg-subtle-dark-map
+
+  // scss-docs-start theme-border-subtle-dark-map
+  $theme-colors-border-subtle-dark: (
+    "primary": $primary-border-subtle-dark,
+    "secondary": $secondary-border-subtle-dark,
+    "success": $success-border-subtle-dark,
+    "info": $info-border-subtle-dark,
+    "warning": $warning-border-subtle-dark,
+    "danger": $danger-border-subtle-dark,
+    "light": $light-border-subtle-dark,
+    "dark": $dark-border-subtle-dark,
+  ) !default;
+  // scss-docs-end theme-border-subtle-dark-map
+}
+
+// Utilities maps
+//
+// Extends the default `$theme-colors` maps to help create our utilities.
+
+// Come v6, we'll de-dupe these variables. Until then, for backward compatibility, we keep them to reassign.
+// scss-docs-start utilities-colors
+$utilities-colors: $theme-colors-rgb !default;
+// scss-docs-end utilities-colors
+
+// scss-docs-start utilities-text-colors
+$utilities-text: map-merge(
+  $utilities-colors,
+  (
+    "black": to-rgb($black),
+    "white": to-rgb($white),
+    "body": to-rgb($body-color)
+  )
+) !default;
+$utilities-text-colors: map-loop($utilities-text, rgba-css-var, "$key", "text") !default;
+
+$utilities-text-emphasis-colors: (
+  "primary-emphasis": var(--#{$prefix}primary-text-emphasis),
+  "secondary-emphasis": var(--#{$prefix}secondary-text-emphasis),
+  "success-emphasis": var(--#{$prefix}success-text-emphasis),
+  "info-emphasis": var(--#{$prefix}info-text-emphasis),
+  "warning-emphasis": var(--#{$prefix}warning-text-emphasis),
+  "danger-emphasis": var(--#{$prefix}danger-text-emphasis),
+  "light-emphasis": var(--#{$prefix}light-text-emphasis),
+  "dark-emphasis": var(--#{$prefix}dark-text-emphasis)
+) !default;
+// scss-docs-end utilities-text-colors
+
+// scss-docs-start utilities-bg-colors
+$utilities-bg: map-merge(
+  $utilities-colors,
+  (
+    "black": to-rgb($black),
+    "white": to-rgb($white),
+    "body": to-rgb($body-bg)
+  )
+) !default;
+$utilities-bg-colors: map-loop($utilities-bg, rgba-css-var, "$key", "bg") !default;
+
+$utilities-bg-subtle: (
+  "primary-subtle": var(--#{$prefix}primary-bg-subtle),
+  "secondary-subtle": var(--#{$prefix}secondary-bg-subtle),
+  "success-subtle": var(--#{$prefix}success-bg-subtle),
+  "info-subtle": var(--#{$prefix}info-bg-subtle),
+  "warning-subtle": var(--#{$prefix}warning-bg-subtle),
+  "danger-subtle": var(--#{$prefix}danger-bg-subtle),
+  "light-subtle": var(--#{$prefix}light-bg-subtle),
+  "dark-subtle": var(--#{$prefix}dark-bg-subtle)
+) !default;
+// scss-docs-end utilities-bg-colors
+
+// scss-docs-start utilities-border-colors
+$utilities-border: map-merge(
+  $utilities-colors,
+  (
+    "black": to-rgb($black),
+    "white": to-rgb($white)
+  )
+) !default;
+$utilities-border-colors: map-loop($utilities-border, rgba-css-var, "$key", "border") !default;
+
+$utilities-border-subtle: (
+  "primary-subtle": var(--#{$prefix}primary-border-subtle),
+  "secondary-subtle": var(--#{$prefix}secondary-border-subtle),
+  "success-subtle": var(--#{$prefix}success-border-subtle),
+  "info-subtle": var(--#{$prefix}info-border-subtle),
+  "warning-subtle": var(--#{$prefix}warning-border-subtle),
+  "danger-subtle": var(--#{$prefix}danger-border-subtle),
+  "light-subtle": var(--#{$prefix}light-border-subtle),
+  "dark-subtle": var(--#{$prefix}dark-border-subtle)
+) !default;
+// scss-docs-end utilities-border-colors
+
+$utilities-links-underline: map-loop($utilities-colors, rgba-css-var, "$key", "link-underline") !default;
+
+$negative-spacers: if($enable-negative-margins, negativify-map($spacers), null) !default;
+
+$gutters: $spacers !default;

assets/scss/hotfix/_root.scss

@@ -0,0 +1,180 @@
+// Copied from https://github.com/twbs/bootstrap/commit/15744ee1d04bcca03155c3bb37ee7e65a7b011c6
+
+:root,
+[data-bs-theme="light"] {
+  // Note: Custom variable values only support SassScript inside `#{}`.
+
+  // Colors
+  //
+  // Generate palettes for full colors, grays, and theme colors.
+
+  @each $color, $value in $colors {
+    --#{$prefix}#{$color}: #{$value};
+  }
+
+  @each $color, $value in $grays {
+    --#{$prefix}gray-#{$color}: #{$value};
+  }
+
+  @each $color, $value in $theme-colors {
+    --#{$prefix}#{$color}: #{$value};
+  }
+
+  @each $color, $value in $theme-colors-rgb {
+    --#{$prefix}#{$color}-rgb: #{$value};
+  }
+
+  @each $color, $value in $theme-colors-text {
+    --#{$prefix}#{$color}-text-emphasis: #{$value};
+  }
+
+  @each $color, $value in $theme-colors-bg-subtle {
+    --#{$prefix}#{$color}-bg-subtle: #{$value};
+  }
+
+  @each $color, $value in $theme-colors-border-subtle {
+    --#{$prefix}#{$color}-border-subtle: #{$value};
+  }
+
+  --#{$prefix}white-rgb: #{to-rgb($white)};
+  --#{$prefix}black-rgb: #{to-rgb($black)};
+
+  // Fonts
+
+  // Note: Use `inspect` for lists so that quoted items keep the quotes.
+  // See https://github.com/sass/sass/issues/2383#issuecomment-336349172
+  --#{$prefix}font-sans-serif: #{inspect($font-family-sans-serif)};
+  --#{$prefix}font-monospace: #{inspect($font-family-monospace)};
+  --#{$prefix}gradient: #{$gradient};
+
+  // Root and body
+  // scss-docs-start root-body-variables
+  @if $font-size-root != null {
+    --#{$prefix}root-font-size: #{$font-size-root};
+  }
+  --#{$prefix}body-font-family: #{inspect($font-family-base)};
+  @include rfs($font-size-base, --#{$prefix}body-font-size);
+  --#{$prefix}body-font-weight: #{$font-weight-base};
+  --#{$prefix}body-line-height: #{$line-height-base};
+  @if $body-text-align != null {
+    --#{$prefix}body-text-align: #{$body-text-align};
+  }
+
+  --#{$prefix}body-color: #{$body-color};
+  --#{$prefix}body-color-rgb: #{to-rgb($body-color)};
+  --#{$prefix}body-bg: #{$body-bg};
+  --#{$prefix}body-bg-rgb: #{to-rgb($body-bg)};
+
+  --#{$prefix}emphasis-color: #{$body-emphasis-color};
+  --#{$prefix}emphasis-color-rgb: #{to-rgb($body-emphasis-color)};
+
+  --#{$prefix}secondary-color: #{$body-secondary-color};
+  --#{$prefix}secondary-color-rgb: #{to-rgb($body-secondary-color)};
+  --#{$prefix}secondary-bg: #{$body-secondary-bg};
+  --#{$prefix}secondary-bg-rgb: #{to-rgb($body-secondary-bg)};
+
+  --#{$prefix}tertiary-color: #{$body-tertiary-color};
+  --#{$prefix}tertiary-color-rgb: #{to-rgb($body-tertiary-color)};
+  --#{$prefix}tertiary-bg: #{$body-tertiary-bg};
+  --#{$prefix}tertiary-bg-rgb: #{to-rgb($body-tertiary-bg)};
+  // scss-docs-end root-body-variables
+
+  @if $headings-color != null {
+    --#{$prefix}heading-color: #{$headings-color};
+  }
+
+  --#{$prefix}link-color: #{$link-color};
+  --#{$prefix}link-color-rgb: #{to-rgb($link-color)};
+  --#{$prefix}link-decoration: #{$link-decoration};
+
+  --#{$prefix}link-hover-color: #{$link-hover-color};
+  --#{$prefix}link-hover-color-rgb: #{to-rgb($link-hover-color)};
+
+  @if $link-hover-decoration != null {
+    --#{$prefix}link-hover-decoration: #{$link-hover-decoration};
+  }
+
+  --#{$prefix}code-color: #{$code-color};
+  --#{$prefix}highlight-bg: #{$mark-bg};
+
+  // scss-docs-start root-border-var
+  --#{$prefix}border-width: #{$border-width};
+  --#{$prefix}border-style: #{$border-style};
+  --#{$prefix}border-color: #{$border-color};
+  --#{$prefix}border-color-translucent: #{$border-color-translucent};
+
+  --#{$prefix}border-radius: #{$border-radius};
+  --#{$prefix}border-radius-sm: #{$border-radius-sm};
+  --#{$prefix}border-radius-lg: #{$border-radius-lg};
+  --#{$prefix}border-radius-xl: #{$border-radius-xl};
+  --#{$prefix}border-radius-xxl: #{$border-radius-xxl};
+  --#{$prefix}border-radius-2xl: var(--#{$prefix}border-radius-xxl); // Deprecated in v5.3.0 for consistency
+  --#{$prefix}border-radius-pill: #{$border-radius-pill};
+  // scss-docs-end root-border-var
+
+  --#{$prefix}box-shadow: #{$box-shadow};
+  --#{$prefix}box-shadow-sm: #{$box-shadow-sm};
+  --#{$prefix}box-shadow-lg: #{$box-shadow-lg};
+  --#{$prefix}box-shadow-inset: #{$box-shadow-inset};
+
+  // Focus styles
+  // scss-docs-start root-focus-variables
+  --#{$prefix}focus-ring-width: #{$focus-ring-width};
+  --#{$prefix}focus-ring-opacity: #{$focus-ring-opacity};
+  --#{$prefix}focus-ring-color: #{$focus-ring-color};
+  // By default, there is no `--bs-focus-ring-x`, `--bs-focus-ring-y`, or `--bs-focus-ring-blur`, but we provide CSS variables with fallbacks to initial `0` values
+  --#{$prefix}focus-ring-box-shadow: var(--#{$prefix}focus-ring-x, 0) var(--#{$prefix}focus-ring-y, 0) var(--#{$prefix}focus-ring-blur, 0) var(--#{$prefix}focus-ring-width) var(--#{$prefix}focus-ring-color);
+  // scss-docs-end root-focus-variables
+}
+
+@if $enable-dark-mode {
+  @include color-mode(dark, true) {
+    color-scheme: dark;
+
+    // scss-docs-start root-dark-mode-vars
+    --#{$prefix}body-color: #{$body-color-dark};
+    --#{$prefix}body-color-rgb: #{to-rgb($body-color-dark)};
+    --#{$prefix}body-bg: #{$body-bg-dark};
+    --#{$prefix}body-bg-rgb: #{to-rgb($body-bg-dark)};
+
+    --#{$prefix}emphasis-color: #{$body-emphasis-color-dark};
+    --#{$prefix}emphasis-color-rgb: #{to-rgb($body-emphasis-color-dark)};
+
+    --#{$prefix}secondary-color: #{$body-secondary-color-dark};
+    --#{$prefix}secondary-color-rgb: #{to-rgb($body-secondary-color-dark)};
+    --#{$prefix}secondary-bg: #{$body-secondary-bg-dark};
+    --#{$prefix}secondary-bg-rgb: #{to-rgb($body-secondary-bg-dark)};
+
+    --#{$prefix}tertiary-color: #{$body-tertiary-color-dark};
+    --#{$prefix}tertiary-color-rgb: #{to-rgb($body-tertiary-color-dark)};
+    --#{$prefix}tertiary-bg: #{$body-tertiary-bg-dark};
+    --#{$prefix}tertiary-bg-rgb: #{to-rgb($body-tertiary-bg-dark)};
+
+    @each $color, $value in $theme-colors-text-dark {
+      --#{$prefix}#{$color}-text-emphasis: #{$value};
+    }
+
+    @each $color, $value in $theme-colors-bg-subtle-dark {
+      --#{$prefix}#{$color}-bg-subtle: #{$value};
+    }
+
+    @each $color, $value in $theme-colors-border-subtle-dark {
+      --#{$prefix}#{$color}-border-subtle: #{$value};
+    }
+
+    @if $headings-color-dark != null {
+      --#{$prefix}heading-color: #{$headings-color-dark};
+    }
+
+    --#{$prefix}link-color: #{$link-color-dark};
+    --#{$prefix}link-hover-color: #{$link-hover-color-dark};
+    --#{$prefix}link-color-rgb: #{to-rgb($link-color-dark)};
+    --#{$prefix}link-hover-color-rgb: #{to-rgb($link-hover-color-dark)};
+
+    --#{$prefix}code-color: #{$code-color-dark};
+
+    --#{$prefix}border-color: #{$border-color-dark};
+    --#{$prefix}border-color-translucent: #{$border-color-translucent-dark};
+    // scss-docs-end root-dark-mode-vars
+  }
+}

assets/scss/hotfix/_variables-dark.scss

@@ -0,0 +1,77 @@
+// Copied from https://github.com/twbs/bootstrap/pull/37953
+
+// Dark color mode variables
+//
+// Custom variables for the `[data-bs-theme="dark"]` theme. Use this as a starting point for your own custom color modes by creating a new theme-specific file like `_variables-dark.scss` and adding the variables you need.
+
+//
+// Global colors
+//
+
+// scss-docs-start sass-dark-mode-vars
+// scss-docs-start theme-text-dark-variables
+$primary-text-emphasis-dark:        tint-color($primary, 40%) !default;
+$secondary-text-emphasis-dark:      tint-color($secondary, 40%) !default;
+$success-text-emphasis-dark:        tint-color($success, 40%) !default;
+$info-text-emphasis-dark:           tint-color($info, 40%) !default;
+$warning-text-emphasis-dark:        tint-color($warning, 40%) !default;
+$danger-text-emphasis-dark:         tint-color($danger, 40%) !default;
+$light-text-emphasis-dark:          $gray-100 !default;
+$dark-text-emphasis-dark:           $gray-300 !default;
+// scss-docs-end theme-text-dark-variables
+
+// scss-docs-start theme-bg-subtle-dark-variables
+$primary-bg-subtle-dark:            shade-color($primary, 80%) !default;
+$secondary-bg-subtle-dark:          shade-color($secondary, 80%) !default;
+$success-bg-subtle-dark:            shade-color($success, 80%) !default;
+$info-bg-subtle-dark:               shade-color($info, 80%) !default;
+$warning-bg-subtle-dark:            shade-color($warning, 80%) !default;
+$danger-bg-subtle-dark:             shade-color($danger, 80%) !default;
+$light-bg-subtle-dark:              $gray-800 !default;
+$dark-bg-subtle-dark:               mix($gray-800, $black) !default;
+// scss-docs-end theme-bg-subtle-dark-variables
+
+// scss-docs-start theme-border-subtle-dark-variables
+$primary-border-subtle-dark:        shade-color($primary, 40%) !default;
+$secondary-border-subtle-dark:      shade-color($secondary, 40%) !default;
+$success-border-subtle-dark:        shade-color($success, 40%) !default;
+$info-border-subtle-dark:           shade-color($info, 40%) !default;
+$warning-border-subtle-dark:        shade-color($warning, 40%) !default;
+$danger-border-subtle-dark:         shade-color($danger, 40%) !default;
+$light-border-subtle-dark:          $gray-700 !default;
+$dark-border-subtle-dark:           $gray-800 !default;
+// scss-docs-end theme-border-subtle-dark-variables
+
+$body-color-dark:                   $gray-500 !default;
+$body-bg-dark:                      $gray-900 !default;
+$body-secondary-color-dark:         rgba($body-color-dark, .75) !default;
+$body-secondary-bg-dark:            $gray-800 !default;
+$body-tertiary-color-dark:          rgba($body-color-dark, .5) !default;
+$body-tertiary-bg-dark:             mix($gray-800, $gray-900, 50%) !default;
+$body-emphasis-color-dark:          $white !default;
+$border-color-dark:                 $gray-700 !default;
+$border-color-translucent-dark:     rgba($white, .15) !default;
+$headings-color-dark:               null !default;
+$link-color-dark:                   tint-color($primary, 40%) !default;
+$link-hover-color-dark:             shift-color($link-color-dark, -$link-shade-percentage) !default;
+$code-color-dark:                   tint-color($code-color, 40%) !default;
+
+
+//
+// Forms
+//
+
+$form-select-indicator-color-dark:  $body-color-dark !default;
+$form-select-indicator-dark:        url("data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16'><path fill='none' stroke='#{$form-select-indicator-color-dark}' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' d='m2 5 6 6 6-6'/></svg>") !default;
+
+$form-switch-color-dark:            rgba($white, .25) !default;
+$form-switch-bg-image-dark:         url("data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='-4 -4 8 8'><circle r='3' fill='#{$form-switch-color-dark}'/></svg>") !default;
+
+
+//
+// Accordion
+//
+
+$accordion-button-icon-dark:         url("data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16' fill='#{$primary-text-emphasis-dark}'><path fill-rule='evenodd' d='M1.646 4.646a.5.5 0 0 1 .708 0L8 10.293l5.646-5.647a.5.5 0 0 1 .708.708l-6 6a.5.5 0 0 1-.708 0l-6-6a.5.5 0 0 1 0-.708z'/></svg>") !default;
+$accordion-button-active-icon-dark:  url("data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16' fill='#{$primary-text-emphasis-dark}'><path fill-rule='evenodd' d='M1.646 4.646a.5.5 0 0 1 .708 0L8 10.293l5.646-5.647a.5.5 0 0 1 .708.708l-6 6a.5.5 0 0 1-.708 0l-6-6a.5.5 0 0 1 0-.708z'/></svg>") !default;
+// scss-docs-end sass-dark-mode-vars

assets/scss/theme.scss

@@ -0,0 +1,2 @@
+// Placeholder to quickly add your own styles
+// The file is included last in the build pipeline

config/_default/languages.toml

@@ -8,8 +8,6 @@
     [en.params.head]
         tagline = "A Hugo Theme"
     [en.params.feature]
-        message = "Welcome to Hinode!"
-        tagline = "A clean documentation and blog theme for your Hugo site based on Bootstrap 5."
         link = "/en/about"
         caption = "About"
     [en.params.footer]
@@ -25,8 +23,6 @@
     [nl.params.head]
         tagline = "Een Hugo Thema"
     [nl.params.feature]
-        message = "Welkom bij Hinode!"
-        tagline = "Een documentatie en blog thema voor Hugo gebaseerd op Bootstrap 5."
         link = "/nl/over-mij"
         caption = "Over mij"
     [nl.params.footer]

config/_default/menus/menus.en.toml

@@ -3,20 +3,15 @@
   url = "/about/"
   weight = 10
 
-[[main]]
-  name = "Docs"
-  url = "/docs/"
-  weight = 20
-
 [[main]]
   name = "Blog"
   url = "/blog/"
-  weight = 30
+  weight = 20
 
 [[main]]
   name = "Projects"
   url = "/projects/"
-  weight = 40
+  weight = 30
 
 [[main]]
   name = "Sample project"
@@ -33,7 +28,7 @@
 [[main]]
   name = "Tags"
   url = "/tags/"
-  weight = 50
+  weight = 40
 
 [[social]]
   name = "LinkedIn"

config/_default/menus/menus.nl.toml

@@ -13,6 +13,18 @@
   url = "/projecten/"
   weight = 30
 
+[[main]]
+  name = "Voorbeeldproject"
+  url = "/nl/projecten/voorbeeldproject/"
+  parent = "Projecten"
+  weight = 1
+
+[[main]]
+  name = "Ander project"
+  url = "/nl/projecten/ander-project/"
+  parent = "Projecten"
+  weight = 2
+
 [[main]]
   name = "Tags"
   url = "/tags/"
@@ -34,4 +46,28 @@
   name = "Medium"
   pre = "<i class=\"fab fa-medium fa-2x\"></i>"
   url = "https://medium.com/"
-  weight = 30
+  weight = 30
+
+# toml-docs-start sample-navigation
+[[sample]]
+  name = "Blog"
+  url = "/blog/"
+  weight = 10
+
+[[sample]]
+  name = "Projecten"
+  url = "/projecten/"
+  weight = 20
+
+[[sample]]
+  name = "Voorbeeldproject"
+  url = "/nl/projecten/voorbeeldproject/"
+  parent = "Projecten"
+  weight = 1
+
+[[sample]]
+  name = "Ander project"
+  url = "/nl/projecten/ander-project/"
+  parent = "Projecten"
+  weight = 2
+# toml-docs-end sample-navigation

config/_default/params.toml

@@ -2,11 +2,13 @@
 [main]
     separator = "-"
     description = "Hinode is a clean documentation and blog theme for your Hugo site based on Bootstrap 5."
+    enableDarkMode = true
 # toml-docs-end main
 
 # toml-docs-start docs
 [docs]
     version = "0.8"
+    basePath = ""
 # toml-docs-end docs
 
 # toml-docs-start home
@@ -14,13 +16,13 @@
     sections = ["blog", "projects"]
     featurePhoto = "/img/sunrise.jpg" # source: https://unsplash.com/photos/ZX6BPboJrYk
     fullCover = false
+    style = ""
 # toml-docs-end home
 
 # toml-docs-start navigation
 [navigation]
-    logo = "/img/logo_embedded.svg"
-    color = "white"
-    style = "light"
+    logo = "/img/logo_icon.svg"
+    color = "body"
     fixed = true
     offset = "4em"
     search = true
@@ -41,8 +43,9 @@
         header = "full"
         footer = "none"
         orientation = "stacked"
-        style = "border-0"
+        style = "border-0 card-zoom"
         homepage = 3
+        separator = true
     [projects]
         title = "Projects"
         sort = "title"
@@ -55,6 +58,7 @@
         orientation = "none"
         style = "border-1 card-emphasize"
         homepage = 3
+        separator = false
 # toml-docs-end list
 
 [favicon]
@@ -75,7 +79,8 @@
     themeOpacity = "10"
 # toml-docs-start font
     themeFont = "Inter"
-    themeFontPath = "https://fonts.googleapis.com/css2?family=Inter:wght@200;300;600&display=swap"
+    # themeFontPath = "https://fonts.googleapis.com/css2?family=Inter:wght@200;300;600&display=swap" # external path
+    themeFontPath = "/fonts" # local path
 # toml-docs-end font
 
 [schema]
@@ -114,78 +119,11 @@
     #theme = "" 
 
 [links]
-    azure = "https://azure.microsoft.com"
-    az_blob_domain = "https://learn.microsoft.com/en-us/azure/storage/blobs/storage-custom-domain-name"
-    az_blob_pricing = "https://azure.microsoft.com/en-us/free"
-    az_cdn_rules = "https://learn.microsoft.com/en-us/azure/cdn/cdn-standard-rules-engine-reference"
-    blist = "https://github.com/apvarun/blist-hugo-theme"
-    bootstrap = "https://getbootstrap.com"
     bs_badge_heading = "https://getbootstrap.com/docs/5.2/components/badge/#headings"
-    bs_breakpoints = "https://getbootstrap.com/docs/5.3/layout/breakpoints"
-    bs_grid = "https://getbootstrap.com/docs/5.3/layout/grid"
-    bs_offcanvas = "https://getbootstrap.com/docs/5.3/components/offcanvas"
-    bs_navbar_placement = "https://getbootstrap.com/docs/5.3/components/navbar/#placement"
-    bs_tables = "https://getbootstrap.com/docs/5.3/content/tables"
-    cc_by_nc_4_0 = "https://creativecommons.org/licenses/by-nc/4.0/"
-    commit_message = "https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html"
-    contrast_checker = "https://accessibleweb.com/color-contrast-checker/"
-    css_codeguide = "https://codeguide.co/#css"
-    doks = "https://github.com/h-enk/doks"
-    eslint = "https://eslint.org"
-    flexsearch = "https://github.com/nextapps-de/flexsearch"
-    fontawesome = "https://fontawesome.com"
-    fa_icons = "https://fontawesome.com/icons"
-    fa_styling = "https://fontawesome.com/docs/web/style/styling"
-    fa_animation = "https://fontawesome.com/docs/web/style/animate"
-    git_download = "https://git-scm.com"
-    github_pr = "https://help.github.com/articles/about-pull-requests/"
-    github_rebase = "https://help.github.com/articles/about-git-rebase/"
-    google_fonts = "https://fonts.google.com"
-    html_codeguide = "https://codeguide.co/#html"
-    hugo = "https://gohugo.io"
-    hugo_config = "https://gohugo.io/getting-started/configuration/#all-configuration-settings"
-    hugo_config_dir = "https://gohugo.io/getting-started/configuration/#configuration-directory"
-    hugo_content = "https://gohugo.io/content-management/formats"
-    hugo_chroma = "https://gohugo.io/content-management/syntax-highlighting/#list-of-chroma-highlighting-languages"
-    hugo_deploy = "https://gohugo.io/hosting-and-deployment/hugo-deploy"
-    hugo_deployment = "https://gohugo.io/hosting-and-deployment"
-    hugo_config_deploy = "https://gohugo.io/hosting-and-deployment/hugo-deploy/#configure-the-deployment"
-    hugo_fingerprint = "https://gohugo.io/hugo-pipes/fingerprint"
-    hugo_frontmatter = "https://gohugo.io/content-management/front-matter"
-    hugo_i18n = "https://gohugo.io/functions/i18n"
-    hugo_image = "https://gohugo.io/content-management/image-processing"
-    hugo_lang = "https://gohugo.io/content-management/multilingual"
-    hugo_lang_config = "https://gohugo.io/content-management/multilingual/#configure-languages"
-    hugo_links = "https://gohugo.io/content-management/cross-references"
-    hugo_menus = "https://gohugo.io/content-management/menus/"
-    hugo_mounts = "https://gohugo.io/hugo-modules/configuration/#module-config-mounts"
+    hinode_docs = "https://gethinode.com/docs"
     hugo_imaging = "https://gohugo.io/content-management/image-processing/#imaging-configuration"
-    hugo_ordering = "https://gohugo.io/templates/lists/#order-content"
-    hugo_templates = "https://gohugo.io/templates/introduction/"
-    hugo_toc = "https://gohugo.io/content-management/toc"
-    issue_tracker = "https://github.com/gethinode/hinode/issues"
-    license = "https://github.com/gethinode/hinode/blob/main/LICENSE"
-    markdown_emoji = "https://gist.github.com/rxaviers/7360908"
-    markdown_md013 = "https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md#md013---line-length"
-    markdown_md024 = "https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md#md024---multiple-headings-with-the-same-content"
-    markdown_md026 = "https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md#md026---trailing-punctuation-in-heading"
-    markdown_md033 = "https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md#md033---inline-html"
-    markdown_md034 = "https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md#md034---bare-url-used"
-    markdown_md051 = "https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md#md051---link-fragments-should-be-valid"
-    markdown_md053 = "https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md#md053---link-and-image-reference-definitions-should-be-needed"
-    markdown_rules = "https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md"
-    markdownlint = "https://github.com/DavidAnson/markdownlint-cli2"
     mozilla_image = "https://developer.mozilla.org/en-US/docs/Learn/HTML/Multimedia_and_embedding/Responsive_images"
-    netlify = "https://www.netlify.com"
-    nodejs = "https://nodejs.org"
-    npm = "https://www.npmjs.com"
     observatory = "https://observatory.mozilla.org/analyze/demo.gethinode.com"
-    package_npm = "https://www.npmjs.com/package/@gethinode/hinode"
     pagespeed = "https://pagespeed.web.dev/report?url=https%3A%2F%2Fdemo.gethinode.com%2F"
-    repository = "https://github.com/gethinode/hinode"
-    repository_child = "https://github.com/gethinode/child.git"
-    repository_owner = "https://github.com/gethinode/"
-    semver = "https://semver.org"
-    stylelint = "https://stylelint.io"
     utterances = "https://utteranc.es"
-    wcag_contrast = "https://www.w3.org/TR/WCAG20/#visual-audio-contrast"
+ 

config/_default/server.toml

@@ -32,6 +32,11 @@ for = '/**'
         fullscreen=(), \
         payment=() \
         """
-    Cache-Control = "public, max-age=31536000"
+    cache-control = """\
+        max-age=0, \
+        no-cache, \
+        no-store, \
+        must-revalidate \
+        """
     Access-Control-Allow-Origin = "*"
 # toml-docs-end server-config

config/postcss.config.js

@@ -1,47 +1,18 @@
-const autoprefixer = require('autoprefixer');
-const purgecss = require('@fullhuman/postcss-purgecss');
-const whitelister = require('purgecss-whitelister');
+const autoprefixer = require('autoprefixer')
+const cssnano = require('cssnano')
+// const purgecss = require('@fullhuman/postcss-purgecss')
 
 module.exports = {
   plugins: [
     autoprefixer(),
-    purgecss({
-      content: [
-        './layouts/**/*.html',
-        './content/**/*.md',
-      ],
-      safelist: [
-        /lazyloaded/,
-        /table/,
-        /thead/,
-        /tbody/,
-        /tr/,
-        /th/,
-        /td/,
-        /h5/,
-        /alert-link/,
-        /container-xxl/,
-        /container-fluid/,
-        /^bg-opacity-\d+/,
-        /svg.*/, 
-        /fa.*/,
-        /ratio.*/,
-        /suggestion.*/,
-        ...whitelister([
-          './assets/scss/components/_blockquote.scss',
-          './assets/scss/components/_buttons.scss',
-          './assets/scss/components/_card.scss',
-          './assets/scss/components/_clipboard.scss',
-          './assets/scss/components/_img.scss',
-          './assets/scss/components/_navbar.scss',
-          './assets/scss/components/_search.scss',
-          './assets/scss/components/_syntax.scss',
-          './assets/scss/layouts/_reboot.scss',
-          './assets/scss/layouts/type.scss',
-          './node_modules/bootstrap/scss/_dropdown.scss',
-          './node_modules/bootstrap/scss/_utilities.scss',
-        ]),
-      ],
-    }),
-  ],
+    cssnano({
+      preset: 'advanced'
+    })
+    // purgecss({
+    //   content: [
+    //     './layouts/**/*.html',
+    //     './content/**/*.md'
+    //   ]
+    // })
+  ]
 }

content/en/_index.md

@@ -1,4 +1,6 @@
 ---
 author: Mark Dumay
-title: A Clean Theme for Hugo
+title: Welcome to Hinode!
 ---
+
+A clean documentation and blog theme for your Hugo site based on Bootstrap 5.

content/en/about.md

@@ -2,11 +2,11 @@
 title: About
 description: Hinode is a clean documentation and blog theme for your Hugo site based on Bootstrap 5.
 date: 2022-04-11
-updated: 2023-01-14
+updated: 2023-02-11
 showComments: false
 ---
 
-<p class="text-center"><img src="/img/logo_embedded.svg" class="img-fluid w-50" alt="Logo"></p>
+<p class="text-center"><svg class="img-fluid w-50"><use href="/img/logo_var.svg#logo"></use></svg></p>
 
 <section class="section section-sm mt-5 mb-5">
     <div class="container-fluid">
@@ -32,6 +32,7 @@ showComments: false
 
 Additional features include:
 
+* Switching between light mode and dark mode
 * Support for multiple languages
 * Reusable Bootstrap components through configurable shortcodes and partials
 * Embedded comments through light-weight integration with GitHub via [utteranc.es]({{< param "links.utterances" >}})

content/en/blog/bootstrap-elements.md

@@ -0,0 +1,243 @@
+---
+author: Mark Dumay
+title: Bootstrap elements
+date: 2023-02-17
+description: Use shortcodes to add common Bootstrap elements with ease.
+tags: ["bootstrap", "shortcode"]
+thumbnail: img/boots.jpg
+photoCredits: <a href="https://unsplash.com/@nate_dumlao">Nathan Dumlao</a>
+photoSource: <a href="https://unsplash.com/photos/QLPWQvHvmII">Unsplash</a>
+---
+
+Hinode provides several shortcodes that wrap common Bootstrap components. Refer to the [official documentation]({{< param "links.hinode_docs" >}}) for more details.
+
+## Accordion
+
+As an example, the following shortcode displays an accordion with three elements, of which the first element is expanded.
+
+<!-- markdownlint-disable MD037 -->
+{{< example lang="hugo" >}}
+{{</* accordion */>}}
+  {{</* accordion-item header="Accordion Item #1" show="true" */>}}
+    This is the first item's accordion body. It supports HTML content. The item is shown by adding the value
+    <code>show</code> to the <code>class</code> argument.
+  {{</* /accordion-item */>}}
+  {{</* accordion-item header="Accordion Item #2" */>}}
+    This is the second item's accordion body. It supports HTML content too.
+  {{</* /accordion-item */>}}
+  {{</* accordion-item header="Accordion Item #3" */>}}
+    This is the third item's accordion body.
+  {{</* /accordion-item */>}}
+{{</* /accordion */>}}
+{{< /example >}}
+<!-- markdownlint-enable MD037 -->
+
+## Alert
+
+As an example, the following shortcode displays a simple alert.
+
+<!-- markdownlint-disable MD037 -->
+{{< example lang="hugo" >}}
+{{</* alert color="danger" dismissible="true" */>}}
+    A simple danger alert—check it out!
+{{</* /alert */>}}
+{{< /example >}}
+<!-- markdownlint-enable MD037 -->
+
+## Badge
+
+Use HTML code to display a badge for a heading. See the Bootstrap [documentation]({{< param "links.bs_badge_heading" >}}) for more options.
+
+{{< example >}}
+<h1>Example heading of size one <span class="badge bg-secondary">New</span></h1>
+<h2>Example heading of size two <span class="badge bg-secondary">New</span></h2>
+<h3>Example heading of size three <span class="badge bg-secondary">New</span></h3>
+<h4>Example heading of size four <span class="badge bg-secondary">New</span></h4>
+<h5>Example heading of size five <span class="badge bg-secondary">New</span></h5>
+<h6>Example heading of size six <span class="badge bg-secondary">New</span></h6>
+{{< /example >}}
+
+## Breadcrumb
+
+As an example, the following shortcode displays a breadcrumb for the blog page.
+
+<!-- markdownlint-disable MD037 -->
+{{< example lang="hugo" >}}
+{{</* breadcrumb path="blog" */>}}
+{{< /example >}}
+<!-- markdownlint-enable MD037 -->
+
+## Button
+
+As an example, the following shortcode displays a tooltip for a dark button with a badge.
+
+<!-- markdownlint-disable MD037 -->
+{{< example lang="hugo" >}}
+{{</* button color="secondary" tooltip="Click on the inbox to view your unread messages" href="#" badge="99+" */>}}
+    Inbox
+{{</* /button */>}}
+{{< /example>}}
+<!-- markdownlint-enable MD037 -->
+
+## Button group
+
+As an example, the following shortcode displays a group of three buttons.
+
+<!-- markdownlint-disable MD037 -->
+{{< example lang="hugo" >}}
+{{</* button-group aria-label="Basic example" */>}}
+  {{</* button color="primary" href="#" */>}}Left{{</* /button */>}}
+  {{</* button color="primary" href="#" */>}}Middle{{</* /button */>}}
+  {{</* button color="primary" href="#" */>}}Right{{</* /button */>}}
+{{</* /button-group */>}}
+{{< /example >}}
+<!-- markdownlint-enable MD037 -->
+
+## Card
+
+As an example, the following shortcode displays a stacked card with icon that links to the [about]({{< ref "about" >}}) page. It includes a custom header.
+
+<!-- markdownlint-disable MD037 -->
+{{< example lang="hugo" >}}
+{{</* card path="about" padding="3" class="w-50" color="light" header="publication" footer="none" */>}}
+{{< /example >}}
+<!-- markdownlint-enable MD037 -->
+
+## Carousel
+
+As an example, the following shortcode displays a centered carousel with three slides, 16x9 aspect ratio, and a relative width of 67% on large screens.
+
+<!-- markdownlint-disable MD037 -->
+{{< example lang="hugo" >}}
+{{</* carousel ratio="16x9" class="col-sm-12 col-lg-8 mx-auto" */>}}
+  {{</* img src="img/coffee.jpg" caption="slide 1" */>}}
+  {{</* img src="img/phone.jpg" caption="slide 2" */>}}
+  {{</* img src="img/dunes.jpg" caption="slide 3" */>}}
+{{</* /carousel */>}}
+{{< /example >}}
+<!-- markdownlint-enable MD037 -->
+
+## Collapse
+
+As an example, the following shortcode displays a button that, when clicked, triggers a panel to appear or disappear.
+
+<!-- markdownlint-disable MD037 -->
+{{< example lang="hugo" >}}
+{{</* button collapse="collapse-1" */>}}
+    Trigger panel
+{{</* /button */>}}
+
+{{</* collapse id="collapse-1" class="p-3 border rounded" */>}}
+    Some placeholder content for the collapse component. This panel is <i>hidden by default</i> but
+    revealed when the user activates the relevant trigger.
+{{</* /collapse */>}}
+{{< /example >}}
+<!-- markdownlint-enable MD037 -->
+
+## Command prompt
+
+Use the `command` shortcode to generate a block with a default bash command prompt.
+
+<!-- markdownlint-disable MD037 -->
+{{< example lang="hugo" >}}
+{{</* command */>}}
+export MY_VAR=123
+{{</* /command */>}}
+{{< /example >}}
+<!-- markdownlint-enable MD037 -->
+
+Specify `user` and `host` to add the user context to the prompt. In addition, use `(out)` to specify an output line and use `\` to denote a line continuation.
+
+<!-- markdownlint-disable MD037 -->
+{{< example lang="hugo" >}}
+{{</* command user="user" host="localhost" */>}}
+export MY_VAR=123
+echo "hello"
+(out)hello
+echo one \
+two \
+three
+(out)one two three
+echo "goodbye"
+(out)goodbye
+{{</* /command */>}}
+{{< /example >}}
+<!-- markdownlint-enable MD037 -->
+
+## Docs
+
+Use the `docs` shortcode to display the content of a `toml` or `scss` file:
+
+{{< docs name="theme-colors" file="config/_default/params.toml" >}}
+
+## Icon
+
+As an example, the following shortcodes show a square check, a brand logo, and a circle check.
+
+<!-- markdownlint-disable MD037 -->
+{{< example lang="hugo" >}}
+{{</* fa square-check */>}}
+{{</* fab linkedin */>}}
+{{</* fas circle-check */>}}
+{{< /example >}}
+<!-- markdownlint-enable MD037 -->
+
+## Image
+
+As an example, the following shortcode displays an image with rounded corners and a 21x9 aspect ratio.
+
+<!-- markdownlint-disable MD037 -->
+{{< example lang="hugo" >}}
+{{</* image src="img/flowers.jpg" ratio="21x9" caption="Figure caption" class="rounded" */>}}
+{{< /example >}}
+<!-- markdownlint-enable MD037 -->
+
+## Navbar
+
+As an example, the following shortcode displays a light navigation header.
+
+<!-- markdownlint-disable MD037 -->
+{{< example lang="hugo" >}}
+{{</* navbar path="about" color="primary" size="sm" search="false" menus="sample" title="Brand" */>}}
+{{< /example >}}
+<!-- markdownlint-enable MD037 -->
+
+## Spinner
+
+As an example, the following shortcode displays a centered spinner.
+
+<!-- markdownlint-disable MD037 -->
+{{< example lang="hugo" >}}
+{{</* spinner color="info" class="text-center" */>}}
+Loading...
+{{</* /spinner */>}}
+{{< /example>}}
+<!-- markdownlint-enable MD037 -->
+
+## Toast
+
+As an example, the following shortcode displays a button that, when clicked, triggers the toast message.
+
+<!-- markdownlint-disable MD037 -->
+{{< example lang="hugo" >}}
+{{</* button id="toastButton" */>}}
+    Show toast
+{{</* /button */>}}
+
+{{</* toast header="Custom title" */>}}
+    This is a toast message.
+{{</* /toast */>}}
+{{< /example >}}
+<!-- markdownlint-enable MD037 -->
+
+## Tooltip
+
+As an example, the following shortcode displays a tooltip for a colored hyperlink.
+
+<!-- markdownlint-disable MD037 -->
+{{< example lang="hugo" >}}
+{{</* tooltip color="primary" title="Tooltip" href="#" */>}}
+    Tooltip demonstration
+{{</* /tooltip */>}}
+{{< /example >}}
+<!-- markdownlint-enable MD037 -->

content/en/blog/code-highlighting.md

@@ -1,58 +0,0 @@
----
-author: "Mark Dumay"
-title: "Code Highlighting"
-date: 2022-04-16
-description: "Examples on how to enable code highlighting."
-tags: ["code"]
-thumbnail: img/notepad.jpg
-photoCredits: <a href="https://unsplash.com/@frederickjmedina">Frederick Medina</a>
-photoSource: <a href="https://unsplash.com/photos/PdfRE-xB--s">Unsplash</a>
----
-
-## Code Fencing
-
-Use code fencing to highlight the syntax of a specific language.
-
-```json
-{
-  "version": "0.2.0",
-  "themes": [],
-  "projects": [],
-  "configuration": {}
-}
-```
-
-```html
-<div class="highlight">
-    <pre>
-        <code>some code...</code>
-    </pre>
-</div>
-```
-
-## Highlight Shortcode
-
-Use the `highlight` shortcode to customize the layout of a specific code block.
-
-{{< highlight go "linenos=table,hl_lines=8 15-17,linenostart=199" >}}
-// GetTitleFunc returns a func that can be used to transform a string to
-// title case.
-//
-// The supported styles are
-//
-// - "Go" (strings.Title)
-// - "AP" (see https://www.apstylebook.com/)
-// - "Chicago" (see https://www.chicagomanualofstyle.org/home.html)
-//
-// If an unknown or empty style is provided, AP style is what you get.
-func GetTitleFunc(style string) func(s string) string {
-  switch strings.ToLower(style) {
-  case "go":
-    return strings.Title
-  case "chicago":
-    return transform.NewTitleConverter(transform.ChicagoStyle)
-  default:
-    return transform.NewTitleConverter(transform.APStyle)
-  }
-}
-{{< / highlight >}}

content/en/blog/emoji-support.md

@@ -1,24 +0,0 @@
----
-author: "Hugo Authors"
-title: "Emoji Support"
-date: 2021-07-15
-description: "Guide to emoji usage in Hugo."
-tags: ["emoji"]
-# thumbnail: img/dunes.jpg
-thumbnail: https://picsum.photos/id/184/4288/2848.jpg
-photoCredits: <a href="https://unsplash.com/@timdegroot">Tim de Groot</a>
-photoSource: <a href="https://unsplash.com/photos/yNGQ830uFB4">Unsplash</a>
----
-
-Emoji can be enabled in a Hugo project in a number of ways.
-
-<!--more-->
-
-The [`emojify`](https://gohugo.io/functions/emojify/) function can be called directly in templates or [Inline Shortcodes](https://gohugo.io/templates/shortcode-templates/#inline-shortcodes).
-
-To enable emoji globally, set `enableEmoji` to `true` in your site's [configuration](https://gohugo.io/getting-started/configuration/) and then you can type emoji shorthand codes directly in content files; e.g.
-
-<p><span class="nowrap"><span class="emojify">🙈</span> <code>:see_no_evil:</code></span>  <span class="nowrap"><span class="emojify">🙉</span> <code>:hear_no_evil:</code></span>  <span class="nowrap"><span class="emojify">🙊</span> <code>:speak_no_evil:</code></span></p>
-<br>
-
-The [Emoji cheat sheet](http://www.emoji-cheat-sheet.com/) is a useful reference for emoji shorthand codes.

content/en/blog/first-post.md

@@ -0,0 +1,14 @@
+---
+author: Mark Dumay
+title: First post
+date: 2022-10-01
+description: This is my first blog post.
+tags: ["blog"]
+thumbnail: img/notepad.jpg
+photoCredits: <a href="https://unsplash.com/@frederickjmedina">Frederick Medina</a>
+photoSource: <a href="https://unsplash.com/photos/PdfRE-xB--s">Unsplash</a>
+---
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque vulputate, ante in luctus congue, leo risus semper justo, vel consequat sapien lectus quis ipsum. In imperdiet urna justo. Nulla vel pellentesque ipsum. Cras congue feugiat dolor ac aliquam. Pellentesque eget dui venenatis, ultrices urna ac, vehicula nibh. Curabitur est lectus, dapibus eu vehicula non, malesuada et dui. Nam enim nulla, egestas et nunc non, elementum aliquet justo. Mauris euismod mauris sapien, eget vestibulum odio dictum sit amet. Morbi nisl elit, placerat at auctor in, finibus ac neque. Curabitur placerat feugiat risus non vestibulum. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque quis cursus est, nec posuere libero.
+
+In ac lobortis diam. Curabitur id dui ac nunc mattis rhoncus a sed lorem. Sed lobortis sem turpis, at posuere enim dignissim et. Vivamus fermentum justo quis volutpat volutpat. Proin eget vehicula neque, ut tempus urna. Duis ac ex vel leo pharetra lobortis et vitae lacus. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia curae; Aliquam erat volutpat. Suspendisse ullamcorper ultrices elementum. Suspendisse mi elit, commodo at varius a, cursus a ligula. Sed et mattis elit, eu luctus arcu. Cras a porttitor libero. Vestibulum tincidunt sed magna at dapibus. Sed quis orci eu lacus aliquam tristique. Integer porttitor ultrices ipsum quis porttitor. Etiam a sodales ligula.

content/en/blog/fourth-post.md

@@ -0,0 +1,16 @@
+---
+author: Mark Dumay
+title: Fourth post
+date: 2023-01-01
+description: This is my fourth blog post.
+tags: ["blog"]
+thumbnail: img/flowers.jpg # https://picsum.photos/id/106/2592/1728
+photoCredits: <a href="https://unsplash.com/@flutterhappy">Arvee Marie</a>
+photoSource: <a href="https://unsplash.com/photos/YnfGtpt2gf4">Unsplash</a>
+---
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam finibus libero in felis accumsan, vitae imperdiet metus vehicula. Quisque nec dignissim purus. In id dui porta sapien posuere viverra nec vel nisi. Sed varius tincidunt lectus, quis sagittis felis interdum id. Proin purus odio, ultrices auctor libero convallis, volutpat gravida turpis. Ut commodo metus orci, quis sagittis lectus rhoncus non. Nulla et lectus tortor. Suspendisse quam felis, molestie non odio quis, consequat venenatis orci. Etiam sed turpis sit amet elit scelerisque imperdiet. Sed suscipit felis non nibh suscipit egestas. Nulla sodales libero non rhoncus consequat. Nunc in elit at est cursus congue ut ac velit. Cras luctus libero augue, id semper sapien volutpat ultrices.
+
+Pellentesque sit amet sollicitudin nibh. Cras in dolor eget quam feugiat ultricies in ac lectus. Ut venenatis vitae justo quis pretium. Pellentesque vulputate nulla ac est iaculis vulputate. Proin pellentesque sem nec molestie imperdiet. Duis eu molestie sapien, vel ultricies lacus. Donec in felis tempus, rutrum ipsum at, fermentum felis. Praesent mi odio, semper non vulputate vitae, vulputate quis ex.
+
+Nunc rhoncus eleifend gravida. Aliquam feugiat tristique pellentesque. Pellentesque vel elit sed nulla commodo convallis. Curabitur placerat sapien augue, ac semper metus volutpat non. Sed semper ultricies enim, consequat convallis justo placerat eget. Ut fermentum leo facilisis metus congue commodo. Vestibulum consectetur magna vitae ullamcorper sodales. Nulla lobortis aliquam odio id tincidunt. Suspendisse efficitur auctor tortor non consequat. Quisque sit amet posuere lorem, convallis bibendum nisi. Proin ullamcorper justo tempus dignissim scelerisque. Quisque sit amet sapien libero. Phasellus eget enim velit. Proin ut fermentum dui. Proin gravida tortor in ligula lacinia, id dapibus dui tincidunt. Mauris suscipit nisi et urna consectetur, non venenatis nisi euismod.

content/en/blog/markdown-syntax.md

@@ -1,165 +0,0 @@
----
-author: Hugo Authors
-title: Markdown Syntax Guide
-description: Use Markdown syntax and basic HTML elements to style your Hugo content files.
-tags: ["markdown", "css", "html"]
-date: 2022-01-14
-thumbnail: img/phone.jpg # https://picsum.photos/id/160/3200/2119
-photoCredits: <a href="https://unsplash.com/@thomweerd">Thom</a> 
-photoSource: <a href="https://unsplash.com/photos/Zdcq3iKly6g">Unsplash</a>
----
-
-This article offers a sample of basic Markdown syntax that can be used in Hugo content files, also it shows whether basic HTML elements are decorated with CSS in a Hugo theme.
-
-<!--more-->
-
-## Headings
-
-The following HTML `<h1>`—`<h6>` elements represent six levels of section headings. `<h1>` is the highest section level while `<h6>` is the lowest.
-
-<!-- markdownlint-disable-next-line -->
-# H1
-
-## H2
-
-### H3
-
-#### H4
-
-##### H5
-
-###### H6
-
-## Paragraph
-
-Xerum, quo qui aut unt expliquam qui dolut labo. Aque venitatiusda cum, voluptionse latur sitiae dolessi aut parist aut dollo enim qui voluptate ma dolestendit peritin re plis aut quas inctum laceat est volestemque commosa as cus endigna tectur, offic to cor sequas etum rerum idem sintibus eiur? Quianimin porecus evelectur, cum que nis nust voloribus ratem aut omnimi, sitatur? Quiatem. Nam, omnis sum am facea corem alique molestrunt et eos evelece arcillit ut aut eos eos nus, sin conecerem erum fuga. Ri oditatquam, ad quibus unda veliamenimin cusam et facea ipsamus es exerum sitate dolores editium rerore eost, temped molorro ratiae volorro te reribus dolorer sperchicium faceata tiustia prat.
-
-Itatur? Quiatae cullecum rem ent aut odis in re eossequodi nonsequ idebis ne sapicia is sinveli squiatum, core et que aut hariosam ex eat.
-
-## Blockquotes
-
-The blockquote element represents content that is quoted from another source, optionally with a citation which must be within a `footer` or `cite` element, and optionally with in-line changes such as annotations and abbreviations.
-
-### Blockquote without attribution
-
-> Tiam, ad mint andaepu dandae nostion secatur sequo quae.
-> **Note** that you can use _Markdown syntax_ within a blockquote.
-{.blockquote}
-
-### Blockquote with attribution
-
-> Don't communicate by sharing memory, share memory by communicating.<br>
-> — <cite>Rob Pike[^1]</cite>
-{.blockquote}
-
-[^1]: The above quote is excerpted from Rob Pike's [talk](https://www.youtube.com/watch?v=PAAkCSZUG1c) during Gopherfest, November 18, 2015.
-
-<figure>
-  <blockquote class="blockquote">
-    <p>A well-known quote, contained in a blockquote element.</p>
-  </blockquote>
-  <figcaption class="blockquote-footer">
-    Someone famous in <cite title="Source Title">Source Title</cite>
-  </figcaption>
-</figure>
-
-## Tables
-
-Tables aren't part of the core Markdown spec, but Hugo supports supports them out-of-the-box.
-
-| Name  | Age |
-| ----- | --- |
-| Bob   | 27  |
-| Alice | 23  |
-{.table}
-
-### Inline Markdown within tables
-
-| Italics   | Bold     | Code   |
-| --------- | -------- | ------ |
-| _italics_ | **bold** | `code` |
-{.table}
-
-## Code Blocks
-
-### Code block with backticks
-
-```html
-<!DOCTYPE html>
-<html lang="en">
-  <head>
-    <meta charset="utf-8">
-    <title>Example HTML5 Document</title>
-  </head>
-  <body>
-    <p>Test</p>
-  </body>
-</html>
-```
-
-<!-- markdownlint-disable MD046 -->
-### Code block indented with four spaces
-
-    <!doctype html>
-    <html lang="en">
-    <head>
-      <meta charset="utf-8">
-      <title>Example HTML5 Document</title>
-    </head>
-    <body>
-      <p>Test</p>
-    </body>
-    </html>
-<!-- markdownlint-enable MD046 -->
-
-### Code block with Hugo's internal highlight shortcode
-
-{{< highlight html >}}
-
-<!doctype html>
-<html lang="en">
-<head>
-  <meta charset="utf-8">
-  <title>Example HTML5 Document</title>
-</head>
-<body>
-  <p>Test</p>
-</body>
-</html>
-{{< /highlight >}}
-
-## List Types
-
-### Ordered List
-
-1. First item
-2. Second item
-3. Third item
-
-### Unordered List
-
-- List item
-- Another item
-- And another item
-
-### Nested list
-
-- Fruit
-  - Apple
-  - Orange
-  - Banana
-- Dairy
-  - Milk
-  - Cheese
-
-## Other Elements — abbr, sub, sup, kbd, mark
-
-<abbr title="Graphics Interchange Format">GIF</abbr> is a bitmap image format.
-
-H<sub>2</sub>O
-
-X<sup>n</sup> + Y<sup>n</sup> = Z<sup>n</sup>
-
-Press <kbd><kbd>CTRL</kbd>+<kbd>ALT</kbd>+<kbd>Delete</kbd></kbd> to end the session.
-
-Most <mark>salamanders</mark> are nocturnal, and hunt for insects, worms, and other small creatures.

content/en/blog/rich-content.md

@@ -1,34 +0,0 @@
----
-author: "Hugo Authors"
-title: "Rich Content"
-date: 2021-07-13
-description: "A brief description of Hugo Shortcodes."
-tags: ["shortcode", "privacy"]
-thumbnail: img/flowers.jpg # https://picsum.photos/id/106/2592/1728
-photoCredits: <a href="https://unsplash.com/@flutterhappy">Arvee Marie</a>
-photoSource: <a href="https://unsplash.com/photos/YnfGtpt2gf4">Unsplash</a>
----
-
-Hugo ships with several [Built-in Shortcodes](https://gohugo.io/content-management/shortcodes/#use-hugos-built-in-shortcodes) for rich content, along with a [Privacy Config](https://gohugo.io/about/hugo-and-gdpr/) and a set of Simple Shortcodes that enable static and no-JS versions of various social media embeds.
-
-## <!--more-->
-
-## YouTube Privacy Enhanced Shortcode
-
-{{< youtube id="ZJthWmvUzzc" class="video">}}
-
-<br>
-
----
-
-## Twitter Simple Shortcode
-
-{{< twitter_simple user="SanDiegoZoo" id="1453110110599868418" >}}
-
-<br>
-
----
-
-## Vimeo Simple Shortcode
-
-{{< vimeo_simple id="48912912" class="__h_video" >}}

content/en/blog/second-post.md

@@ -0,0 +1,16 @@
+---
+author: Mark Dumay
+title: Second post
+date: 2022-11-01
+description: This is my second blog post.
+tags: ["blog"]
+thumbnail: img/phone.jpg # https://picsum.photos/id/160/3200/2119
+photoCredits: <a href="https://unsplash.com/@thomweerd">Thom</a> 
+photoSource: <a href="https://unsplash.com/photos/Zdcq3iKly6g">Unsplash</a>
+---
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed non sollicitudin sapien. Ut porttitor lectus eu tempor ultricies. Sed semper tincidunt nibh pellentesque condimentum. Vivamus dictum sem eu rhoncus semper. Vestibulum convallis congue tincidunt. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia curae; Mauris magna urna, egestas sit amet ligula quis, viverra semper arcu. Praesent laoreet nunc vitae nulla posuere facilisis.
+
+Nunc eget dignissim ex, sed lobortis leo. Suspendisse mollis posuere tellus, in viverra nunc ullamcorper vitae. Nam vel tempor arcu, in imperdiet odio. Fusce malesuada vehicula odio, in iaculis nulla congue eget. Quisque id odio id nisl facilisis posuere porta sit amet mauris. Curabitur lorem leo, tempus id rhoncus eget, placerat vitae lectus. Morbi eu aliquet enim. Nulla malesuada laoreet sodales.
+
+Nunc volutpat dui in elit euismod, sed egestas purus tristique. Nam in condimentum mauris. Praesent nec suscipit enim. Aliquam dolor ipsum, faucibus vitae purus ac, congue egestas nisi. Donec hendrerit erat eu arcu porttitor rhoncus. Nunc a odio bibendum metus semper pellentesque. Sed at sapien ut est semper eleifend. Aliquam lorem libero, porttitor nec tristique ut, auctor vitae ipsum. Suspendisse pretium pharetra rutrum. Nulla tincidunt tempus enim eu sagittis. Maecenas pulvinar metus a urna mattis dictum sed id tellus.

content/en/blog/third-post.md

@@ -0,0 +1,16 @@
+---
+author: Mark Dumay
+title: Third post
+date: 2022-12-01
+description: This is my third blog post.
+tags: ["blog"]
+thumbnail: https://picsum.photos/id/184/4288/2848.jpg
+photoCredits: <a href="https://unsplash.com/@timdegroot">Tim de Groot</a>
+photoSource: <a href="https://unsplash.com/photos/yNGQ830uFB4">Unsplash</a>
+---
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Praesent id scelerisque ligula. Vestibulum eu lorem tortor. Suspendisse tristique ultrices mauris, non maximus lorem faucibus in. Suspendisse sagittis eleifend dapibus. Curabitur dignissim luctus sapien eu consequat. Proin congue dui vel ipsum bibendum varius. Pellentesque cursus nisi metus, egestas eleifend ipsum sollicitudin vitae. Sed vitae erat elementum, semper turpis sed, molestie nulla.
+
+Nulla molestie ultrices vehicula. Etiam iaculis, erat a blandit blandit, nulla tellus dapibus ligula, vitae venenatis turpis diam non felis. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed vitae arcu in justo iaculis egestas. In imperdiet arcu vitae pharetra commodo. Quisque ut erat eget nisl semper laoreet vitae eget ligula. Mauris bibendum purus nec vulputate faucibus. In luctus sagittis ante, quis laoreet orci bibendum vitae. Nam at odio accumsan, tincidunt eros at, lacinia metus. In et ultricies sapien, a mollis est. Nunc convallis orci eu tristique euismod. Proin vel ullamcorper diam. Quisque et semper orci. Proin pharetra lorem justo, id malesuada erat feugiat sit amet. Praesent bibendum mi at lorem volutpat suscipit. Morbi sed libero elit.
+
+Nunc sodales est eu ipsum volutpat, in mollis dui facilisis. Nulla faucibus interdum lectus, a condimentum elit vulputate eu. Nunc ipsum risus, suscipit sit amet nulla ac, pulvinar maximus nulla. In venenatis diam erat, non elementum ante dignissim posuere. Aliquam sem justo, luctus at vestibulum ut, egestas ut quam. Quisque a dolor viverra, aliquam nunc vel, lacinia nulla. In id magna magna. Morbi dapibus pretium sollicitudin. Morbi volutpat augue at felis tristique, quis euismod tellus vulputate. Morbi dui lacus, aliquam eget quam vel, vestibulum faucibus enim. Proin porta pretium metus id venenatis. Aliquam nec tempor lorem. Vivamus euismod est varius sagittis placerat. Maecenas tincidunt elementum libero, at imperdiet elit feugiat vel.

content/en/docs/0.8/about/credits.md

@@ -1,26 +0,0 @@
----
-title: Credits
-description: Hinode is fully open source and uses several open-source frameworks and libraries.
-date: "2023-01-14"
-group: about
-layout: docs
----
-
-## Team
-
-Hinode is maintained by [Mark Dumay]({{< param "links.repository_owner" >}}) and several contributors as an open-source repository on GitHub. You are more than welcome to contribute. Get involved in the development by [opening an issue]({{< param "links.issue_tracker" >}}) or submitting a pull request. Read our [contributing guidelines]({{< ref "contribute" >}}) for information on how we develop.
-
-## Core components
-
-Hinode is based on the following core components:
-
-- [Hugo]({{< param "links.hugo" >}}) is a fast and modern static site generator written in Go. It is a so-called static site generator, meaning that the website is created when you update its content. This is a different approach to systems that dynamically build a page upon request.
-- [Bootstrap]({{< param "links.bootstrap" >}}) is a popular, open-source web development framework. Using a mobile-first approach, it provides several functions and components to simplify the creation of responsive websites.
-- [npm]({{< param "links.npm" >}}) is a software registry that enables the sharing and reuse of both open-source and private software packages. By taking advantage of its version management, software dependencies are easily tracked and updated.
-
-## Themes
-
-Hinode is inspired by the following themes:
-
-- [Blist]({{< param "links.blist" >}}) is a clean and fast blog theme for your Hugo site using Tailwind CSS.
-- [Doks]({{< param "links.doks" >}}) is a Hugo theme for building secure, fast, and SEO-ready documentation websites, which you can easily update and customize.

content/en/docs/0.8/about/license.md

@@ -1,15 +0,0 @@
----
-title: License
-description: Hinode's open-source license for the codebase and documentation.
-date: "2023-01-14"
-group: about
-layout: docs
----
-
-## Codebase
-
-The codebase of Hinode is open source under the conditions of the [MIT license]({{< param "links.license" >}}) and is copyright &copy; 2023 by Mark Dumay. In short, the MIT license allows you to use the Hinode codebase for both personal and commercial use, as long as you include the original license and copyright notice. Licensed works, modifications, and larger works may be distributed under different terms and without source code. No liability or warranty is given.
-
-## Documentation
-
-The documentation of Hinode is licensed under the Creative Commons ([CC BY-NC 4.0)]({{< param "links.cc_by_nc_4_0" >}}) license. This includes all files within the repository's `/content` folder and its children, as well as the "README" in the repository root. The license allows you to share and adapt the materials, as long as you give appropriate credit and do not use the materials for commercial purposes. No warranties are given.

content/en/docs/0.8/advanced-settings/icons.md

@@ -1,67 +0,0 @@
----
-title: Icons
-description: Configure secure access to icons from Bootstrap and Font Awesome.
-date: 2023-01-28
-group: advanced-settings
-layout: docs
----
-
-Hinode processes the Bootstrap icons to ensure they adhere to the strict [content security policy]({{< ref "server" >}}). In addition, it provides access to the free icons of [Font Awesome]({{< param "links.fontawesome" >}}).
-
-## Bootstrap icons
-
-Bootstrap uses various embedded vector images (in <abbr title="Scalable Vector Graphics">SVG</abbr> format) throughout its Sass source files. Hinode replaces these embedded images with file-based vector images, as the [content security policy]({{< ref "server" >}}) prohibits loading of embedded images. To ensure the images are consistent with the [theme colors]({{< ref "colors" >}}), the images are postprocessed using [Hugo templating]({{< param "links.hugo_templates">}}).
-
-### Build pipeline
-
-Hinodes uses npm and mounted folders to create a flexibile virtual file system that is automatically kept up to date. Review the [overview]({{< ref "overview" >}}) for a detailed explanation. The build pipeline of the Bootstrap icons consists of four steps. It is intertwined with the [build process for the stylesheets]({{< ref "styles" >}}).
-
-1. Override the inline Bootstrap icon definitions
-
-   Replace the default inline icon definitions within the Bootstrap Sass files with references to local vector images. Use the file `assets/scss/common/_icons.scss` to ensure the definitions take precedence over the default Bootstrap values. For example, the following statement updates the value of the `$form-switch-focus-bg-image`:
-
-   ```scss
-   $form-switch-focus-bg-image: url("icons/form-switch-focus-bg-image.svg") !default;
-   ```
-
-2. Export the Sass variables
-
-   Export the required Sass variables by defining them in the `assets/scss/common/_export.scss` file. Hinode converts the variable names from kebab case to snake case to make them compatible with Hugo's variable naming convention. For example, the css variable `--form-switch-focus-color` is exposed as `.form_switch_focus_color` to the Hugo templates.
-
-   ```scss
-   :hinode-theme {
-       --form-switch-focus-color: #{$form-switch-focus-color};
-   }
-   ```
-
-3. Reference the Sass variables within each icon file
-
-   Use [Hugo templating]({{< param "links.hugo_templates">}}) to reference the Sass variables for fill colors and stroke colors. For example, the file `assets/icons/form-switch-focus-bg-image.svg` defines the fill color as `{{ .form_switch_focus_color }}`. The entire vector definition is as such:
-
-   ```html
-   <svg xmlns='http://www.w3.org/2000/svg' viewBox='-4 -4 8 8'>
-       <circle r='3' fill='{{ .form_switch_focus_color }}'/>
-   </svg>
-   ```
-
-4. Process the icon files
-
-   Add the local icon files to the `assets/icons` folder with a filename as defined in step 1. The partial `partials/head/stylesheet.html` calls the partial `partials/head/icons.html` to process all icon files with the `.svg` extension recursively. The output is stored in the `icons` folder within the output directory (usually `public` when building the site). The icon files are referenced in the main stylesheet automatically.
-
-### Icons definitions
-
-The icons are defined in the file `assets/scss/common/_icons.scss`. The current configuration is the following:
-
-{{< docs name="icons" file="assets/scss/common/_icons.scss" >}}
-
-### Export definitions
-
-The exported variables are defined in the file `assets/scss/common/_export.scss`. The current configuration is the following:
-
-{{< docs name="export" file="assets/scss/common/_export.scss" >}}
-
-## Font Awesome icons
-
-[Font Awesome]({{< param "links.fontawesome" >}}) provides a collection of icons to be used freely on websites and other media. See the [icons documentation]({{< relref "../content/icons" >}}) in the content section on how to use them to style your website. Hinode uses the <abbr title="Cascading Style Sheets">CSS</abbr> files and web fonts of Font Awesome, as the [content security policy]({{< ref "server" >}}) prohibits the inline execution of stylesheets by the JavaScripts of Font Awesome. The CSS files are bundled with the main stylesheet. The web fonts are copied to the `/static/fonts` folder with the repository. Use the npm command `npm run copy:fonts` to copy the latest version of the files. The CSS files are referenced in the `assets/scss/app.scss` file. This is the current configuration:
-
-{{< docs name="awesome" file="assets/scss/app.scss" >}}

content/en/docs/0.8/advanced-settings/overview.md

@@ -1,66 +0,0 @@
----
-title: Overview
-description: Configure and customize Hinode to your liking using Hugo Templating and npm dependencies.
-date: 2023-01-28
-group: advanced-settings
-layout: docs
----
-
-As a theme for Hugo, Hinode is highly configurable and customizable. Based on Go's template libraries, Hugo enriches plain Markdown content with powerful features to generate websites. More information is available in [Hugo's documentation]({{< param "links.hugo_templates" >}}). To take advantage of package versioning and dependency management, Hinode takes a slightly different approach compared to most themes. The below paragraphs clarify the build system.
-
-## npm packages
-
-Both the [main theme]({{< param "links.repository" >}}) and [child theme]({{< param "links.repository_child" >}}) packages of Hinode are defined in the file `package.json` in the repository root. The extract below defines the key elements of the package configuration. The `name` is a unique identifier to identify the [package on npm]({{< param "links.package_npm" >}}). The `version` tag uses [semantic versioning]({{< param "links.semver" >}}), consisting of a `MAJOR` version, `MINOR` version, and `PATCH` version. In short, anything below `MAJOR` version `1` is considered to be in development and may not be backwards compatible. Starting from `1`, each `MAJOR` version may introduce breaking changes, whilst `MINOR` version usually introduce new features that are compatible with the `MAJOR` version. Lastly, `PATCH` usually indicates a bug fix or small revision.
-
-The other two sections of interest are `devDependencies` and `otherDependencies`. As an Hugo theme, Hinode does not require any packages in production. Instead the development dependencies are used to generate the static site and its assets. For example, Bootstrap's JavaScript distribution file `/node_modules/bootstrap/dist/js` is bundled into the `js/main.bundle<.min>.js` file during build. The path `/node_modules/bootstrap/` refers to the Bootstap package defined as dependency. Lastly, the Hugo binary is installed as version-controlled dependency too. This ensures the build process is transparent and traceable, which simplifies debugging. Please refer to the [commands]({{< ref "commands" >}}) section to review the various npm commands available.
-
-```yml
-{
-    "name": "@gethinode/hinode",
-    "version": "0.8.0",
-    "scripts": {
-        [...]
-    },
-    [...]
-    "devDependencies": {
-        "bootstrap": "^5.2.3",
-        [...]
-    },
-    "otherDependencies": {
-        "hugo": "0.110.0"
-    }
-}
-```
-
-## Mounted folders
-
-Hugo supports the [mounting of folders]({{< param "links.hugo_mounts" >}}) since version 0.56.0. Hinode takes advantage of this feature to create a virtual file system, combining assets from multiple sources. For example, the below section of the `/config/_default/config.toml` instructs Hugo to make Bootstrap's JavaScript distribution file `/node_modules/bootstrap/dist/js` available in the `/assets/js` folder. This file is then bundled with the JavaScript files defined in the `/assets/js` folder of Hinode.
-
-{{< alert color="primary" >}}
-    When you add a mount, the default mount for the concerned target root is ignored: be sure to explicitly add it.
-{{< /alert >}}
-
-```toml
-[module]
-    [...]
-    [[module.mounts]]
-        source = "assets"
-        target = "assets"
-    [[module.mounts]]
-        source = "node_modules/bootstrap/dist/js"
-        target = "assets/js/vendor/bootstrap"
-        includeFiles = "*.bundle.js"
-```
-
-As another example, the Hinode child theme merges the key folders of the main theme with its own folder. This simplifies the modification of any base files, as the files in the local repository take precedence over the files of the main theme.
-
-```toml
-[module]
-    [...]
-    [[module.mounts]]
-        source = "node_modules/@gethinode/hinode/i18n"
-        target = "i18n"
-    [[module.mounts]]
-        source = "i18n"
-        target = "i18n"  
-```

content/en/docs/0.8/advanced-settings/scripts.md

@@ -1,35 +0,0 @@
----
-title: Scripts
-description: Automatically bundle local and external JavaScript files into a single file.
-date: 2023-01-28
-group: advanced-settings
-layout: docs
----
-
-Hinode bundles local and external JavaScript into a single file. By utilizing [npm]({{< ref "overview" >}}), external JavaScript files are automatically ingested and kept up to date.
-
-## Build pipeline
-
-Hinodes uses npm and mounted folders to create a flexibile virtual file system that is automatically kept up to date. Review the [overview]({{< ref "overview" >}}) for a detailed explanation. The build pipeline of the JavaScript files consists of four steps.
-
-1. Add the local JavaScript files
-
-   Add the local JavaScript files to the `assets/js` folder with a recognizable filename.
-
-2. Mount the JavaScript files maintained within a node package
-
-   Make JavaScripts defined in node packages available by mounting them into the `assets/js/vendor` folder. Define the mount points in `config/_default/config.toml`.
-
-3. Bundle the JavaScript files
-
-   The partial `partials/footer/scripts.html` bundles all files that end with `.js` recursively into a single file called `js/main.bundle.js`. In production mode, the output is minified and linked to with a [fingerprint]({{< param "links.hugo_fingerprint" >}}).
-
-4. Link to the JavaScript in the base layout
-
-   Hinode's base layout `layouts/_default/baseof.html` imports the bundled JavaScript file in the footer. The file is cached to improve performance.
-
-## Example
-
-Mount the external JavaScript files to Hugo's virtual file system within the file `config/_default/config.toml`. The current configuration imports the relevant files of [Bootstrap]({{< param "links.bootstrap" >}}) and [FlexSearch]({{< param "links.flexsearch" >}}).
-
-{{< docs name="javascript" file="config/_default/config.toml" >}}

content/en/docs/0.8/advanced-settings/server.md

@@ -1,15 +0,0 @@
----
-title: Server
-description: Configure the server headers to refine the content security policy.
-date: 2023-01-28
-group: advanced-settings
-layout: docs
----
-
-<!-- TODO: expand -->
-
-## Server headers
-
-Hinode uses rather strict security policies by default. This ensures the site is [secure by default]({{< param "links.observatory" >}}). However, if you want to include external resources, such as images and videos, you will need to explicity add these sources to the server headers. If omitted, the browser will refuse to load these resources, resulting in broken links or missing elements. The settings of the local development server are defined in `server.toml`. See the below configuration, which captures the external resources currently used by Hinode. Refine these settings as needed. Similar settings are defined in the `netlify.toml` file provided in the repository's root when deploying to [Netlify]({{< param "links.netlify" >}}).
-
-{{< docs name="server-config" file="config/_default/server.toml" >}}

content/en/docs/0.8/advanced-settings/styles.md

@@ -1,59 +0,0 @@
----
-title: Styles
-description: Use extensible Sass files to generate the stylesheets for your website.
-date: 2023-01-28
-group: advanced-settings
-layout: docs
----
-
-<!-- TODO: include dartsass -->
-
-Hinode uses Sass files to take advantage of variables, maps, and functions to generate the cascading style sheets of the website. By utilizing [npm]({{< ref "overview" >}}), Bootstrap's source Sass file are automatically ingested and kept up to date.
-
-## Build pipeline
-
-Hinodes uses npm and mounted folders to create a flexibile virtual file system that is automatically kept up to date. Review the [overview]({{< ref "overview" >}}) for a detailed explanation. The build pipeline of the stylesheet consists of five steps.
-
-1. Define the Sass entrypoint
-
-   The main entrypoint for the Sass files is defined in `assets/scss/app.scss`. It supports Hugo templating. For example, it defines a variable `$themeFont` that links to the [font configuration]({{< ref "fonts" >}}). The variable is available within all source Sass files.
-
-2. Import the source Sass files
-
-   The application entrypoint imports the various source Sass files defined in `assets/scss`, which are combined with the Sass files of [Bootstrap]({{< param "links.bootstrap" >}}) and [Font Awesome (Free)]({{< param "links.fontawesome" >}}). The vendor paths are relative to the `node_modules` folder, which are installed by [npm]({{< ref "commands" >}}).
-
-3. Override and expand the Sass configuration
-
-   The import order of the source files defines which variables and functions to use. In Sass, the first definition of a variable or function takes precedence. For example, to override the setting for the variable `$primary`, is needs to be defined prior to Bootstrap's definition in `_variables.scss`.
-
-4. Transpile the Sass files
-
-   The partial `partials/head/stylesheet.html` reads the application entrypoint, configures the `node_modules` folder as import path, and transpiles the stylesheet into a single file `main.css`. In production mode, the output is minified and linked to with a [fingerprint]({{< param "links.hugo_fingerprint" >}}).
-
-5. Link to the stylesheet in the base layout
-
-   Hinode's base layout `layouts/_default/baseof.html` imports the generated stylesheet in the header section of the webpage via the partial `layouts/partials/head/head.html`.
-
-## Example
-
-The below Sass file defines a skeleton configuration for the main entrypoint. The full configuration is defined in `assets/scss/app.scss`.
-
-```scss
-// 1) Define template variables (linking to Hugo config)
-$primary:  {{ site.Params.style.primary | default "#007bff" }};
-
-// 2) Include default variable overrides
-@import "common/variables.scss";
-
-// 3) Import Bootstrap configuration
-@import "bootstrap/scss/variables";
-
-// 4) Import Bootstrap layout & components
-@import "bootstrap/scss/root";
-
-// 5) Import Font Awesome
-@import "@fortawesome/fontawesome-free/scss/fontawesome";
-
-// 6) Import Hinode theme styles
-@import "common/styles.scss";
-```

content/en/docs/0.8/components/_bootstrap.md

@@ -1,338 +0,0 @@
----
-author: "Mark Dumay"
-title: "Bootstrap Components"
-date: 2022-12-26
-draft: true
-description: "Overview of available Bootstrap components."
-tags: ["bootstrap"]
-thumbnail: img/boots.jpg
-photoCredits: <a href="https://unsplash.com/@nate_dumlao">Nathan Dumlao</a>
-photoSource: <a href="https://unsplash.com/photos/QLPWQvHvmII">Unsplash</a>
-layout: docs
----
-
-
-## Close button
-
-Use HTML code to display a generic close button. See the Bootstrap [documentation][bs_close_button] for more options. The following example displays a button with default styling.
-
-```html
-<button type="button" class="btn-close" aria-label="Close"></button>
-```
-
-The result looks like this.
-
-<button type="button" class="btn-close" aria-label="Close"></button>
-
-## Dropdowns
-
-### Single button
-
-<div class="dropdown">
-  <button class="btn btn-secondary dropdown-toggle" type="button" data-bs-toggle="dropdown" aria-expanded="false">
-    Dropdown button
-  </button>
-  <ul class="dropdown-menu">
-    <li><a class="dropdown-item" href="#">Action</a></li>
-    <li><a class="dropdown-item" href="#">Another action</a></li>
-    <li><a class="dropdown-item" href="#">Something else here</a></li>
-  </ul>
-</div>
-
-### Split button
-
-<!-- Example split danger button -->
-<div class="btn-group">
-  <button type="button" class="btn btn-danger">Action</button>
-  <button type="button" class="btn btn-danger dropdown-toggle dropdown-toggle-split" data-bs-toggle="dropdown" aria-expanded="false">
-    <span class="visually-hidden">Toggle Dropdown</span>
-  </button>
-  <ul class="dropdown-menu">
-    <li><a class="dropdown-item" href="#">Action</a></li>
-    <li><a class="dropdown-item" href="#">Another action</a></li>
-    <li><a class="dropdown-item" href="#">Something else here</a></li>
-    <li><hr class="dropdown-divider"></li>
-    <li><a class="dropdown-item" href="#">Separated link</a></li>
-  </ul>
-</div>
-
-## List group
-
-<div class="list-group">
-  <a href="#" class="list-group-item list-group-item-action active" aria-current="true">
-    The current link item
-  </a>
-  <a href="#" class="list-group-item list-group-item-action">A second link item</a>
-  <a href="#" class="list-group-item list-group-item-action">A third link item</a>
-  <a href="#" class="list-group-item list-group-item-action">A fourth link item</a>
-  <a class="list-group-item list-group-item-action disabled">A disabled link item</a>
-</div>
-
-## Modal
-
-<!-- Button trigger modal -->
-<button type="button" class="btn btn-primary" data-bs-toggle="modal" data-bs-target="#exampleModal">
-  Launch demo modal
-</button>
-
-<!-- Modal -->
-<div class="modal fade" id="exampleModal" tabindex="-1" aria-labelledby="exampleModalLabel" aria-hidden="true">
-  <div class="modal-dialog">
-    <div class="modal-content">
-      <div class="modal-header">
-        <h1 class="modal-title fs-5" id="exampleModalLabel">Modal title</h1>
-        <button type="button" class="btn-close" data-bs-dismiss="modal" aria-label="Close"></button>
-      </div>
-      <div class="modal-body">
-        ...
-      </div>
-      <div class="modal-footer">
-        <button type="button" class="btn btn-secondary" data-bs-dismiss="modal">Close</button>
-        <button type="button" class="btn btn-primary">Save changes</button>
-      </div>
-    </div>
-  </div>
-</div>
-
-## Navs & tabs
-
-<ul class="nav nav-tabs">
-  <li class="nav-item">
-    <a class="nav-link active" aria-current="page" href="#">Active</a>
-  </li>
-  <li class="nav-item">
-    <a class="nav-link" href="#">Link</a>
-  </li>
-  <li class="nav-item">
-    <a class="nav-link" href="#">Link</a>
-  </li>
-  <li class="nav-item">
-    <a class="nav-link disabled">Disabled</a>
-  </li>
-</ul>
-
-## Offcanvas
-
-<a class="btn btn-primary" data-bs-toggle="offcanvas" href="#offcanvasExample" role="button" aria-controls="offcanvasExample">
-  Link with href
-</a>
-<button class="btn btn-primary" type="button" data-bs-toggle="offcanvas" data-bs-target="#offcanvasExample" aria-controls="offcanvasExample">
-  Button with data-bs-target
-</button>
-
-<div class="offcanvas offcanvas-start" tabindex="-1" id="offcanvasExample" aria-labelledby="offcanvasExampleLabel">
-  <div class="offcanvas-header">
-    <h5 class="offcanvas-title" id="offcanvasExampleLabel">Offcanvas</h5>
-    <button type="button" class="btn-close" data-bs-dismiss="offcanvas" aria-label="Close"></button>
-  </div>
-  <div class="offcanvas-body">
-    <div>
-      Some text as placeholder. In real life you can have the elements you have chosen. Like, text, images, lists, etc.
-    </div>
-    <div class="dropdown mt-3">
-      <button class="btn btn-secondary dropdown-toggle" type="button" data-bs-toggle="dropdown">
-        Dropdown button
-      </button>
-      <ul class="dropdown-menu">
-        <li><a class="dropdown-item" href="#">Action</a></li>
-        <li><a class="dropdown-item" href="#">Another action</a></li>
-        <li><a class="dropdown-item" href="#">Something else here</a></li>
-      </ul>
-    </div>
-  </div>
-</div>
-
-## Pagination
-
-<nav aria-label="Page navigation example">
-  <ul class="pagination justify-content-center">
-    <li class="page-item disabled">
-      <a class="page-link">Previous</a>
-    </li>
-    <li class="page-item"><a class="page-link" href="#">1</a></li>
-    <li class="page-item"><a class="page-link" href="#">2</a></li>
-    <li class="page-item"><a class="page-link" href="#">3</a></li>
-    <li class="page-item">
-      <a class="page-link" href="#">Next</a>
-    </li>
-  </ul>
-</nav>
-
-## Placeholders
-
-<div class="card w-50" aria-hidden="true">
-  <img src="/img/bd_placeholder_img.svg" class="card-img-top" alt="...">
-  <div class="card-body">
-    <h5 class="card-title placeholder-glow">
-      <span class="placeholder col-6"></span>
-    </h5>
-    <p class="card-text placeholder-glow">
-      <span class="placeholder col-7"></span>
-      <span class="placeholder col-4"></span>
-      <span class="placeholder col-4"></span>
-      <span class="placeholder col-6"></span>
-      <span class="placeholder col-8"></span>
-    </p>
-    <a href="#" tabindex="-1" class="btn btn-primary disabled placeholder col-6"></a>
-  </div>
-</div>
-
-## Popovers
-
-<button type="button" class="btn btn-lg btn-danger" data-bs-toggle="popover" data-bs-title="Popover title" data-bs-content="And here's some amazing content. It's very engaging. Right?">Click to toggle popover</button>
-
-## Progress
-
-<div class="progress">
-  <div class="progress-bar progress-bar-striped progress-bar-animated w-75" role="progressbar" aria-label="Animated striped example" aria-valuenow="75" aria-valuemin="0" aria-valuemax="100"></div>
-</div>
-
-## Scrollspy
-
-### Navbar
-
-<nav id="navbar-example2" class="navbar bg-light px-3 mb-3">
-  <a class="navbar-brand" href="#">Navbar</a>
-  <ul class="nav nav-pills">
-    <li class="nav-item">
-      <a class="nav-link" href="#scrollspyHeading1">First</a>
-    </li>
-    <li class="nav-item">
-      <a class="nav-link" href="#scrollspyHeading2">Second</a>
-    </li>
-    <li class="nav-item dropdown">
-      <a class="nav-link dropdown-toggle" data-bs-toggle="dropdown" href="#" role="button" aria-expanded="false">Dropdown</a>
-      <ul class="dropdown-menu">
-        <li><a class="dropdown-item" href="#scrollspyHeading3">Third</a></li>
-        <li><a class="dropdown-item" href="#scrollspyHeading4">Fourth</a></li>
-        <li><hr class="dropdown-divider"></li>
-        <li><a class="dropdown-item" href="#scrollspyHeading5">Fifth</a></li>
-      </ul>
-    </li>
-  </ul>
-</nav>
-<div data-bs-spy="scroll" data-bs-target="#navbar-example2" data-bs-root-margin="0px 0px -40%" data-bs-smooth-scroll="true" class="scrollspy-example bg-light p-3 rounded-2" tabindex="0">
-  <h4 id="scrollspyHeading1">First heading</h4>
-  <p>...</p>
-  <h4 id="scrollspyHeading2">Second heading</h4>
-  <p>...</p>
-  <h4 id="scrollspyHeading3">Third heading</h4>
-  <p>...</p>
-  <h4 id="scrollspyHeading4">Fourth heading</h4>
-  <p>...</p>
-  <h4 id="scrollspyHeading5">Fifth heading</h4>
-  <p>...</p>
-</div>
-
-### Nested nav
-
-<div class="row">
-  <div class="col-4">
-    <nav id="navbar-example3" class="h-100 flex-column align-items-stretch pe-4 border-end">
-      <nav class="nav nav-pills flex-column">
-        <a class="nav-link" href="#item-1">Item 1</a>
-        <nav class="nav nav-pills flex-column">
-          <a class="nav-link ms-3 my-1" href="#item-1-1">Item 1-1</a>
-          <a class="nav-link ms-3 my-1" href="#item-1-2">Item 1-2</a>
-        </nav>
-        <a class="nav-link" href="#item-2">Item 2</a>
-        <a class="nav-link" href="#item-3">Item 3</a>
-        <nav class="nav nav-pills flex-column">
-          <a class="nav-link ms-3 my-1" href="#item-3-1">Item 3-1</a>
-          <a class="nav-link ms-3 my-1" href="#item-3-2">Item 3-2</a>
-        </nav>
-      </nav>
-    </nav>
-  </div>
-
-  <div class="col-8">
-    <div data-bs-spy="scroll" data-bs-target="#navbar-example3" data-bs-smooth-scroll="true" class="scrollspy-example-2" tabindex="0">
-      <div id="item-1">
-        <h4>Item 1</h4>
-        <p>...</p>
-      </div>
-      <div id="item-1-1">
-        <h5>Item 1-1</h5>
-        <p>...</p>
-      </div>
-      <div id="item-1-2">
-        <h5>Item 1-2</h5>
-        <p>...</p>
-      </div>
-      <div id="item-2">
-        <h4>Item 2</h4>
-        <p>...</p>
-      </div>
-      <div id="item-3">
-        <h4>Item 3</h4>
-        <p>...</p>
-      </div>
-      <div id="item-3-1">
-        <h5>Item 3-1</h5>
-        <p>...</p>
-      </div>
-      <div id="item-3-2">
-        <h5>Item 3-2</h5>
-        <p>...</p>
-      </div>
-    </div>
-  </div>
-</div>
-
-### List group
-
-<div class="row">
-  <div class="col-4">
-    <div id="list-example" class="list-group">
-      <a class="list-group-item list-group-item-action" href="#list-item-1">Item 1</a>
-      <a class="list-group-item list-group-item-action" href="#list-item-2">Item 2</a>
-      <a class="list-group-item list-group-item-action" href="#list-item-3">Item 3</a>
-      <a class="list-group-item list-group-item-action" href="#list-item-4">Item 4</a>
-    </div>
-  </div>
-  <div class="col-8">
-    <div data-bs-spy="scroll" data-bs-target="#list-example" data-bs-smooth-scroll="true" class="scrollspy-example" tabindex="0">
-      <h4 id="list-item-1">Item 1</h4>
-      <p>...</p>
-      <h4 id="list-item-2">Item 2</h4>
-      <p>...</p>
-      <h4 id="list-item-3">Item 3</h4>
-      <p>...</p>
-      <h4 id="list-item-4">Item 4</h4>
-      <p>...</p>
-    </div>
-  </div>
-</div>
-
-### Simple anchors
-
-<!-- TODO: fix Simple anchors -->
-
-<div class="row">
-  <div class="col-4">
-    <div id="simple-list-example" class="d-flex flex-column gap-2 simple-list-example-scrollspy text-center">
-      <a class="p-1 rounded" href="#simple-list-item-1">Item 1</a>
-      <a class="p-1 rounded" href="#simple-list-item-2">Item 2</a>
-      <a class="p-1 rounded" href="#simple-list-item-3">Item 3</a>
-      <a class="p-1 rounded" href="#simple-list-item-4">Item 4</a>
-      <a class="p-1 rounded" href="#simple-list-item-5">Item 5</a>
-    </div>
-  </div>
-  <div class="col-8">
-    <div data-bs-spy="scroll" data-bs-target="#simple-list-example" data-bs-offset="0" data-bs-smooth-scroll="true" class="scrollspy-example" tabindex="0">
-      <h4 id="simple-list-item-1">Item 1</h4>
-      <p>...</p>
-      <h4 id="simple-list-item-2">Item 2</h4>
-      <p>...</p>
-      <h4 id="simple-list-item-3">Item 3</h4>
-      <p>...</p>
-      <h4 id="simple-list-item-4">Item 4</h4>
-      <p>...</p>
-      <h4 id="simple-list-item-5">Item 5</h4>
-      <p>...</p>
-    </div>
-  </div>
-</div>
-
-<!-- MARKDOWN PUBLIC LINKS -->
-[bs_close_button]: https://getbootstrap.com/docs/5.2/components/close-button/

content/en/docs/0.8/components/accordion.md

@@ -1,51 +0,0 @@
----
-author: Mark Dumay
-title: Accordion
-date: 2023-01-28
-description: Use the accordion shortcode to show a group of vertically collapsing and expanding items.
-group: components
-layout: docs
----
-
-## Overview
-
-Use the `accordion` shortcode to show a group of vertically collapsing and expanding items. Add `accordion-item` inner elements for each accordion item.
-
-## Arguments
-
-The shortcode supports the following arguments:
-
-| Argument    | Required | Description |
-|-------------|----------|-------------|
-| class       | No  | Optional class attribute of the accordion element, e.g. “w-50”. |
-{.table}
-
-Add an inner `accordion-item` element for each item of the accordion. The `accordion-item` element supports the following arguments:
-
-| Argument  | Required | Description |
-|-----------|----------|-------------|
-| header      | Yes | Required header of the accordion element. |
-| class       | No  | Optional class attribute of the inner accordion element. |
-| show        | No  | Optional flag to indicate an item should be shown as collapsed. |
-{.table}
-
-## Example
-
-As an example, the following shortcode displays an accordion with three elements, of which the first element is expanded.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* accordion */>}}
-  {{</* accordion-item header="Accordion Item #1" show="true" */>}}
-    This is the first item's accordion body. It supports HTML content. The item is shown by adding the value
-    <code>show</code> to the <code>class</code> argument.
-  {{</* /accordion-item */>}}
-  {{</* accordion-item header="Accordion Item #2" */>}}
-    This is the second item's accordion body. It too supports HTML content.
-  {{</* /accordion-item */>}}
-  {{</* accordion-item header="Accordion Item #3" */>}}
-    This is the third item's accordion body.
-  {{</* /accordion-item */>}}
-{{</* /accordion */>}}
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->

content/en/docs/0.8/components/alert.md

@@ -1,34 +0,0 @@
----
-author: Mark Dumay
-title: Alert
-date: 2023-01-28
-description: Use the alert shortcode to display a contextual feedback message.
-group: components
-layout: docs
----
-
-## Overview
-
-Use the `alert` shortcode to display a contextual feedback message. The inner content is used as alert text.
-
-## Arguments
-
-The shortcode supports the following arguments:
-
-| Argument    | Required | Description |
-|-------------|----------|-------------|
-| color       | No  | Optional theme color of the alert, either "primary" (default), "secondary", "success", "danger",  "warning", "info", "light", "dark", "white" or "black". |
-| dismissible | No  | Optional flag to indicate the alert is dismissible, defaults to false. |
-{.table}
-
-## Example
-
-As an example, the following shortcode displays a simple alert.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* alert color="danger" */>}}
-    A simple danger alert—check it out!
-{{</* /alert */>}}
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->

content/en/docs/0.8/components/badge.md

@@ -1,29 +0,0 @@
----
-author: Mark Dumay
-title: Badge
-date: 2023-01-28
-description: Use the badge to enrich headings and buttons.
-group: components
-layout: docs
----
-
-## Overview
-
-Badges can be added to headings and buttons. The badge for a button is part of a [custom shortcode]({{< ref "button" >}} "custom shortcode"). The example below illustrates the HTML code for a heading.
-
-## Arguments
-
-The shortcode requires no arguments.
-
-## Example
-
-Use HTML code to display a badge for a heading. See the Bootstrap [documentation]({{< param "links.bs_badge_heading" >}}) for more options. The following example displays a badge for a heading of size four.
-
-{{< example >}}
-<h1>Example heading of size one <span class="badge bg-secondary">New</span></h1>
-<h2>Example heading of size two <span class="badge bg-secondary">New</span></h2>
-<h3>Example heading of size three <span class="badge bg-secondary">New</span></h3>
-<h4>Example heading of size four <span class="badge bg-secondary">New</span></h4>
-<h5>Example heading of size five <span class="badge bg-secondary">New</span></h5>
-<h6>Example heading of size six <span class="badge bg-secondary">New</span></h6>
-{{< /example >}}

content/en/docs/0.8/components/breadcrumb.md

@@ -1,31 +0,0 @@
----
-author: Mark Dumay
-title: Breadcrumb
-date: 2023-01-28
-description: Use the breadcrumb shortcode to display the current page’s location within the site's navigational hierarchy.
-group: components
-layout: docs
----
-
-## Overview
-
-Use the `breadcrumb` shortcode to display the current page’s location within the site's navigational hierarchy.
-
-## Arguments
-
-The shortcode supports the following arguments:
-
-| Argument    | Required | Description |
-|-------------|----------|-------------|
-| path        | No       | Optional path of the page, defaults to current page.
-{.table}
-
-## Example
-
-As an example, the following shortcode displays a breadcrumb for the current page.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* breadcrumb path="breadcrumb" */>}}
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->

content/en/docs/0.8/components/button-group.md

@@ -1,35 +0,0 @@
----
-author: Mark Dumay
-title: Button Group
-date: 2023-01-28
-description: Use the button-group shortcode to display a group of buttons.
-group: components
-layout: docs
----
-
-## Overview
-
-Use the `button-group` shortcode to display a group of buttons. Add inner `<button>` elements for each [button]({{< ref "button" >}} "button").
-
-## Arguments
-
-The shortcode supports the following arguments:
-
-| Argument    | Required | Description |
-|-------------|----------|-------------|
-| aria-label  | No   | Optional assistive label for the button group. |
-{.table}
-
-## Example
-
-As an example, the following shortcode displays a group of three buttons.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* button-group aria-label="Basic example" */>}}
-  {{</* button color="primary" href="#" */>}}Left{{</* /button */>}}
-  {{</* button color="primary" href="#" */>}}Middle{{</* /button */>}}
-  {{</* button color="primary" href="#" */>}}Right{{</* /button */>}}
-{{</* /button-group */>}}
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->

content/en/docs/0.8/components/button.md

@@ -1,42 +0,0 @@
----
-author: Mark Dumay
-title: Button
-date: 2023-01-28
-description: Use the button shortcode to display a button with a hyperlink.
-group: components
-layout: docs
----
-
-## Overview
-
-Use the `button` shortcode to display a button with a hyperlink. The inner content is used as button title. The button supports an optional badge and tooltip.
-
-## Arguments
-
-The shortcode supports the following arguments:
-
-| Argument    | Required | Description |
-|-------------|----------|-------------|
-| href        | No   | Optional address for the button or hyperlink. Automatically assigned when using collapse. |
-| state       | No   | Optional state of the button, either "enabled" (default), "disabled", "active", or "inactive". |
-| size        | No   | Optional size of the button, either "sm", "md" (default), or "lg". |
-| color       | No   | Optional theme color of the element, either "primary" (default), "secondary", "success", "danger",  "warning", "info", "light", "dark", "white" or "black". |
-| badge       | No   | Optional positioned badge to display on top of the button. |
-| outline     | No   | Optional flag indicating the button should be outlined, either "false" (default) or "true". |
-| aria-label  | No   | Optional label for the badge. |
-| tooltip     | No   |  Optional text to display in a tooltip. Cannot be used together with collapse. Ignored for active/inactive buttons. |
-| collapse    | No   | Optional panel to collapse. Cannot be used together with tooltip. Ignored for active/inactive buttons. |
-| placement   | No   | How to position the tooltip: "top" (default), "bottom", "left", or "right". |
-{.table}
-
-## Example
-
-As an example, the following shortcode displays a tooltip for a dark button with a badge.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* button color="dark" tooltip="Click on the inbox to view your unread messages" href="#" badge="99+" */>}}
-    Inbox
-{{</* /button */>}}
-{{< /example>}}
-<!-- markdownlint-enable MD037 -->

content/en/docs/0.8/components/card.md

@@ -1,37 +0,0 @@
----
-author: Mark Dumay
-title: Card
-date: 2023-01-28
-description: Use the card shortcode to display a card that links to a content page.
-group: components
-layout: docs
----
-
-## Overview
-
-Use the `card` shortcode to display a card that links to a content page. When using a rich layout, the card includes a thumbnail and a header.
-
-## Arguments
-
-The shortcode supports the following arguments:
-
-| Argument    | Required | Description |
-|-------------|----------|-------------|
-| path        | Yes | Required path of the page. |
-| class       | No  | Optional class attribute of the card element, e.g. “w-50”. |
-| color       | No  | Optional theme color of the card, either "primary", "secondary", "success", "danger", "warning", "info", "light", "dark", "white" or "black". By default, no color is specified. |
-| padding     | No  | Optional padding of the content, either "0", "1", "2", "3", "4", "5", or "auto" (default). |
-| header      | No  | Optional header components of the card, displayed in small caps. Supported values are "full" (default), "publication", "tags", and "none". |
-| footer      | No  | Optional footer components of the card, displayed in small caps. Supported values are "full", "publication", "tags", and "none" (default). |
-| orientation | No  | Optional placecement of the thumbnail, either "stacked" (default), "horizontal", or "none". |
-{.table}
-
-## Example
-
-As an example, the following shortcode displays a colored, borderless horizontal card that links to the [Rich Content]({{< ref "rich-content" >}} "Rich Content") page. It includes a custom header and footer.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* card path="rich-content" class="w-100 border-0" orientation="horizontal" color="info" header="publication" footer="tags" */>}}
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->

content/en/docs/0.8/components/carousel.md

@@ -1,48 +0,0 @@
----
-author: Mark Dumay
-title: Carousel
-date: 2023-01-29
-description: Use the carousel shortcode to display a carousel of several images.
-group: components
-layout: docs
----
-
-## Overview
-
-Use the `carousel` shortcode to display a carousel of several images, with similar behavior as the [image]({{< ref "image" >}} "image")
-
-## Arguments
-
-The shortcode supports the following arguments:
-
-| Argument  | Required | Description |
-|-----------|----------|-------------|
-| ratio     | No  | Aspect ratio of the image, either "1x1", "4x3", "16x9", or "21x9". If unspecified, the original aspect ratio is preserved. |
-| class     | No  | Optional class attribute of the `carousel` element, e.g. "w-75". |
-{.table}
-
-{{< alert >}}
-The carousel uses the original aspect ratio of the provided images when no aspect ratio is provided. Ensure the included images have a similar height and width to avoid inconsistent behavior.
-{{< /alert >}}
-
-Add an inner `img` element for each slide of the carousel. The `img` element supports the following arguments:
-
-| Argument  | Required | Description |
-|-----------|----------|-------------|
-| src       | Yes | Required url of the image, e.g. "img/boots.jpg". |
-| caption   | No  | Optional image caption. If set, the image is darkened to improve the contrast. The caption is hidden on smaller screens. |
-{.table}
-
-## Example
-
-As an example, the following shortcode displays a centered carousel with three slides, 16x9 aspect ratio, and a relative width of 67% on large screens.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* carousel ratio="16x9" class="col-sm-12 col-lg-8 mx-auto" */>}}
-  {{</* img src="img/coffee.jpg" caption="slide 1" */>}}
-  {{</* img src="img/phone.jpg" caption="slide 2" */>}}
-  {{</* img src="img/dunes.jpg" caption="slide 3" */>}}
-{{</* /carousel */>}}
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->

content/en/docs/0.8/components/collapse.md

@@ -1,39 +0,0 @@
----
-author: Mark Dumay
-title: Collapse
-date: 2023-01-28
-description: Use the collapse shortcode to reveil or hide a panel.
-group: components
-layout: docs
----
-
-## Overview
-
-Use the `collapse` shortcode to reveil or hide a panel. The panel can contain both HTML code and plain text. Link a button to the panel by assigning it's ID to the `collapse` attribute.
-
-## Arguments
-
-The shortcode supports the following arguments:
-
-| Argument    | Required | Description |
-|-------------|----------|-------------|
-| id          | Yes      | Required unique id of the collapse element, e.g. "collapse-1". |
-| class       | No       | Optional class attribute of the inner panel element, e.g. “p-3”. |
-{.table}
-
-## Example
-
-As an example, the following shortcode displays a button that, when clicked, triggers a panel to appear or disappear.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* button collapse="collapse-1" */>}}
-    Trigger panel
-{{</* /button */>}}
-
-{{</* collapse id="collapse-1" class="p-3 border rounded" */>}}
-    Some placeholder content for the collapse component. This panel is <i>hidden by default</i> but
-    revealed when the user activates the relevant trigger.
-{{</* /collapse */>}}
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->

content/en/docs/0.8/components/command-prompt.md

@@ -1,104 +0,0 @@
----
-author: Mark Dumay
-title: Command Prompt
-date: 2023-01-28
-description: The command shortcode generates terminal output for either Bash, PowerShell, or SQL shell languages.
-group: components
-layout: docs
----
-
-## Overview
-
-The `command` shortcode generates terminal output for either `bash`, `powershell`, or `sql` shell languages.
-
-## Arguments
-
-The shortcode supports the following arguments:
-
-| Argument  | Required | Description |
-|-----------|----------|-------------|
-| user      | No | Optional user to add to the prompt, e.g. "user". |
-| host      | No | Optional host to add to the prompt, e.g. "localhost". |
-| prompt    | No | Optional prompt override, e.g. "PS C:\Users\User>". |
-| shell     | No | Type of shell, either "bash" (default), "powershell", or "sql". |
-{.table}
-
-## Examples
-
-### Bash (default shell)
-
-Use the `command` shortcode to generate a block with a default bash command prompt.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* command */>}}
-export MY_VAR=123
-{{</* /command */>}}
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->
-
-Specify `user` and `host` to add the user context to the prompt. In addition, use `(out)` to specify an output line and use `\` to denote a line continuation.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* command user="user" host="localhost" */>}}
-export MY_VAR=123
-echo "hello"
-(out)hello
-echo one \
-two \
-three
-(out)one two three
-echo "goodbye"
-(out)goodbye
-{{</* /command */>}}
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->
-
-### PowerShell
-
-Set the `shell` argument to `powershell` to generate a PowerShell terminal. Override the `prompt` to add a directory if needed. Use the backtick `` ` `` symbol to denote a line continuation.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* command prompt="PS C:\Users\User>" shell="powershell" */>}}
-Write-Host `
-'Hello' `
-'from' `
-'PowerShell!'
-(out)Hello from PowerShell!
-Write-Host 'Goodbye from PowerShell!'
-(out)Goodbye from PowerShell!
-{{</* /command */>}}
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->
-
-### SQL
-
-Set the `shell` argument to `sql` to generate a SQL terminal. Use the `(con)` suffix to denote a line continuation.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* command prompt="mysql>" shell="sql" */>}}
-set @my_var = 'foo';
-set @my_other_var = 'bar';
-CREATE TABLE people ((con)
-first_name VARCHAR(30) NOT NULL,(con)
-last_name VARCHAR(30) NOT NULL(con)
-);
-(out)Query OK, 0 rows affected (0.09 sec)
-insert into people(con)
-values ('John', 'Doe');
-(out)Query OK, 1 row affected (0.02 sec)
-select *(con)
-from people(con)
-order by last_name;
-(out)+------------+-----------+
-(out)| first_name | last_name |
-(out)+------------+-----------+
-(out)| John       | Doe       |
-(out)+------------+-----------+
-(out)1 row in set (0.00 sec)
-{{</* /command */>}}
-{{< /example >}}
-<!-- markdownlint-ensable MD037 -->

content/en/docs/0.8/components/icon.md

@@ -1,28 +0,0 @@
----
-author: Mark Dumay
-title: Icon
-date: 2023-02-02
-description: Use the fa shortcode to add a Font Awesome icon with ease.
-group: components
-layout: docs
----
-
-## Overview
-
-Use the `fa` shortcode to quickly add a Font Awesome icon to your content. Use `fa` for regular icons, `fab` for brand icons, and `fas` for solid icons.
-
-## Arguments
-
-The shortcode supports unnamed arguments only and requires at least one argument. The first argument is used as the icon name without the `fa-` prefix. Additional (unnamed) arguments are passed as `class` attributes to the inner HTML element.
-
-## Example
-
-As an example, the following shortcodes show a square check, a brand logo, and a circle check.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* fa square-check */>}}
-{{</* fab linkedin */>}}
-{{</* fas circle-check */>}}
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->

content/en/docs/0.8/components/image.md

@@ -1,35 +0,0 @@
----
-author: Mark Dumay
-title: Image
-date: 2023-01-28
-description: Use the image shortcode to display a responsive image with a specific aspect ratio.
-group: components
-layout: docs
----
-
-## Overview
-
-Use the `image` shortcode to display a responsive image with a specific aspect ratio. The source link can refer to either an image available in the `/assets/img` folder of your site or a public web location. The shortcode renders the image as a so-called [image set]({{< param "links.mozilla_image" >}}) to optimize the image for different screen sizes and resolutions. Behind the scenes, Hugo renders the images in `WebP` format and stores them in a local folder (`resources` or `public`). The images are processed using the quality setting specified in the `[imaging]` section of the main [config file]({{< param "links.hugo_imaging" >}}) (defaults to 75). Supported image types are `.png`, `.jpeg`, `.gif`, `.tiff`, `.bmp`, and `.webp`. A fallback image of type `.jpeg` is provided for older browsers.
-
-## Arguments
-
-The shortcode supports the following arguments:
-
-| Argument  | Required | Description |
-|-----------|----------|-------------|
-| src       | Yes | Required url of the image, e.g. "img/boots.jpg". |
-| ratio     | No  | Optional aspect ratio of the image, either "1x1", "4x3", "16x9", or "21x9". If set, the image is resized and cropped to match the ratio. Else the original aspect ratio of the image is kept. |
-| class     | No  | Optional class attribute of the inner `img` element, e.g. "rounded". |
-| title     | No  | Optional alternate text of the image. |
-| caption   | No  | Optional figure caption. |
-{.table}
-
-## Example
-
-As an example, the following shortcode displays an image with rounded corners and a 21x9 aspect ratio.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* image src="img/flowers.jpg" ratio="21x9" caption="Figure caption" class="rounded" */>}}
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->

content/en/docs/0.8/components/navbar.md

@@ -1,40 +0,0 @@
----
-author: Mark Dumay
-title: Navbar
-date: 2023-01-28
-description: Use the navbar shortcode to display a navigation header with a toggler.
-group: components
-layout: docs
----
-
-## Overview
-
-Use the `navbar` shortcode to display a navigation header with a toggler. The menu items are derived from the site's configuration, which defaults to the menus defined under `main`. Nested items are supported at one-level depth. The navigation bar includes a search area and a language switcher if applicable. The items in the navigation header are accentuated if the current page or any of its descendants is active.
-
-<!-- TODO: add sidebar -->
-
-## Arguments
-
-The shortcode supports the following arguments:
-
-| Argument  | Required | Description |
-|-----------|----------|-------------|
-| path      | Yes | Required path of the active page. |
-| menus     | No  | Optional name of the menu configuration, defaults to "main". |
-| size      | No  | Optional breakpoint of the navbar toggler, either "xs", "sm", "md" (default), "lg", or "xl". |
-| style     | No  | Optional style of the navbar, either "light" (default) or "dark". |
-| color     | No  | Optional background color of the navbar, either "primary", "secondary", "success", "danger", "warning", "info", "light", "dark", "white" or "black". The default color is none. |
-| search    | No  | Optional flag to include a search input, defaults to the parameter "logo" set in the "navigation" section of the site's parameter configuration. |
-| logo      | No  | Optional address of the logo image, defaults to the parameter "logo" set in the "navigation" section of the site's parameter configuration. |
-| title     | No  | Optional brand title, displayed when the logo is not set. Defaults to the site's title. |
-{.table}
-
-## Example
-
-As an example, the following shortcode displays a light navigation header.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* navbar path="blog" color="light" size="sm" search="false" menus="sample" title="Brand" */>}}
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->

content/en/docs/0.8/components/overview.md

@@ -1,10 +0,0 @@
----
-author: Mark Dumay
-title: Overview
-date: 2023-01-14
-description: Use predefined shortcodes to embed Bootstrap components in your content.
-group: components
-layout: docs
----
-
-<!-- TODO: expand -->

content/en/docs/0.8/components/spinner.md

@@ -1,35 +0,0 @@
----
-author: Mark Dumay
-title: Spinner
-date: 2023-01-28
-description: Use the spinner shortcode to indicate the loading state of a component or page.
-group: components
-layout: docs
----
-
-## Overview
-
-Use the `spinner` shortcode to indicate the loading state of a component or page. The inner content is used as alternative description.
-
-## Arguments
-
-The shortcode supports the following arguments:
-
-| Argument    | Required | Description |
-|-------------|----------|-------------|
-| color       | No  | Optional theme color of the spinner, either "primary" (default), "secondary", "success", "danger",  "warning", "info", "light", "dark", "white" or "black". |
-| grow        | No  | Optional flag to indicate the spinner is growing instead of rotating, defaults to false. |
-| class       | No  | Optional class attribute of the spinner wrapping element, e.g. “text-center”. |
-{.table}
-
-## Example
-
-As an example, the following shortcode displays a centered spinner.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* spinner color="info" class="text-center" */>}}
-Loading...
-{{</* /spinner */>}}
-{{< /example>}}
-<!-- markdownlint-enable MD037 -->

content/en/docs/0.8/components/toast.md

@@ -1,37 +0,0 @@
----
-author: Mark Dumay
-title: Toast
-date: 2023-01-28
-description: Use the toast shortcode to display a dismissable message in the bottom-right corner of the screen.
-group: components
-layout: docs
----
-
-## Overview
-
-Use the `toast` shortcode to display a dismissable message in the bottom-right corner of the screen. Hinode defines a click event for a button with id `toastButton`. Modify the file `assets/js/toast.js` if needed.
-
-## Arguments
-
-The shortcode supports the following arguments:
-
-| Argument    | Required | Description |
-|-------------|----------|-------------|
-| header      | No  | Optional header of the toast message. Uses the site title by default. |
-{.table}
-
-## Example
-
-As an example, the following shortcode displays a button that, when clicked, triggers the toast message.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* button id="toastButton" */>}}
-    Show toast
-{{</* /button */>}}
-
-{{</* toast header="Custom title" */>}}
-    This is a toast message.
-{{</* /toast */>}}
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->

content/en/docs/0.8/components/tooltip.md

@@ -1,36 +0,0 @@
----
-author: Mark Dumay
-title: Tooltip
-date: 2023-01-28
-description: Use the toast shortcode to display a dismissable message in the bottom-right corner of the screen.
-group: components
-layout: docs
----
-
-## Overview
-
-Use the `tooltip` shortcode to display a tooltip for a hyperlink. Refer to the [button]({{< ref "#button" >}} "button") on how to display a tooltip for a button instead. The inner content is used as hyperlink text.
-
-## Arguments
-
-The shortcode supports the following arguments:
-
-| Argument    | Required | Description |
-|-------------|----------|-------------|
-| color       | No   | Optional theme color of the element, either "primary" (default), "secondary", "success", "danger",  "warning", "info", "light", "dark", "white" or "black". |
-| title       | Yes  | Title to display in the tooltip. |
-| href        | Yes  | Address for the button or hyperlink. |
-| placement   | No   | How to position the tooltip: "top" (default), "bottom", "left", or "right". |
-{.table}
-
-## Example
-
-As an example, the following shortcode displays a tooltip for a colored hyperlink.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* tooltip color="warning" title="Tooltip" href="#" */>}}
-    Tooltip demonstration
-{{</* /tooltip */>}}
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->

content/en/docs/0.8/configuration/colors.md

@@ -1,93 +0,0 @@
----
-title: Colors
-description: Use Bootstrap's color system to easily adjust your website's colors.
-date: 2023-01-14
-group: configuration
-layout: docs
----
-
-## Theme colors
-
-Hinode uses Bootstrap's color system. You can adjust them in the `/config/_default/params.toml` file in the `style` section.
-
-{{< docs name="theme-colors" file="config/_default/params.toml" >}}
-
-In addition, the background colors `black` and `white` are available too. Below is an overview of the rendered colors.
-
-<div class="row">
-    <div class="col-md-4">
-        <div class="p-3 mb-3 text-bg-primary rounded-3">Primary</div>
-    </div>
-    <div class="col-md-4">
-        <div class="p-3 mb-3 text-bg-secondary rounded-3">Secondary</div>
-    </div>
-    <div class="col-md-4">
-        <div class="p-3 mb-3 text-bg-success rounded-3">Success</div>
-    </div>
-    <div class="col-md-4">
-        <div class="p-3 mb-3 text-bg-danger rounded-3">Danger</div>
-    </div>
-    <div class="col-md-4">
-        <div class="p-3 mb-3 text-bg-warning rounded-3">Warning</div>
-    </div>
-    <div class="col-md-4">
-        <div class="p-3 mb-3 text-bg-info rounded-3">Info</div>
-    </div>
-    <div class="col-md-4">
-        <div class="p-3 mb-3 text-bg-light rounded-3">Light</div>
-    </div>
-    <div class="col-md-4">
-        <div class="p-3 mb-3 text-bg-dark rounded-3">Dark</div>
-    </div>
-    <div class="col-md-4">
-        <div class="p-3 mb-3 text-bg-white rounded-3">White</div>
-    </div>
-    <div class="col-md-4">
-        <div class="p-3 mb-3 bg-black text-white rounded-3">Black</div>
-    </div>
-</div>
-
-## Colored contrasting links
-
-Hinode defines additional classes to render links that contrast with their background. Simply add `link-bg-<color>` to the class of an `<a>` anchor element. The next example adds a link constrasting with the background color `bg-success`.
-
-{{< example >}}
-<div class="col-md-2">
-    <div class="p-3 mb-3 bg-success rounded-3 text-center"><a class="link-bg-success" href="#">Success</a></div>
-</div>
-{{< /example>}}
-
-Below grid illustrates the contrasting colors for each background.
-
-<div class="row">
-    <div class="col-md-4">
-        <div class="p-3 mb-3 bg-primary rounded-3"><a class="link-bg-primary" href="#">Primary</a></div>
-    </div>
-    <div class="col-md-4">
-        <div class="p-3 mb-3 bg-secondary rounded-3"><a class="link-bg-secondary" href="#">Secondary</a></div>
-    </div>
-    <div class="col-md-4">
-        <div class="p-3 mb-3 bg-success rounded-3"><a class="link-bg-success" href="#">Success</a></div>
-    </div>
-    <div class="col-md-4">
-        <div class="p-3 mb-3 bg-danger rounded-3"><a class="link-bg-danger" href="#">Danger</a></div>
-    </div>
-    <div class="col-md-4">
-        <div class="p-3 mb-3 bg-warning rounded-3"><a class="link-bg-warning" href="#">Warning</a></div>
-    </div>
-    <div class="col-md-4">
-        <div class="p-3 mb-3 bg-info rounded-3"><a class="link-bg-info" href="#">Info</a></div>
-    </div>
-    <div class="col-md-4">
-        <div class="p-3 mb-3 bg-light rounded-3"><a class="link-bg-light" href="#">Light</a></div>
-    </div>
-    <div class="col-md-4">
-        <div class="p-3 mb-3 bg-dark rounded-3"><a class="link-bg-dark" href="#">Dark</a></div>
-    </div>
-</div>
-
-## Generating helper
-
-The SCSS generator for the colored links is defined in `assets/scss/helpers/_colored-links.scss`.
-
-{{< docs name="colored-links" file="assets/scss/helpers/_colored-links.scss" >}}

content/en/docs/0.8/configuration/comments.md

@@ -1,9 +0,0 @@
----
-title: Comments
-description: 
-date: 2023-01-14
-group: configuration
-layout: docs
----
-
-<!-- TODO: expand -->

content/en/docs/0.8/configuration/fonts.md

@@ -1,23 +0,0 @@
----
-title: Fonts
-description: Configure a specific font to style your website.
-date: 2023-01-28
-group: configuration
-layout: docs
----
-
-Hinode uses a configurable font stack that includes support for Emoji across browsers and devices. Review the configuration settings below on how to update the font.
-
-## Font configuration
-
-Hinode uses Bootstrap's font configuration. The font stack includes support for Emoji across browsers and devices. You can adjust the main font in the `/config/_default/params.toml` file in the `style` section.
-
-{{< docs name="font" file="config/_default/params.toml" >}}
-
- By default, Hinode configures the `Inter` font provided by [Google Fonts]({{< param "links.google_fonts" >}}) with the weights 200, 300, and 600. If you use a different font provider, be sure to adjust the Content Security Policy in the [server configuration]({{< ref "server" >}}).
-
-## Customization
-
-The font stack is defined in the `assets/scss/common/_variables.scss` file. The variable `$themeFont` is initialized to the value in the [font configuration](#font-configuration).
-
-{{< docs name="font" file="assets/scss/common/_variables.scss" >}}

content/en/docs/0.8/configuration/languages.md

@@ -1,43 +0,0 @@
----
-title: Languages
-description: Configure multiple languages to enable multilingual sites.
-date: 2023-01-21
-group: configuration
-layout: docs
----
-
-Hinode supports Hugo's [multilingual mode]({{< param "links.hugo_lang" >}}) to create websites with multiple languages side by side. The next paragraphs explain how to configure multiple languages, how to provide content translations, and how to define multilingual messages and keywords.
-
-## Language configuration
-
-Define the languages available to your site in the main site configuration. The below configuration shows the default configuration set in `config/_default/languages.toml` for the English language.
-
-{{< docs name="lang-main" file="config/_default/languages.toml" >}}
-
-The default behavior is set in `config/_default/config.toml`. For example, you can set the `defaultContentLanguageInSubdir` to `false` to remove the language slug `/en` from your site entirely.
-
-{{< docs name="language" file="config/_default/config.toml" >}}
-
-## Content translation
-
-Hugo supports multiple ways to define translated content. Hinode uses an approach to define translations in separate directories for each language. In the default settings, content for the English language is defined in the folder `content/en`. It is recommended to use the same filename for each page translation. This enables Hugo to recognize if a page translation is available. Hinode links to this translation in the main navigation bar.
-
-For example, consider the `About` page. It is available in both English and Dutch. The content files are defined in `content/en/about.md` and `content/nl/about.md`. Hugo now recognizes the page is available in two languages. To translate the URL for the Dutch page, a `slug` is defined the page's frontmatter:
-
-```yml
----
-slug: "over-mij"
----
-```
-
-The English page is available by navigating to `/en/about` and the Dutch translation is available on `/nl/over-mij`. The [main navigation]({{< ref "navigation#main-navigation" >}}) item shows a language switcher for both translations.
-
-## Internationalization
-
-Hinode uses Hugo's [internationalization function]({{< param "links.hugo_i18n" >}}) to translate keywords and messages. Translations are available in English, Dutch, and German. For example, the translation for the word `about` in the Dutch language is defined in `i18n/nl.yaml` (strictly speaking, it translates to `about me`).
-
-```yml
-# Content
-- id: about
-  translation: "Over mij"
-```

content/en/docs/0.8/configuration/layout.md

@@ -1,321 +0,0 @@
----
-title: Layout
-description: Hinode uses a grid-based, responsive design for the home page, single pages and list pages.
-date: 2023-01-21
-group: configuration
-layout: docs
----
-
-Hinode uses Bootstrap's [grid system]({{< param "links.bs_grid" >}}) and [breakpoints]({{< param "links.bs_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]({{< ref "navigation#main-navigation" >}}) and can be optionally fixed to the top. By default, the base layout is expanded to fill the entire available viewport. This means that all elements stretch horizontally across the entire viewport. The body also expands vertically, where the footers align to the bottom of the viewport.
-
-### Example
-
-The following diagram illustrates the conceptual base design:
-
-<div class="container-fluid text-center bg-light border rounded-3 bg-opacity-10 p-3">
-    <div class="row g-3">
-        <div class="col-12">
-            <div class="p-3 bg-primary bg-opacity-10 rounded-3">Header .col-12 <i>(optionally fixed)</i></div>
-        </div>
-        <div class="col-12">
-            <div class="p-3 bg-primary bg-opacity-10 rounded-3">
-                <p class="mb-5">Body .col-12 .flex-fill</p>
-                <i>expands to fill viewport</i>
-            </div>
-        </div>
-        <div class="col-12">
-            <div class="p-3 bg-primary bg-opacity-10 rounded-3">Social .col-12</div>
-        </div>
-        <div class="col-12">
-            <div class="p-3 bg-primary bg-opacity-10 rounded-3">Footer .col-12</div>
-        </div>
-    </div>
-</div>
-
-### Configuration
-
-Hinode uses several settings from Hugo's [main configuration]({{< param "links.hugo_config" >}}). Several extensions are defined in the [custom site parameters]({{< param "links.hugo_config_dir" >}}) and [language-specific configuration]({{< param "links.hugo_lang_config" >}}).
-
-#### Main configuration
-
-The base layout uses the [main configuration]({{< param "links.hugo_config" >}}) 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. |
-| paginate      | 9       | Maximum number of elements to display on a [list page](#list-pages) before pagination. |
-| enableGitInfo | -       | Enables git information, which is used by [documentation pages](#documentation-layout). |
-{.table}
-
-The below configuration shows the default configuration set in `config/_default/config.toml`.
-
-{{< docs name="main" file="config/_default/config.toml" >}}
-
-#### Extended configuration
-
-Hinode uses the following extended settings in the `main` section of the `site parameters`:
-
-| Setting      | Default | Description |
-|--------------|---------|-------------|
-| separator    | "-"     | Seperator to join the website title and page title. |
-| description  | -       | Short description of the website that is added to the page metadata. |
-{.table}
-
-The below configuration shows the default configuration set in `config/_default/params.toml`.
-
-{{< docs name="main" file="config/_default/params.toml" >}}
-
-#### Language-specific configuration
-
-Hinode supports [multilingual content]({{< param "links.hugo_lang_config" >}}). The following parameters are used in the site's footer, header, and meta data. Refer to the [languages]({{< ref "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 | message       | -       | Welcome message used in the featured section on the home page. |
-| feature | tagline       | -       | Tagline used below the welcome message in the featured section on the home page. |
-| feature | link          | -       | Call to action link in the featured section on the home page. |
-| feature | caption       | "About" | Call to action title in the featured section on the home page. |
-| footer  | license       | -       | License displayed on the site's footer. |
-| footer  | socialTitle   | -       | Title displayed in the site's social footer. |
-| footer  | socialCaption | -       | Caption displayed in the site's social footer. |
-{.table}
-
-The below configuration shows the default configuration set in `config/_default/languages.toml` for the English language.
-
-{{< docs name="lang-param" file="config/_default/languages.toml" >}}
-
-## Home page
-
-The home page introduces a feature element and provides a selection of the three most recent items in a section, such as blog posts and project descriptions. The items are displayed as card groups and alternate between a vertical grid and a horizontal grid. A button that links to the related section is added below each group. The feature element can optionally cover the entire viewscreen.
-
-### Example
-
-The following diagram illustrates the conceptual layout of the home page:
-
-<div class="container-fluid text-center bg-light border rounded-3 bg-opacity-10 p-3">
-    <div class="row g-3">
-        <div class="col-12">
-            <div class="p-3 bg-secondary bg-opacity-10 rounded-3">Header .col-12</div>
-        </div>
-        <div class="col-12">
-            <div class="p-3 bg-primary bg-opacity-10 rounded-3">
-                <p>Feature .col-12</p>
-                <i>optionally spans viewport</i>
-            </div>
-        </div>
-        <div class="col-4">
-            <div class="p-3 bg-primary bg-opacity-10 rounded-3">Card .col-4</div>
-        </div>
-        <div class="col-4">
-            <div class="p-3 bg-primary bg-opacity-10 rounded-3">Card .col-4</div>
-        </div>
-        <div class="col-4">
-            <div class="p-3 bg-primary bg-opacity-10 rounded-3">Card .col-4</div>
-        </div>
-        <div class="col-12">
-            <div class="p-3 bg-primary bg-opacity-10 rounded-3">Card .col-12</div>
-        </div>
-        <div class="col-12">
-            <div class="p-3 bg-primary bg-opacity-10 rounded-3">Card .col-12</div>
-        </div>
-        <div class="col-12">
-            <div class="p-3 bg-primary bg-opacity-10 rounded-3">Card .col-12</div>
-        </div>
-        <div class="col-12">
-            <div class="p-3 bg-secondary bg-opacity-10 rounded-3">Social .col-12</div>
-        </div>
-        <div class="col-12">
-            <div class="p-3 bg-secondary bg-opacity-10 rounded-3">Footer .col-12</div>
-        </div>
-    </div>
-</div>
-
-### Configuration
-
-The configuration of the home page is set in the `home` section of the `site parameters`. The folllowing settings are supported:
-
-| Setting      | Default | Description |
-|--------------|---------|-------------|
-| sections     | -       | Sections to include on the home page, e.g. ["blog", "projects"]. |
-| featurePhoto | -       | Url of the photo to include in the feature element. |
-| fullCover    | false   | Flag to indicate if the feature element should cover the entire front page. |
-{.table}
-
-The below configuration shows the default configuration set in `config/_default/params.toml`.
-
-{{< docs name="home" file="config/_default/params.toml" >}}
-
-## List pages
-
-List pages provide an overview of available content within a section as a card group. By default, the most recent nine items are displayed. Adjust the setting `paginate` in the [main configuration](#configuration) as needed. If the section contains more items, a paginator is added below the card group.
-
-### Example
-
-The following diagram illustrates the conceptual layout of a list page:
-
-<div class="container-fluid text-center bg-light border rounded-3 bg-opacity-10 p-3">
-    <div class="row g-3">
-        <div class="col-12">
-            <div class="p-3 bg-secondary bg-opacity-10 rounded-3">Header .col-12</div>
-        </div>
-        <div class="col-4">
-            <div class="p-3 bg-primary bg-opacity-10 rounded-3">Card</div>
-        </div>
-        <div class="col-4">
-            <div class="p-3 bg-primary bg-opacity-10 rounded-3">Card</div>
-        </div>
-        <div class="col-4">
-            <div class="p-3 bg-primary bg-opacity-10 rounded-3">Card</div>
-        </div>
-        <div class="col-4">
-            <div class="p-3 bg-primary bg-opacity-10 rounded-3">Card</div>
-        </div>
-        <div class="col-4">
-            <div class="p-3 bg-primary bg-opacity-10 rounded-3">Card</div>
-        </div>
-        <div class="col-4">
-            <div class="p-3 bg-primary bg-opacity-10 rounded-3">Card</div>
-        </div>
-        <div class="col-4">
-            <div class="p-3 bg-primary bg-opacity-10 rounded-3">Card</div>
-        </div>
-        <div class="col-4">
-            <div class="p-3 bg-primary bg-opacity-10 rounded-3">Card</div>
-        </div>
-        <div class="col-4">
-            <div class="p-3 bg-primary bg-opacity-10 rounded-3">Card</div>
-        </div>
-        <div class="col-12">
-            <div class="p-3 bg-secondary bg-opacity-10 rounded-3">Social .col-12</div>
-        </div>
-        <div class="col-12">
-            <div class="p-3 bg-secondary bg-opacity-10 rounded-3">Footer .col-12</div>
-        </div>
-    </div>
-</div>
-
-### Configuration
-
-The configuration of the list pages is set in the `list` section of the `site parameters`. You can specify the settings for each section of your content. The entire configuration is fully optional and uses default settings if omitted. The folllowing settings are supported per section:
-
-| Setting      | Default      | Description |
-|--------------|--------------|-------------|
-| title        | Section name | Title of the list page, displayed above the card group. By default, the title defined in the page's frontmatter is used. |
-| sort         | "date"       | Type of sorting to be used, either "date" (default), "weight", "publication", "expiration", "lastmod", "length", "title", "linktitle", or "&lt;param&gt;". See Hugo's [content ordering]({{< param "links.hugo_ordering" >}}) for more details. |
-| reverse      | true         | Flag to indicate the sorting of the section content should be reversed, defaults to true. |
-| cols         | 3            | Number of columns to display in the card group, defaults to 3. |
-| color        | -            | Theme color of the card, either "primary", "secondary", "success", "danger", "warning", "info", "light", "dark", "white" or "black". By default, no color is specified. |
-| 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"    | Placecement of the thumbnail, either "stacked" (default), "horizontal", or "none". |
-| style        | -            | Optional styling attributes added to card class, e.g. "border-0" to remove the borders. |
-| homepage     | 3            | Number of items to display on the home page (if defined in the [configuration](#configuration-1)), defaults to 3. |
-{.table}
-
-The below configuration shows the default configuration set in `config/_default/params.toml`.
-
-{{< docs name="list" file="config/_default/params.toml" >}}
-
-## Single pages
-
-Single pages follow the base layout but introduce two columns next to the body content. The left column shows a [sidebar navigation]({{< ref "navigation#sidebar-navigation" >}}) if applicable and is left empty otherwise. The right column shows a [table of contents]({{< ref "navigation#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.
-
-### Default layout
-
-By default, single pages, such as a blog page, include the following elements in the body:
-
-- **Title** - the title of the page as set in the page's frontmatter.
-- **Metadata** - the date of the page, the modification date (if applicable), the read time, and the amount of words on the page.
-- **Tags** - links to any tags defined in the page's frontmatter.
-- **Description** - the description as defined in the page's frontmatter, or as summarized by Hugo if omitted in the frontmatter.
-- **Thumbnail** - a thumbnail image with figure caption that links to the photo credits (if defined in the frontmatter).
-- **Navigation links** - links on the bottom of the page that link to the previoud and next page within the current section.
-
-The below example illustrates the parameters used in the page's frontmatter:
-
-```yaml
----
-author: Mark Dumay
-title: Another project
-date: 2021-07-15
-description: Another project.
-tags: ["javascript", "golang"]
-thumbnail: img/coffee.jpg
-photoCredits: <a href="https://unsplash.com/@kfred">Karl Fredrickson</a>
-photoSource: <a href="https://unsplash.com/photos/TYIzeCiZ_60">Unsplash</a>
----
-```
-
-### Documentation layout
-
-Documentation pages use a more straightforward, simplified layout compared to the default layout. They include the following elements in their body:
-
-- **Title** - the title of the page as set in the page's frontmatter.
-- **Description** - the description as defined in the page's frontmatter, or as summarized by Hugo if omitted in the frontmatter.
-- **Metadata** - a revision date and link to the latest git commit on the bottom of the page. Enable `enableGitInfo` in the [main configuration](#main-configuration) for the git commit message to work.
-
-Be sure to select the `docs` layout in the page's frontmatter to enable the documentation layout:
-
-```yml
----
-layout: docs
----
-```
-
-### Example
-
-<div class="container-fluid text-center bg-light border rounded-3 bg-opacity-10 p-3">
-    <div class="row g-3">
-        <div class="col-12">
-            <div class="p-3 bg-secondary bg-opacity-10 rounded-3">Header .col-12</div>
-        </div>
-        <div class="col-12">
-            <div class="row">
-                <div class="col-3">
-                    <div class="bg-primary bg-opacity-10 rounded-3">
-                        <p>Sidebar</p>
-                        <i>sticky</i>
-                    </div>
-                </div>
-                <div class="col-6">
-                    <div class="bg-primary bg-opacity-10 rounded-3">
-                        <p>Body .col-8 .flex-fill</p>
-                        <i>expands to fill viewport</i>
-                    </div>
-                </div>
-                <div class="col-3">
-                    <div class="bg-primary bg-opacity-10 rounded-3">
-                        <p>TOC</p>
-                        <i>sticky</i>
-                    </div>
-                </div>
-            </div>
-        </div>
-        <div class="col-12">
-            <div class="p-3 bg-secondary bg-opacity-10 rounded-3">Social .col-12</div>
-        </div>
-        <div class="col-12">
-            <div class="p-3 bg-secondary bg-opacity-10 rounded-3">Footer .col-12</div>
-        </div>
-    </div>
-</div>
-
-### Configuration
-
-The configuration of the documentation pages is set in the `docs` section of the site parameters. The folllowing settings are supported:
-
-| Setting      | Default | Description |
-|--------------|---------|-------------|
-| docs_version | -       | Default version to use in documentation links. |
-{.table}
-
-The below configuration shows the default configuration set in `config/_default/params.toml`.
-
-{{< docs name="docs" file="config/_default/params.toml" >}}

content/en/docs/0.8/configuration/metadata.md

@@ -1,9 +0,0 @@
----
-title: Metadata
-description: 
-date: 2023-01-18
-group: configuration
-layout: docs
----
-
-<!-- TODO: expand -->

content/en/docs/0.8/configuration/navigation.md

@@ -1,106 +0,0 @@
----
-title: Navigation
-description: Help the user navigate your website using configurable navigation elements.
-date: 2023-01-15
-group: configuration
-layout: docs
----
-
-Hinode supports several types of navigation that utilize Bootstrap elements. The main navigation is positioned on the top of the screen and includes a search input element. An optional secondary navigation is available as sidebar. Next to these navigation items, pages may optionally include a breadcrumb to indicate the current page's location within the site's navigational hierarchy. Finally, pages may also include a table of contents element that is linked to the scroll position of the current page.
-
-## Basic configuration
-
-The basic configuration of the navigation elements is set in the `navigation` section of the site parameters. The folllowing settings are supported:
-
-| Setting    | Default | Description |
-|------------|---------|-------------|
-| logo       | -       | Address of the brand logo image, e.g. "/img/logo_embedded.svg". |
-| color      | "white" | [Theme color]({{< ref "colors" >}}) of the navigation bar. Set the style to set the correct contrast of the menu items. |
-| style      | "light" | Style of the navigation bar, either "light" or "dark". It changes the colors of the menu items accordingly. |
-| fixed      | false   | Flag indicating to keep the navigation bar fixed at the top of the screen. |
-| offset     | "3em"   | Applies an [offset to main elements]({{< param "links.bs_navbar_placement" >}}) when `fixed` is set to true. |
-| search     | true    | Flag indicating to include a search input. |
-| breadcrumb | false   | Flag indicating to add breadcrumb navigation to the top of any single page. List pages are excluded. |
-| toc        | true    | Flag indicating to enable table of contents globally. Individual pages can override this setting in the frontmatter using the value `includeToc`. |
-| sidebar    | true    | Flag indicating to enable sidebar navigation globally. If set, a sidebar is displayed when applicable. |
-{.table}
-
-The below configuration shows the default configuration set in `config/_default/params.toml`.
-
-{{< docs name="navigation" file="config/_default/params.toml" >}}
-
-## Main navigation
-
-The main navigation uses [Hugo's menu system]({{< param "links.hugo_menus" >}}) to generate a responsive navigation bar at the top of the page. The navigation bar uses a breakpoint to add a toggler for smaller screens. A language switcher is added automatically if your site supports multiple languages. The language switcher links to the currently translated page if available.
-
-### Menus
-
-The navigation bar uses [Hugo's menu system]({{< param "links.hugo_menus" >}}) to generate the menu items. The navigation supports nesting at one level depth. The following example defines an example menu configuration called `sample` (the main configuration is called `main`).
-
-{{< docs name="sample-navigation" file="config/_default/menus/menus.en.toml" >}}
-
-### Example
-
-Using the sample configuration defined in the previous paragraph, the navigation bar looks like this:
-
-{{< navbar color="light" size="sm" search="false" menus="sample" title="Sample" >}}
-
-### Customization
-
-Hinode includes a navigation bar at the top of the screen by default. You can modify the configuration in the `layouts/_default/baseof.html` file. The navigation bar is also available as [shortcode]({{< ref "navbar" >}}).
-
-## Sidebar navigation
-
-Hinode supports optional sidebar navigation. It is intended to be used as companion to the main navigation and is typically used in content-heavy sections, such as documentation pages. On smaller screens, the sidebar is replaced with an [offcanvas element]({{< param "links.bs_offcanvas" >}}). In this case, the main navigation receives an additional toggler on the left of the screen.
-
-### Menus
-
-Inspired by Bootstrap's documentation site, Hinode uses a separate configuration file for the sidebar menus. A sidebar can be configured for each main section of the site. For example, the sidebar menus of the `Docs` section are defined in `data/docs.yml`. The menus support group items and single page items. Below example defines a group section called `Getting started` with three siblings. A single page `About` is added next.
-
-```yml
-- title: Getting started
-  pages:
-    - title: Introduction
-    - title: Commands
-    - title: Contribute
-- title: About
-```
-
-An entry in the page's [frontmatter]({{< param "links.hugo_frontmatter" >}}) is needed to link the page to the correct entry in the sidebar. Below example highlights the relevant frontmatter elements from the `Introduction` page, which is part of the `Getting started` group. Please notice the group name needs to be defined in kebab-case, e.g. `getting-started`. You can omit the group name for single page entries, such as the `About` page in the example configuration above.
-
-```yml
----
-title: Introduction
-group: getting-started
----
-```
-
-### Customization
-
-The file `assets/scss/components/_sidebar.scss` contains the styling of the sidebar. It refers to a button `$btn-toggle` that is defined in `assets/scss/common/_icons.scss`. It also defines the spacing to be added to the page's main content section when using a fixed navigation bar:
-
-{{< docs name="sidebar" file="assets/scss/components/_sidebar.scss" >}}
-
-## Breadcrumb
-
-Hinode supports optional breadcrumb navigation. The breadcrumb indicates the current page's location within the site's navigational hierarchy. It is automatically populated by Hugo. Enable the breadcrumb in the [basic navigation configuration](#basic-configuration). If enabled, all single pages will add breadcrumb navigation to the top of the page.
-
-### Example
-
-When enabled, the breadcrumb looks like this:
-
-{{< breadcrumb >}}
-
-### Customization
-
-The breadcrumb is also available as [shortcode]({{< ref "breadcrumb" >}}).
-
-## Table of contents
-
-Single pages can optionally show an [table of contents]({{< param "links.hugo_toc" >}}) on the right of the screen. The table of contents is automatically popuplated based on the headings within the page content (two levels deep). The table of contents is hidden on smaller screens or if it has less than two items. Enable the table of contents in the [basic navigation configuration](#basic-configuration). If enabled, all single pages will show the element, unless disabled in the page's frontmatter.
-
-### Customization
-
-The file `assets/scss/components/_toc.scss` defines the styling of the table of contents element. It adds spacing to align the element to the sidebar, amongst other styling:
-
-{{< docs name="toc" file="assets/scss/components/_toc.scss" >}}

content/en/docs/0.8/content/icons.md

@@ -1,259 +0,0 @@
----
-title: Icons
-description: Use out-of-the-box Font Awesome icons to style your website.
-date: 2023-02-02
-group: content
-layout: docs
----
-
-Hinode provides out-of-the box access to the free icons of [Font Awesome]({{< param "links.fontawesome" >}}). The [shortcodes]({{< relref "icon" >}}) `fa`, `fab`, and `fas` are available to add these icons with as limited code as possible. The Font Awesome icon library provides various [styling options]({{< param "links.fa_styling" >}}). The below paragraphs illustrate how to apply the styling options compatible with Markdown, Bootstrap, and the [content security policy]({{< ref "server" >}}).
-
-## Styling basics
-
-The [Font Awesome icon library]({{< param "links.fa_icons" >}}) provides access to more than 2.000 free and open-source icons. Simply search for a keyword and review the presented options. For example, searching for the keyword `music` and filtering for `free` returns a list of nearly 30 icons. Use one of the following three [shortcodes]({{< relref "icon" >}}) to add an icon to your Markdown content:
-
-- `fa` - regular Font Awesome icon library
-- `fab` - brands Font Awesome icon library
-- `fas` - solid Font Awesome icon library
-
-Specify the correct icon library and omit the `fa-` prefix from the icon name to insert an icon.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* fas music */>}}
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->
-
-The icons inherit the current styling options and as such blend in with text inline. For example, appply the [theme color]({{< ref "colors" >}}) `text-primary` of the outer HTML element `span` to change the color of the icon. You can also pass the class attribute directly to the shortcode, such as `text-info`.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-<span class="text-primary">
-    {{</* fas music */>}}
-</span>
-{{</* fas music text-info */>}}
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->
-
-## Sizing icons
-
-Font Awesome supports both relative and absolute sizing. The following two section explain how to apply the sizing to an icon.
-
-### Relative sizing
-
-Font Awesome includes a range of t-shirt based sizes that are relative to the browser's default font size of 16px. The icons align to the inline text. The following example illustrative the available relative sizes.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-<p>{{</* fas coffee fa-2xs */>}} When my six o’clock alarm buzzes, I require a pot of good java.</p>
-<p>{{</* fas coffee fa-xs */>}} When my six o’clock alarm buzzes, I require a pot of good java.</p>
-<p>{{</* fas coffee fa-sm */>}} When my six o’clock alarm buzzes, I require a pot of good java.</p>
-<p>{{</* fas coffee fa */>}} When my six o’clock alarm buzzes, I require a pot of good java.</p>
-<p>{{</* fas coffee fa-lg */>}} When my six o’clock alarm buzzes, I require a pot of good java.</p>
-<p>{{</* fas coffee fa-xl */>}} When my six o’clock alarm buzzes, I require a pot of good java.</p>
-<p>{{</* fas coffee fa-2xl */>}} When my six o’clock alarm buzzes, I require a pot of good java.</p>
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->
-
-The table below illustrates the relative sizing classes and their equivalent relative and absolute font size.
-
-{{< table "table-striped w-auto" >}}
-| Relative Sizing Class | Font Size | Equivalent in Pixels |
-|----------|--------:|-----:|
-| `fa-2x`  | 0.625em | 10px |
-| `fa-xs`  | 0.75em  | 12px |
-| `fa-sm`  | 0.875em | 14px |
-| `fa`     | 1em     | 16px |
-| `fa-lg`  | 1.25em  | 20px |
-| `fa-xl`  | 1.5em   | 24px |
-| `fa-2xl` | 2em     | 32px |
-{{< /table >}}
-
-### Absolute sizing
-
-Font Awesome also supports absolute sizing on a scale of 1x to 10x. The icons do not necessarily align to their surrounding text. The following example illustrative the various absolute sizes.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* fas camera fa-1x */>}}
-{{</* fas camera fa-2x */>}}
-{{</* fas camera fa-3x */>}}
-{{</* fas camera fa-4x */>}}
-{{</* fas camera fa-5x */>}}
-{{</* fas camera fa-6x */>}}
-{{</* fas camera fa-7x */>}}
-{{</* fas camera fa-8x */>}}
-{{</* fas camera fa-9x */>}}
-{{</* fas camera fa-10x */>}}
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->
-
-The table below illustrates the absolute sizing classes and their equivalent font size.
-
-{{< table "table-striped w-auto" >}}
-| Absolute Sizing Class | Font Size |
-|---------|--------:|
-| `fa-1x` | 1em |
-| `fa-2x` | 2em |
-| `fa-3x` | 3em |
-| `fa-4x` | 4em |
-| `fa-5x` | 5em |
-| `fa-6x` | 6em |
-| `fa-7x` | 7em |
-| `fa-8x` | 8em |
-| `fa-9x` | 9em |
-| `fa-10x` | 10em |
-{{< /table >}}
-
-## Fixed width
-
-Add `fa-fw` to the class of the HTML element referencing your icon to apply a fixed width. This ensures icons of varying icon width are properly aligned to each other. The following example illustrates how this works.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-<div class="fa-3x">
-    <div>{{</* fas skating fa-fw bg-info */>}} Skating</div>
-    <div>{{</* fas skiing fa-fw bg-info */>}} Skiing</div>
-    <div>{{</* fas skiing-nordic fa-fw bg-info */>}} Nordic Skiing</div>
-    <div>{{</* fas snowboarding fa-fw bg-info */>}} Snowboarding</div>
-    <div>{{</* fas snowplow fa-fw bg-info */>}} Snowplow</div>
-</div>
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->
-
-## Lists
-
-Use the classes `fa-ul` and `fa-li` to replace default bullets in unordered lists. The following example illustrates how this works.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-<ul class="fa-ul">
-    <li><span class="fa-li">{{</* fas circle-check */>}}</span>List icons can</li>
-    <li><span class="fa-li">{{</* fas check-square */>}}</span>be used to</li>
-    <li><span class="fa-li">{{</* fas spinner fa-pulse */>}}</span>replace bullets</li>
-    <li><span class="fa-li">{{</* fa square */>}}</span>in lists</li>
-</ul>
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->
-
-## Rotating icons
-
-Use specific classes to rotate the icon with a specific degree. The following example illustrates how this works.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-<div class="fa-3x">
-    {{</* fas snowboarding */>}}
-    {{</* fas snowboarding fa-rotate-90 */>}}
-    {{</* fas snowboarding fa-rotate-180 */>}}
-    {{</* fas snowboarding fa-rotate-270 */>}}
-    {{</* fas snowboarding fa-flip-horizontal */>}}
-    {{</* fas snowboarding fa-flip-vertical */>}}
-    {{</* fas snowboarding fa-flip-both */>}}
-</div>
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->
-
-The following classes are available:
-
-{{< table "table-striped w-auto" >}}
-| Class | Details |
-|---------|--------|
-| `fa-rotate-90` | Rotates an icon 90° |
-| `fa-rotate-180` | Rotates an icon 180° |
-| `fa-rotate-270` | Rotates an icon 270° |
-| `fa-flip-horizontal` | Mirrors an icon horizontally |
-| `fa-flip-vertical` | Mirrors an icon vertically |
-| `fa-flip-both` | Mirrors an icon both vertically and horizontally |
-{{< /table >}}
-
-## Animating icons
-
-Font Awesome supports various animations by simply adding a animation class to the HTML element. The following example illustrates the available basic animations. Add custom styles to your [Sass files]({{< ref "styles" >}}) to apply additional [animation utilities]({{< param "links.fa_animation" >}}).
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-<div class="fa-3x">
-    {{</* fas heart fa-beat */>}}
-    {{</* fas triangle-exclamation fa-fade */>}}
-    {{</* fas circle-info fa-beat-fade */>}}
-    {{</* fas basketball fa-bounce */>}}
-    {{</* fas camera-rotate fa-flip */>}}
-    {{</* fas bell fa-shake */>}}
-    {{</* fas sync fa-spin */>}}
-</div>
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->
-
-The following table describes the available basic animation classes.
-
-{{< table "table-striped w-auto" >}}
-| Class | Details |
-|---------|--------|
-| `fa-beat` | Scales an icon up or down |
-| `fa-fade` | Fades an icon in and out |
-| `fa-beat-fade` | Scales and pulses an icon in and out |
-| `fa-bounce` | Bounces an icon up and down |
-| `fa-flip` | Rotates an icon about the Y axis 180 degrees |
-| `fa-shake` | Shakes an icon back and forth |
-| `fa-spin` | Roates an icon |
-{{< /table >}}
-
-## Bordered and pulled icons
-
-Use `fa-border` and `fa-pull-right` or `fa-pull-left` for easy pull quotes or article icons. The following example illustrates a quote.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* fas quote-left fa-2x fa-pull-left */>}}
-Gatsby believed in the green light, the orgastic future that year by year recedes before us.
-It eluded us then, but that’s no matter — tomorrow we will run faster, stretch our arms further...
-And one fine morning — So we beat on, boats against the current, borne back ceaselessly into the past.
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->
-
-The following table describes the available classes.
-
-{{< table "table-striped w-auto" >}}
-| Class | Details |
-|-------|---------|
-| `fa-border` | Creates a border with border-radius and padding applied around an icons |
-| `fa-pull-left` | Pulls an icon by floating it left and applying a margin-right |
-| `fa-pull-right` | Pulls an icon by floating it right and applying a margin-left |
-{{< /table >}}
-
-## Stacking icons
-
-Use the `fa-stack` class on the parent HTML element of the two icons you want to stack. Then add the `fa-stack-1x` class for the regularly sized icon and add the `fa-stack-2x` class for the larger icon. `fa-inverse` can be added to the icon with the `fa-stack-1x` to help with a knock-out looking effect. Add a [theme color]({{< ref "colors" >}}) such as `text-primary` to change the color of the icon. The following example illustrates the available options.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-<span class="fa-stack fa-2x">
-    {{</* fas square fa-stack-2x */>}}
-    {{</* fab twitter fa-stack-1x fa-inverse */>}}
-</span>
-<span class="fa-stack fa-2x">
-    {{</* fas circle fa-stack-2x */>}}
-    {{</* fas flag fa-stack-1x fa-inverse */>}}
-</span>
-<span class="fa-stack fa-2x">
-    {{</* fas camera fa-stack-1x */>}}
-    {{</* fas ban fa-stack-2x text-danger */>}}
-</span>
-<span class="fa-stack fa-4x">
-    {{</* fas square fa-stack-2x */>}}
-    {{</* fas terminal fa-stack-1x fa-inverse */>}}
-</span>
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->
-
-The following table describes the available classes.
-
-{{< table "table-striped w-auto" >}}
-| Class | Details |
-|-------|---------|
-| `fa-stack`    | Used on a parent HTML element of the two icons to be stacked |
-| `fa-stack-1x` | Used on the icon which should be displayed at base size when stacked |
-| `fa-stack-2x` | Used on the icon which should be displayed larger when stacked |
-| `fa-inverse`  | Inverts the color of the icon displayed at base size when stacked |
-{{< /table >}}

content/en/docs/0.8/content/images-and-figures.md

@@ -1,43 +0,0 @@
----
-title: Images and figures
-description: Use the image shortcode to display a responsive image with optional caption.
-date: 2023-01-28
-group: content
-layout: docs
----
-
-Hinode supports responsive images out-of-the-box. Although you can include images in your content natively with Markdown, these images are not optimized for your viewport or screen. Hinode uses Hugo's powerful [image processing]({{< param "links.hugo_image" >}}) to preprocess images on the server side. By taking advantage of so-called [image sets]({{< param "links.mozilla_image" >}}), the client's browser can decide which image to download whilst reducing the download size.
-
-## Images
-
-As an example, the following shortcode displays an image with rounded corners and a 21x9 aspect ratio. The [image shortcode documentation]({{< relref "image" >}}) provides more details.
-
-{{< alert >}}
-Be sure to store your local images in the `assets` folder to take advantage of the image processing features. Images stored in the `static` folder are not processed.
-{{< /alert >}}
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* image src="img/flowers.jpg" ratio="21x9" class="rounded" */>}}
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->
-
-You can also reference remote images by specifying an URL. Hinode downloads the image to the server and stores the processed images in the local `resources` folder (during debugging) or `public` folder (during build).
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-<div class="mx-auto w-25">
-    {{</* image src="https://picsum.photos/id/56/2880/1920" ratio="1x1" class="rounded" */>}}
-</div>
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->
-
-## Figures
-
-Similar to the [images support]({{< relref "#images" >}}), you can add a caption to display below the image. Add the argument `caption` to include a figure caption.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* image src="img/coffee.jpg" ratio="21x9" caption="Figure caption" class="rounded" */>}}
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->

content/en/docs/0.8/content/links-and-cross-references.md

@@ -1,96 +0,0 @@
----
-title: Links and cross-references
-description: Generate internal links and external links using a combination of Markdown and Hugo shortcodes.
-date: 2023-01-28
-group: content
-layout: docs
----
-
-<!-- TODO: expand -->
-
-## Internal links
-
-Hugo provides the shortcode `ref` to link to another page within the site. The shortcode returns an absolute path. You can provide the document path as input. If you omit the leading `/`, the page is first resolved relative to the current page, then to the remainder of the site. Review [Hugo's documentation]({{< param "links.hugo_links" >}}) for more examples and advanced options.
-
-{{< example lang="hugo" >}}
-[Tables]({{</*ref "tables" */>}})
-
-[About]({{</*ref "/about" */>}})
-{{< /example >}}
-
-Similar to the `ref` shortcode, Hugo provides the shortcode `relref` to return a path relative to the current page.
-
-{{< example lang="hugo" >}}
-[Tables]({{</*relref "tables" */>}})
-
-[About]({{</*relref "/about" */>}})
-{{< /example >}}
-
-## Cross-references
-
-When using Markdown document types, Hugo generates element IDs for every heading on a page. Spaces are replaced with `-`. For example:
-
-```markdown
-## An example reference
-```
-
-produces the following HTML:
-
-```html
-<h2 id="an-example-reference">An example reference</h2>
-```
-
-You can add a cross-reference to the section heading by specifying the generated ID as input for the `ref` and `relref` shortcodes, preceded by a `#`.
-
-{{< example lang="hugo" >}}
-[Reference]({{</* ref "#reference" */>}})
-
-[Reference]({{</* relref "#reference" */>}})
-{{< /example >}}
-
-## External links
-
-Hugo supports basic Markdown to create links to external websites. The following sections explain the various options.
-
-### Basic links
-
-Hugo supports basic Markdown to create links to external websites. To create a link, enclose the link text in brackets (e.g., `[Duck Duck Go]`) and then follow it immediately with the URL in parentheses (e.g., `(https://duckduckgo.com)`).
-
-{{< example lang="markdown" >}}
-My favorite search engine is [Duck Duck Go](https://duckduckgo.com).
-{{< /example >}}
-
-### URLs and email addresses
-
-To quickly turn a URL or email address into a link, enclose it in angle brackets.
-
-{{< example lang="markdown" >}}
-<https://www.markdownguide.org>
-
-<fake@example.com>
-{{< /example >}}
-
-### Reference-style links
-
-Instead of using parentheses, you can use brackets to link to a predefined address. The following example uses a named reference to link to the website of Font Awesome.
-
-{{< example lang="markdown" >}}
-[Font Awesome][fontawesome]
-
-[fontawesome]: https://fontawesome.com
-{{< /example >}}
-
-### Managed links
-
-Hinode uses `config/default/params.toml` to manage links to external addresses in a single place. You can use a combination of Markdown and Hugo shortcodes to generate a managed link. The following snippet of `config/default/params.toml` defines the link address for `fontawesome`:
-
-```toml
-[links]
-    fontawesome = "https://fontawesome.com"
-```
-
-You can then use the following statement to generate the link.
-
-{{< example lang="markdown" >}}
-[Font Awesome]({{</* param "links.fontawesome" */>}})
-{{< /example >}}

content/en/docs/0.8/content/tables.md

@@ -1,139 +0,0 @@
----
-title: Tables
-description: Enhance out-of-the-box Markdown tables with Bootstrap styling.
-date: 2023-01-22
-group: content
-layout: docs
----
-
-Hugo supports out-of-the box Markdown tables. Hinode enhances the basic tables with optional styling features provided by Bootstrap. The following paragraphs illustrate how to use basic tables, how to accent them, how to adjust the borders, and how to make the table more compact.
-
-## Basic tables
-
-Hugo supports tables out-of-the-box with extended Markdown. Use an optional shortcode as wrapper to align the table cells.
-
-### Default alignment
-
-Hugo supports tables out-of-the-box by using the `|` and `-` characters. Add `{.table}` at the bottom of the block to apply the correct styling. You can mix the content with inline Markdown.
-
-{{< example lang="markdown" >}}
-| Italics   | Bold     | Code   |
-| --------- | -------- | ------ |
-| _italics_ | **bold** | `code` |
-{.table}
-{{< /example >}}
-
-### Aligned cells and headers
-
-Hugo's Markdown processor applies inline styles to align cells in a table, which is blocked by Hinode's [Content Security Policy]({{< ref "server" >}}). Use the `table` shortcode to wrap your Markdown input instead. You can then align header and cell data to the left, center, or right of a column using the `:` character. Pass additional class attributes between double quotes, e.g. `"table-striped"`. See the [next section](#accented-tables) for more options.
-
-<!-- markdownlint-disable MD037 -->
-{{< example lang="hugo" >}}
-{{</* table "table-striped" */>}}
-| #  | Item        | Left aligned | Center aligned |   Right aligned|
-| -- | ----------- |:-------------|:--------------:| --------------:|
-| 1. | First item  | some text    | more text      | even more text |
-| 2. | Second item | some text    | more text      | even more text |
-| 3. | Third item  | some text    | more text      | even more text |
-{{</* /table */>}}
-{{< /example >}}
-<!-- markdownlint-enable MD037 -->
-
-## Accented tables
-
-Add optional class attributes to style the table using Bootstrap.
-
-### Striped rows
-
-Use `.table-striped` to add zebra-striping to any table row.
-
-{{< example lang="markdown" >}}
-| #  | Item        |
-| -- | ----------- |
-| 1. | First item  |
-| 2. | Second item |
-| 3. | Third item  |
-{.table .table-striped}
-{{< /example >}}
-
-### Striped columns
-
-Use `.table-striped-columns` to add zebra-striping to any table column.
-
-{{< example lang="markdown" >}}
-| #  | Item        | Description            |
-| -- | ----------- | ---------------------- |
-| 1. | First item  | This is the first row  |
-| 2. | Second item | This is the second row |
-| 3. | Third item  | This is the third row  |
-{.table .table-striped-columns}
-{{< /example >}}
-
-### Hoverable rows
-
-Add `.table-hover` to enable a hover state on the table rows.
-
-{{< example lang="markdown" >}}
-| #  | Item        |
-| -- | ----------- |
-| 1. | First item  |
-| 2. | Second item |
-| 3. | Third item  |
-{.table .table-hover}
-{{< /example >}}
-
-### Colored tables
-
-Add `table-<theme>` to apply [theme colors]({{< ref "colors" >}}) to your table. You can mix them with other classes, such as `.table-striped`.
-
-{{< example lang="markdown" >}}
-| #  | Item        |
-| -- | ----------- |
-| 1. | First item  |
-| 2. | Second item |
-| 3. | Third item  |
-{.table .table-success .table-striped}
-{{< /example>}}
-
-## Table borders
-
-Adjust the borders of a table to match your style preferences.
-
-### Bordered tables
-
-Add `.table-bordered` for borders on all sides of the table and cells. Add an optional `border-<theme>` class to apply [theme colors]({{< ref "colors" >}}) to the table borders.
-
-{{< example lang="markdown" >}}
-| #  | Item        |
-| -- | ----------- |
-| 1. | First item  |
-| 2. | Second item |
-| 3. | Third item  |
-{.table .table-bordered .border-primary}
-{{< /example >}}
-
-### Tables without borders
-
-Add `.table-borderless` for a table without borders.
-
-{{< example lang="markdown" >}}
-| #  | Item        |
-| -- | ----------- |
-| 1. | First item  |
-| 2. | Second item |
-| 3. | Third item  |
-{.table .table-borderless}
-{{< /example >}}
-
-## Small tables
-
-Add `.table-sm` to make any table more compact by cutting all cell padding in half.
-
-{{< example lang="markdown" >}}
-| #  | Item        |
-| -- | ----------- |
-| 1. | First item  |
-| 2. | Second item |
-| 3. | Third item  |
-{.table .table-sm}
-{{< /example >}}

content/en/docs/0.8/content/typography.md

@@ -1,219 +0,0 @@
----
-title: Typography
-description: Use a mix of Markdown and HTML syntax to style your content.
-date: 2023-01-22
-group: content
-layout: docs
----
-
-Hinode uses a mix of basic Markdown syntax enriched with Bootstrap styling for the typography. The following paragraphs illustrate the most common applications. Refer to the Hugo documentation to review the extended description of supported [content formats]({{< param "links.hugo_content" >}}). It also contains links to external resource about Markdown.
-
-## Headings
-
-Use the native Markdown character `#` to generate headings for your content. The following input represents six levels of section headings. They are generated as HTML `<h1>`—`<h6>` elements. `<h1>` is the highest section level while `<h6>` is the lowest.
-
-<!-- markdownlint-disable MD025 -->
-{{< example lang="markdown" >}}
-
-# H1. Heading
-
-## H2. Heading
-
-### H3. Heading
-
-#### H4. Heading
-
-##### H5. Heading
-
-###### H6. Heading
-
-{{< /example >}}
-<!-- markdownlint-enable MD025 -->
-
-Alternatively, you can use `.h1` through `.h6` classes, for when you want to match the font styling of a heading but cannot use the associated HTML element. For example, using a `.h2` class will exclude the section heading from the generated [table of contents]({{< ref "navigation#table-of-contents" >}}).
-
-{{< example lang="html" >}}
-<p class="h1">H1</p>
-<p class="h2">H2</p>
-<p class="h3">H3</p>
-<p class="h4">H4</p>
-<p class="h5">H5</p>
-<p class="h6">H6</p>
-{{< /example >}}
-
-## Display headings
-
-Display a larger, slightly more opinionated heading style by adding the `.display` class in HTML.
-
-{{< example lang="html" >}}
-<h1 class="display-1">Display 1</h1>
-<h1 class="display-2">Display 2</h1>
-<h1 class="display-3">Display 3</h1>
-<h1 class="display-4">Display 4</h1>
-<h1 class="display-5">Display 5</h1>
-<h1 class="display-6">Display 6</h1>
-{{< /example >}}
-
-## Lead
-
-Make a paragraph stand out by adding `.lead` class in HTML.
-
-{{< example lang="html" >}}
-<p class="lead">
-  This is a lead paragraph. It stands out from regular paragraphs.
-</p>
-{{< /example >}}
-
-## Inline text elements
-
-You can use native Markdown to apply basic styling. Use HTML elements for additional formatting options.
-
-### Native Markdown
-
-Use native Markdown apply basic styling to your text.
-
-<!-- markdownlint-disable MD049 -->
-{{< example lang="markdown" >}}
-~~This line of text is meant to be treated as deleted text.~~
-
-_This line of text renders as underlined._
-
-**This line of text renders as bold text.**
-
-*This line of text renders as italicized text.*
-{{< /example >}}
-<!-- markdownlint-enable MD049 -->
-
-### HTML Styling
-
-Use HTML tags for additional styling options. The following example illustrates highlighting, fine print, subscript, and superscript.
-
-{{< example lang="html" >}}
-<p>You can use the mark tag to <mark>highlight</mark> text.</p>
-<p><small>This line of text is meant to be treated as fine print.</small></p>
-<p>H<sub>2</sub>O is a liquid.</p>
-<p>2<sup>10</sup> is 1024.</p>
-{{< /example >}}
-
-## Emoji
-
-Use shortcodes to insert Emoji into your content. You can use this [list of emoji]({{< param "links.markdown_emoji" >}}) shortcodes as a reference, although the results may vary across browsers and devices. The following example inserts an inline smiley.
-
-<div class="bg-light p-3 mb-3">
-    That is so funny! <code>:<zero-width space>smiley:<zero-width space></code>
-</div>
-
-The result looks like this:
-
-That is so funny! :smiley:
-
-## Abbreviations
-
-Use the HTML element `<abbr>` for abbreviations and acronyms to show the expanded version on hover. Abbreviations have a default underline and gain a help cursor to provide additional context on hover and to users of assistive technologies.
-
-{{< example lang="html" >}}
-<p><abbr title="HyperText Markup Language">HTML</abbr></p>
-{{< /example >}}
-
-## Blockquotes
-
-The blockquote element represents content that is quoted from another source, optionally with a citation which must be within a `footer` or `cite` element, and optionally with in-line changes such as annotations and abbreviations. Use the `>` Markdown character to generate a blockquote and add `{.blockquote}` at the bottom of the block to apply the correct styling.
-
-### Blockquote without attribution
-
-The following Markdown generates a blockquote without attribution.
-
-{{< example lang="markdown" >}}
-> Tiam, ad mint andaepu dandae nostion secatur sequo quae.
-> **Note** that you can use _Markdown syntax_ within a blockquote.
-{.blockquote}
-{{< /example >}}
-
-### Blockquote with attribution
-
-The following Markdown generates a blockquote with attribution. The citation itself is added to the bottom of the page.
-
-{{< example lang="markdown" >}}
-> Don't communicate by sharing memory, share memory by communicating.<br>
-> — <cite>Rob Pike[^1]</cite>
-{.blockquote}
-
-[^1]: The above quote is excerpted from Rob Pike's [talk](https://www.youtube.com/watch?v=PAAkCSZUG1c) during Gopherfest, November 18, 2015.
-{{< /example >}}
-
-## Code Blocks
-
-Use a single backtick `` ` `` character to denote an inline code element. Use triple backticks `` ``` `` to denote the start and end of a code block. Add the language to the opening backticks to specify the syntax. Hugo uses Chroma highlighting to style the syntax of [supported languages]({{< param "links.hugo_chroma" >}}). The following example defines an `HTML` code block.
-
-{{< example lang="markdown" >}}
-
-```html
-<!DOCTYPE html>
-<html lang="en">
-  <head>
-    <meta charset="utf-8">
-    <title>Example HTML5 Document</title>
-  </head>
-  <body>
-    <p>Test</p>
-  </body>
-</html>
-```
-
-{{< /example >}}
-
-## List Types
-
-Use native Markdown to define ordered lists, unordered lists, and nested lists.
-
-### Ordered List
-
-The following Markdown defines an ordered list of three items. The sequence is automatically determined, so simply add `1.` at the start of each element. The [linting rules]({{< ref "contribute#markdown" >}}) will raise an error if you add the sequence numbering yourself.
-
-{{< example lang="markdown" >}}
-
-1. First item
-1. Second item
-1. Third item
-
-{{< /example >}}
-
-### Unordered List
-
-Use the `-` character to denote an unordered list.
-
-{{< example lang="markdown" >}}
-
-- List item
-- Another item
-- And another item
-
-{{< /example >}}
-
-### Nested list
-
-Use indendation and the `-` character to denote a nested list.
-
-{{< example lang="markdown" >}}
-
-- Fruit
-  - Apple
-  - Orange
-  - Banana
-- Dairy
-  - Milk
-  - Cheese
-
-{{< /example >}}
-
-### Task list
-
-Use the `-` character followed by either `[x]` or `[ ]` to indicate a (completed) task.
-
-{{< example lang="markdown" >}}
-
-- [x] Write the press release
-- [ ] Update the website
-- [ ] Contact the media
-
-{{< /example >}}

content/en/docs/0.8/getting-started/commands.md

@@ -1,75 +0,0 @@
----
-title: Commands
-description: Use npm commands to automate the build process and to keep track of dependencies.
-date: "2023-01-11"
-group: getting-started
-layout: docs
----
-
-Hinode uses [Node Package Manager]({{< param "links.npm" >}}) to automate the build process and to keep track of dependencies. The `package.json` file in the repository root defines several commands to simplify local development and testing. The following paragraphs describe the main commands.
-
-## Starting a local server
-
-Use the following command from the command prompt to start a local **development server**. The command removes any previous build artifacts in the `public` and `resources` folders. The command invokes the local web server from Hugo, which watches for changes in the key system files and configuration directory. By default the generated site is available at `http://localhost:1313/` and is responsive to changes. This alllows for interactive development and testing. When in development mode, the generated assets (such as javascripts and CSS files) are not minified to simplify debugging.
-
-{{% command %}}
-npm run start
-{{% /command %}}
-
-Use the following command to mimick the site in **production mode**. In this setting, generated assets are minified and compliant with the Content Security Policy. Although Hugo's web server is not meant to be run in a real production environment, it does allow validation of the site in an environment close to production.
-
-{{% command %}}
-npm run prod
-{{% /command %}}
-
-## Generating a web site
-
-Use the following command to generate the static site. The build artifacts are stored in the local `public` folder. You can deploy these files to your **production** server.
-
-{{% command %}}
-npm run build
-{{% /command %}}
-
-Add the prefix `debug` to generate a site suitable for **debugging**. The build artifacts are not minified to simplify review and testing.
-
-{{% command %}}
-npm run build:debug
-{{% /command %}}
-
-## Validating linting rules
-
-Use the the following command to analyze the source code and to test for any stylistic errors. The lint command validates three types of files in the `assets` folder and `content` folder:
-
-* Javascript (`assets/*.js`) using [eslint]({{< param "links.eslint" >}}).
-* CSS and SASS (`assets/scss/**/*.{css,sass,scss,sss,less}`) using [stylelint]({{< param "links.stylelint" >}}).
-* Markdown (`*.md` and `content/**/*.md`) using [markdownlint-cli2]({{< param "links.markdownlint" >}}).
-
-The basic configuration of these linting tools is defined in the repository root.
-
-{{% command %}}
-npm run lint
-{{% /command %}}
-
-Be sure to adhere to the linting rules before submitting any code changes / Pull Requests to Hinode's repository.
-
-## Upgrading dependencies
-
-Use the following command to test for any available upgrades of used packages. The command runs `npx` to validate the dependencies and to upgrade the dependency versions in `package.json`.
-
-{{% command %}}
-npm run upgrade
-{{% /command %}}
-
-The `npx` command does not validate the version of the Hugo binary. The version needs to be manually updated in the `package.json` file.
-
-```json
-  "otherDependencies": {
-    "hugo": "0.109.0"
-  }
-```
-
-Be sure to install the upgraded dependencies if needed:
-
-{{% command %}}
-npm install
-{{% /command %}}

content/en/docs/0.8/getting-started/contribute.md

@@ -1,124 +0,0 @@
----
-title: Contribute
-description: Contribute to the open-source development of Hinode.
-date: 2023-01-06
-group: getting-started
-layout: docs
----
-
-Hinode is fully open source and welcomes any contributions, either big or small. To streamline the contribution process, please take a moment to review the guidelines outlined in this article.
-
-## Using the issue tracker
-
-The [issue tracker]({{< param "links.issue_tracker" >}}) on GitHub is the preferred channel for bug reports, feature requests and submitting pull requests.
-
-## Bug reports
-
-A bug is a *demonstrable problem* that is caused by the code in the repository. This may also include issues with the documentation or configuration files. Before filing a bug report, please consider the following guidelines:
-
-- Validate your HTML and Markdown content to ensure your problem isn't caused by a simple error in your own code.
-- Use the GitHub [issue search]({{< param "links.issue_tracker" >}}) — check if the issue has already been reported.
-- Check if the issue has been fixed — try to reproduce it using the latest main in the [repository]({{< param "links.repository" >}}).
-- Isolate the problem — ideally create a reduced test case.
-- Use the provided template in the [issue tracker]({{< param "links.issue_tracker" >}}) to capture the context, evidence and steps on how to reproduce the issue.
-
-## Feature requests
-
-Feature requests are welcome. But take a moment to find out whether your idea fits with the scope and aims of the project. Please use the provided template in the [issue tracker]({{< param "links.issue_tracker" >}}) to capture the idea and context.
-
-## Pull requests
-
-Good pull requests—patches, improvements, new features—are a fantastic help. They should remain focused in scope and avoid containing unrelated commits.
-
-**Please ask first** before embarking on any **significant** pull request (e.g. implementing features, refactoring code, porting to a different language), otherwise you risk spending a lot of time working on something that the project's developers might not want to merge into the project. For trivial things, or things that don't require a lot of your time, you can go ahead and make a PR.
-
-Please adhere to the [coding guidelines](#coding-guidelines) used throughout the project (indentation, accurate comments, etc.) and any other requirements (such as test coverage).
-
-Adhering to the following process is the best way to get your work included in the project:
-
-1. Fork the project, clone your fork, and configure the remotes:
-
-    ```bash
-    git clone https://github.com/<your-username>/hinode.git
-    cd hinode
-    git remote add upstream https://github.com/gethinode/hinode
-    ```
-
-1. If you cloned a while ago, get the latest changes from upstream:
-
-    ```bash
-    git checkout main
-    git pull upstream main
-    ```
-
-1. Create a new topic branch (off the main project development branch) to contain your feature, change, or fix:
-
-    ```bash
-    git checkout -b <topic-branch-name>
-    ```
-
-1. Commit your changes in logical chunks. Please adhere to these [git commit message guidelines]({{< param "links.commit_message" >}}). Use Git's [interactive rebase]({{< param "links.github_rebase" >}}) feature to tidy up your commits before making them public.
-
-1. Locally merge (or rebase) the upstream development branch into your topic branch:
-
-    ```bash
-    git pull [--rebase] upstream main
-    ```
-
-1. Push your topic branch up to your fork:
-
-    ```bash
-    git push origin <topic-branch-name>
-    ```
-
-1. Open a [Pull Request]({{< param "links.github_pr" >}}) with a clear title and description against the main branch.
-
-{{< alert >}}
-**IMPORTANT**: By submitting a patch, you agree to allow the project owners to license your work under the terms of the [MIT license]({{< param "links.license" >}}) (if it includes code changes) and under the terms of the Creative Commons ([CC BY-NC 4.0)]({{< param "links.cc_by_nc_4_0" >}}) license (if it includes documentation changes).
-{{< /alert >}}
-
-## Coding guidelines
-
-In general, run `npm run lint` before committing to ensure your changes follow our coding standards.
-
-### HTML
-
-[Adhere to the Code Guide]({{< param "links.html_codeguide" >}}).
-
-- Use tags and elements appropriate for an HTML5 doctype (e.g., self-closing tags).
-- Use npm packages for third-party JS when possible.
-- Use WAI-ARIA attributes in documentation examples to promote accessibility.
-
-### CSS
-
-[Adhere to the Code Guide]({{< param "links.css_codeguide" >}}).
-
-- When feasible, default color palettes should comply with [WCAG color contrast guidelines]({{< param "links.wcag_contrast" >}}).
-
-### Javascript
-
-Bundle related client-side javascript in a logically named file. Add the file to the `assets/js` when using Hugo templating. Adjust the eslint configuration as needed to handle necessary exceptions. When adapting someone else's code, please add a link to the original source to give them credit.
-
-- No semicolons (in client-side JS)
-- 2 spaces (no tabs)
-- strict mode
-- "Attractive"
-
-### Markdown
-
-See [markdown rules]({{< param "links.markdown_rules" >}}) for more details. The following rules are globally disabled:
-
-| #     | Rule | Remarks |
-|-------|-----------------------------------------------------------------------------------------------|---------------------------------|
-| MD013 | [Line length]({{< param "links.markdown_md013" >}})                                           | |
-| MD024 | [Multiple headings with the same content]({{< param "links.markdown_md024" >}})               | |
-| MD026 | [Trailing punctuation in heading]({{< param "links.markdown_md026" >}})                       | |
-| MD033 | [Inline HTML]({{< param "links.markdown_md033" >}})                                           | |
-| MD034 | [Bare URL used]({{< param "links.markdown_md034" >}})                                         | |
-| MD051 | [Link fragments should be valid]({{< param "links.markdown_md051" >}})                        | |
-| MD053 | [Link and image reference definitions should be needed]({{< param "links.markdown_md053" >}}) | Disabled due to false positives |
-{.table}
-
-## License
-
-By contributing your code, you agree to license your contribution under the [MIT license]({{< param "links.license" >}}). By contributing to the documentation, you agree to license your contribution under the Creative Commons ([CC BY-NC 4.0)]({{< param "links.cc_by_nc_4_0" >}}) license.