Version 6
See the changelog of this version for a detailed list of changes.-
0.126.0 Minimum required Hugo version
-
Breaking Change requiring action after upgrade
-
Change Change of behavior, may require action
-
New New behavior, often introducing new options
6.4.0 (2024-10-11)
Change
- Change If you now display a single code block in a
notice
box, its margin and border will be removed so only the colored notice border is visible.
New
-
New It is now possible to have user-defined styles for all shortcodes that accept the
style
parameter. See thenotice
shortcode for configuration. -
New The
resources
shortcode has a new parameterexpanded
to make the resource list collapsible.
6.3.0 (2024-09-03)
Change
-
Change The
expand
shortcode changed the naming of theopen
parameter toexpanded
. You don’t need to change anything yet but may get deprecation warnings. -
Change If the content for the
notice
shortcode is empty, now only the title bar will be displayed. Previously an empty content box was displayed.
New
-
New The
notice
shortcode has a new parameterexpanded
to make the content collapsible. -
New If you are running Hugo 0.134.0 or later, the theme now supports Obsidian callouts.
-
New The theme has updated its Mermaid dependency to 11.1.0. This adds support for packet and architecture diagrams.
6.2.0 (2024-08-26)
Change
-
Change The heading anchor links are extended in functionality.
If you now click on it, not only is the link copied to the clipboard (previous behavior) but also the heading scrolls to the top of the page.
If you dislike the new behavior, you can deactivate it by setting
disableAnchorScrolling=true
in yourhugo.toml
. See the docs for further options.
New
-
New If you are running Hugo 0.132.0 or later, the theme is now capable to print GitHub alerts.
-
New To support new severity levels for GitHub alerts, all shortcodes that support severity levels with their
style
parameter were expanded with the new severitiescaution
andimportant
and thecolor
parameter was expanded withcyan
andmagenta
. Please note, that coloring and icons of severities may defer from the display you see on GitHub. -
New To support new severity levels for GitHub alerts, the new severities and their according colors are also available as CSS variables
BOX-MAGENTA-color
,BOX-MAGENTA-TEXT-color
,BOX-CAUTION-color
,BOX-CAUTION-TEXT-color
,BOX-CYAN-color
,BOX-CYAN-TEXT-color
,BOX-IMPORTANT-color
,BOX-IMPORTANT-TEXT-color
. You don’t need to change anything in your custom color stylesheet as appropriate default colors will be used.
6.1.0 (2024-08-02)
Change
-
Change The
include
shortcode is now able to resolve links to pages as well as resources or files in the file system (the old behavior). -
Change To make the asset buster mechanism more robust, some internally used stylesheets where restructured. This generally should not affect your page in any negative way.
New
-
New The
openapi
shortcode is now able to resolve links to resources as well as to files in the file system (the old behavior). You can configure to generate warnings or errors during build by settingopenapi.errorlevel
to eitherwarning
orerror
in yourhugo.toml
if a path can not be resolved. -
New Shortcodes supporting an
errorlevel
configuration can now have overridden values in the front matter section of each individual page. -
New The theme now comes with its own overridden version of the
relref
shortcode.While the usage of
relref
is obsolete and discouraged by Hugo for a while, existing installations may use it. In configurations using abaseURL
with a subdirectory, and havingrelativeURLs=false
(the default) Hugo’s standardrelref
implementation was failing.The shortcode is deactivated by default and can be activated by setting
hugo.[params] disableDefaultRelref = true
params: disableDefaultRelref: true
{ "params": { "disableDefaultRelref": true } }
in your
hugo.toml
. Only do this if your site fulfills all of the above assumptions.
6.0.0 (2024-04-27)
Breaking
-
Breaking This release requires you to move your self-defined variant (
theme-*.css
) and chroma stylesheets (chroma-*.css
) fromstatic/css
toassets/css
.This was necessary to avoid permission errors on build if running in certain Unix configurations.
In addition it is not allowed anymore to
@import
your chroma stylesheet from inside of your variant stylesheet.Say, your chroma stylesheet is named
chroma-monokai.css
, you have to add the following inside your variant stylesheet:--CODE-theme: monokai;
-
Breaking The parameter
description
in yourhugo.toml
will now be ignored.With the newly introduced unified handling of descriptions throughout the theme, the only place the old parameter would have been used was your home page.
For migration, move the
description
parameter of yourhugo.toml
into the front matter section of your home page. -
Breaking Search support for the
json
outputformat deprecated in 5.4.0 was removed.Change it to
search
for the homepage in yourhugo.toml
. See the docs for detailed configuration. -
Breaking The front matter option
menuTitle
deprecated in 5.24.0 was removed in favor for Hugo’s ownlinkTitle
.Additionally, if set,
linkTitle
will now be used instead oftitle
to generate the breadcrumb. -
Breaking The
swagger
shortcode deprecated in 5.13.0 was removed in favor for theopenapi
shortcode with the same set of parameter. -
Breaking Support for Internet Explorer 11 was finally dropped.
Change
-
Change With the removal of support for Internet Explorer 11, Font Awesome was upgraded to version 6.5.2.
You may experience slight changes for some icons. In addition you have additional ~1700 icons to chose from.
-
Change The
children
shortcode was fixed to adhere to its documentation, generating the description based on this rule: When no description or summary exists for the page, the first 70 words of the content is taken.Previously, the summary erroneously was ignored which now can lead to different output if you set
description=true
as a parameter.
New
-
New The
include
shortcode is now able to resolve links to resources as well as to files in the file system (the old behavior). You can configure to generate warnings or errors during build by settinginclude.errorlevel
to eitherwarning
orerror
in yourhugo.toml
if a path can not be resolved. -
New Math is now usable without enclosing it in a shortcode or Markdown codefence by using Hugo’s passthrough configuration.
-
New Translation into Romanian.