Discover what this Hugo theme is all about and the core-concepts behind it.
Discover what this Hugo theme is all about and the core-concepts behind it.
This document shows you what’s new in the latest release. For a detailed list of changes, see the history page.
0.95.0 The minimum required Hugo version.
Breaking A change that requires action by you after upgrading to assure the site is still functional.
Change A change in default behavior that may requires action by you if you want to revert it.
New Marks new behavior you might find interesting or comes configurable.
--ACCENT-color brand color introduced in version 5.8.0 is now supported with these shortcodes.
Change The required folder name for the
attachments shortcode was changed for leaf bundles.
Previously, the attachments for leaf bundles in non-multilang setups were required to be in a
files subdirectory. For page bundles and leaf bundles in multilang setups they were always required to be in a
index.<LANGCODE>.files subdirectory accordingly.
This added unnessessary complexity. So attachments for leaf bundles in non-multilang setups can now also reside in a
index.files directory. Although the old
files directory is now deprecated, if both directories are present, only the old
files directory will be used for compatiblity.
Change Absolute links prefixed with
https:// are now opened in a separate browser tab.
You can revert back to the old behavior by defining
externalLinkTarget="_self" in the
params section of your
New The theme now supports Hugo’s module system.
New The new
badge shortcode is now available to add highly configurable markers to your content as you can see it on this page.
New The new
icon shortcode simplyfies the usage of icons. This can even be combined with also new
New A new color
--ACCENT-color was introduced which is used for highlightning search results on the page. In case you simply don’t care, you don’t need to change anything in your variant stylesheet as the old
yellow color is still used as default.
Change The Korean language translation for this theme is now available with the language code
ko. Formerly the country code
kr was used instead.
button shortcode can now also be used as a real button inside of HTML forms - although this is a pretty rare use case. The documentation was updated accordingly.
New The search now supports the Korean language.
New This release introduces an additional dedicated search page. On this page, displayed search results have more space making it easier scanning thru large number of results.
To activate this feature, you need to configure it in your
config.toml as a new outputformat
SEARCHPAGE for the home page. If you don’t configure it, no dedicated search page will be accessible and the theme works as before.
You can access the search page by either clicking on the magnifier glass or pressing enter inside of the search box.
New Keyboard handling for the TOC and search was improved.
CTRL+ALT+t now will not only toggle the TOC overlay but also places the focus to the first heading on opening. Subsequently this makes it possible to easily select headings by using the
The search received its own brand new keyboard shortcut
CTRL+ALT+f. This will focus the cursor inside of the the search box so you can immediately start your search by typing.
New You are now able to turn off the generation of generator meta tags in your HTML head to hide the used versions of Hugo and this theme.
To configure this in your
config.toml make sure to set Hugo’s
disableHugoGeneratorInject=true and also
[params] disableGeneratorVersion=true, otherwise Hugo will generate a meta tag into your home page automagically.
New Creation of your project gets a little bit faster with this release.
This addresses increased build time with the 5.x releases. The theme now heavily caches partial results leading to improved performance. To further increase performance, unnecessary parts of the page are now skipped for creation of the print output (eg. menus, navigation bar, etc.).
Change The way images are processed has changed. Now images are lazy loaded by default which speeds up page load on slow networks and/or big pages and also the print preview.
If you have used HTML directly in your Markdown files, this now has the downside that it doesn’t respect the effect query parameter anymore. In this case you have to migrate all your HTML
img URLs manually to the respective HTML attributes.
Change With the proper settings in your
config.toml your page is now servable from the local file system using
Please note that the searchbox will only work for this if you reconfigure your outputformat for the homepage in your
SEARCH. The now deprecated
JSON outputformat still works as before, so there is no need to reconfigure your installation if it is only served from
button shortcode has a new parameter
target to set the destination frame/window for the URL to open. If not given, it defaults to a new window/tab for external URLs or is not set at all for internal URLs. Previously even internal URLs where opened in a new window/tab.
New Support for languages that are written right to left (like Arabic). This is only implemented for the content area but not the navigation sidebar. This feature is not available in Internet Explorer 11.
New Translation for Finnish (Suomi).
Change In the effort to comply with WCAG standards, the implementation of the collapsible menu was changed. Although the functionality of the new implementation works with old browsers (Internet Explorer 11), the display of the expander icons does not and is limited to modern browsers.
New Image formatting has two new classes to align images to the
right. Additionally, the already existing
inline option is now documented.
collapsibleMenu = truein your
config.toml, the menu will be expanded if a search term is found in a collapsed submenu. The menu will return to its initial collapse state once the search term does not match any submenus.
0.95.0 This release requires a newer Hugo version.
Change Because the print preview URLs were non deterministic for normal pages in comparison to page bundles, this is now changed. Each print preview is now accessible by adding a
index.print.html to the default URL.
You can revert this behavior by overwriting the PRINT output format setting in your
[outputFormats] [outputFormats.PRINT] name= "PRINT" baseName = "index" path = "_print" isHTML = true mediaType = 'text/html' permalinkable = false
*.js file (if not already) and add the
defer keyword to the
script element. Eg.
<script defer src="myscript.js"></script>
Change The way archetypes are used to generate output has changed. The new systems allows you, to redefine existing archetypes or even generate your own ones.
Your existing markdown files will still work like before and therefore you don’t need to change anything after the upgrade. Nevertheless, it is recommended to adapt your existing markdown files to the new way as follows:
for your home page, add the frontmatter parameter
archetype = "home" and remove the leading heading
for all files containing the deprecated frontmatter parameter
chapter = true, replace it with
archetype = "chapter" and remove the leading headings
Change The frontmatter options
post were renamed to
menuPost. The old options will still be used if the new options aren’t set. Therefore you don’t need to change anything after the upgrade.
New Adding new partials
heading-post.html and according frontmatter options
headingPost to modify the way your page`s main heading gets styled.
New The new shortcode
math is available to add beautiful math and chemical formulae. See the documentation for available features. This feature will not work with Internet Explorer 11.
Breaking The second parameter for the
include shortcode was switched in meaning and was renamed from
hidefirstheading. If you haven’t used this parameter in your shortcode, the default behavior hasn’t changed and you don’t need to change anything.
If you’ve used the second boolean parameter, you have to rename it and invert its value to achieve the same behavior.
Change Previously, if the
tabs shortcode could not find a tab item because, the tabs ended up empty. Now the first tab is selected instead.
landingPageURL was removed from
config.toml. You can safely remove this as well from your configuration as it is not used anymore. The theme will detect the landing page URL automatically.
New All shortcodes can now be also called from your partials. Examples for this are added to the documentation of each shortcode.
custom_css config parameter was removed from the configuration. If used in an existing installation, it can be achieved by overriding the
custom-header.html template in a much more generic manner.
Breaking Because anchor hover color was not configurable without introducing more complexity to the variant stylesheets, we decided to remove
--MAIN-ANCHOR-color instead. You don’t need to change anything in your custom color stylesheet as the anchors now get their colors from
New All shortcodes now support named parameter. The positional parameter are still supported but will not be enhanced with new features, so you don’t need to change anything in your installation.
button shortcode received some love and now has a parameter for the color style similar to other shortcodes.
New New colors
--SECONDARY-color were added to provide easier modification of your custom style. Shortcodes with a color style can now have
secondary as additional values.
These two colors are the default for other, more specific color variables. You don’t need to change anything in your existing custom color stylesheets as those variables get reasonable default values.
New The documentation for all shortcodes were revised.
Breaking If you had previously overwritten the
custom-footer.html partial to add visual elements below the content of your page, you have to move this content to the new partial
New If you prefer expandable/collapsible menu items, you can now set
collapsibleMenu=true in your
config.toml. This will add arrows to all menu items that contain sub menus. The menu will expand/collapse without navigation if you click on an arrow.
New You can activate print support in your
config.toml to add the capability to print whole chapters or even the complete site.
New Translation for Traditional Chinese.
New Introduction of new CSS variables to set the font. The theme distinguishes between
--MAIN-font for all content text and
--CODE-font for inline or block code. There are additional overrides for all headings. See the theme variant generator of the exampleSite for all available variables.
New The new shortcode
swagger is available to include a UI for REST OpenAPI Specifications. See the documentation for available features. This feature will not work with Internet Explorer 11.
0.93.0 This release requires a newer Hugo version.
disableMermaid config option as follows: If a Mermaid shortcode or codefence is found, the option will be ignored and Mermaid will be loaded regardlessly.
The option is still useful in case you are using scripting to set up your graph. In this case no shortcode or codefence is involved and the library is not loaded by default. In this case you can set
disableMermaid=false in your frontmatter to force the library to be loaded. See the theme variant generator of the exampleSite for an example.
This change requires at least Hugo 0.93.0 to be used. The minimum requirement will be reported during build on the console if not met.
New Additional color variant variable
--MERMAID-theme to set the variant’s Mermaid theme. This causes the Mermaid theme to switch with the color variant if it defers from the setting of the formerly selected color variant.
noticeshortcodes have a new parameter to override the default icon. Allowed values are all Font Awesome 5 Free icons.
Breaking We made changes to the menu footer. If you have your
menu-footer.html partial overridden, you may have to review the styling (eg. margins/paddings) in your partial. For a reference take a look into the
menu-footer.html partial that is coming with the exampleSite.
This change was made to allow your own menu footer to be placed right after the so called prefooter that comes with the theme (containing the language switch and Clear history functionality).
Breaking We have changed the default colors from the original Learn theme (the purple menu header) to the Relearn defaults (the light green menu header) as used in the official documentation.
This change will only affect your installation if you’ve not set the
themeVariant parameter in your
config.toml. If you still want to use the Learn color variant, you have to explicitly set
themeVariant="learn" in your
Note, that this will also affect your site if viewed with Internet Explorer 11 but in this case it can not be reconfigured as Internet Explorer does not support CSS variables.
Change Due to a bug, that we couldn’t fix in a general manner for color variants, we decided to remove
--MENU-SEARCH-BOX-ICONS-color and introduced
--MENU-SEARCH-color instead. You don’t need to change anything in your custom color stylesheet as the old name will be used as a fallback.
Change For consistency reasons, we renamed
--MENU-SEARCH-BORDER-color. You don’t need to change anything in your custom color stylesheet as the old name will be used as a fallback.
New With this release you are now capable to define your own dark mode variants.
To make this possible, we have introduced a lot more color variables you can use in your color variants. Your old variants will still work and don’t need to be changed as appropriate fallback values are used by the theme. Nevertheless, the new colors allow for much more customization.
To see what’s now possible, see the new variants
neon that are coming with this release.
New To make the creation of new variants easier for you, we’ve added a new interactive theme variant generator. This feature will not work with Internet Explorer 11.
New You can now configure multiple color variants in your
config.toml. In this case, the first variant is the default chosen on first view and a variant switch will be shown in the menu footer. See the documentation for configuration.
Note, that the new variant switch will not work with Internet Explorer 11 as it does not support CSS variables. Therefore, the variant switcher will not be displayed with Internet Explorer 11.
Breaking This release removes the themes implementation of
relref in favor for Hugos standard implementation. This is because of inconsistencies with the themes implementation. In advantage, your project becomes standard compliant and exchanging this theme in your project to some other theme will be effortless.
In a standard compliant form you must not link to the
*.md file but to its logical name. You’ll see, referencing other pages becomes much easier. All three types result in the same reference:
If you’ve linked from a page of one language to a page of another language, conversion is a bit more difficult but Hugo got you covered as well.
Also, the old themes implementation allowed refs to non-existing content. This will cause Hugos implementation to show the error below and abort the generation. If your project relies on this old behavior, you can reconfigure the error handling of Hugos implementation.
In the best case your usage of the old implementation is already standard compliant and you don’t need to change anything. You’ll notice this very easily once you’ve started
hugo server after an upgrade and no errors are written to the console.
You may see errors on the console after the update in the form:
ERROR 2021/11/19 22:29:10 [en] REF_NOT_FOUND: Ref "basics/configuration/_index.md": "hugo-theme-relearn\exampleSite\content\_index.en.md:19:22": page not found
In this case, you must apply one of two options:
Copy the old implementation files
theme/hugo-theme-relearn/layouts/shortcode/relref.html to your own projects
layouts/shortcode/relref.html respectively. This is not recommended as your project will still rely on non-standard behavior afterwards.
Start up a text editor with regular expression support for search and replace. Apply the following conversions in the given order on all
*.md files. This is the recommended choice.
Change Although never officially documented, this release removes the font
Novecento. If you use it in an overwritten CSS please replace it with
Work Sans. This change was necessary as Novacento did not provide all Latin special characters and lead to mixed styled character text eg. for Czech.
New The theme now supports favicons served from
static/images/ named as
logo in SVG, PNG or ICO format out of the box. An overridden partial
layouts/partials/favicon.html may not be necessary anymore in most cases.
New You can hide the table of contents menu for the whole site by setting the
disableToc option in your
config.toml. For an example see the example configuration.
noticeshortcode to set title in box header.
config.toml. See the documentation for a detailed example.
--CODE-BLOCK-BG-colorwere added to provide a fallback for Hugos syntax highlighting in case
guessSyntax=trueis set. Ideally the colors are set to the same values as the ones from your chosen chroma style.
Change Creation of customized stylesheets was simplified down to only contain the CSS variables. Everything else can and should be deleted from your custom stylesheet to assure everything works fine. For the predefined stylesheet variants, this change is already included.
New Hidden pages are displayed by default in their according tags page. You can now turn off this behavior by setting
disableTagHiddenPages=true in your
New You can define the expansion state of your menus for the whole site by setting the
alwaysopen option in your
config.toml. Please see further documentation for possible values and default behavior.
New New frontmatter
ordersectionsby option to change immediate children sorting in menu and
children shortcode. Possible values are
New Alternate content of a page is now advertised in the HTML meta tags. See Hugo documentation.
0.81.0 This release requires a newer Hugo version.
New Showcase multilanguage features by providing a documentation translation “fer us pirrrates”. There will be no other translations besides the original English one and the Pirates one due to maintenance constraints.
0.69.0 This release requires a newer Hugo version.
Change In case the site’s structure contains additional *.md files not part of the site (eg files that are meant to be included by site pages - see
CHANGELOG.md in the exampleSite), they will now be ignored by the search.
New Hidden pages are indexed for the site search by default. You can now turn off this behavior by setting
disableSearchHiddenPages=true in your
New If a search term is found in an
expand shortcode, the expand will be opened.
New The menu will scroll the active item into view on load.
Change Syntax highlighting was switched to the built in Hugo mechanism. You may need to configure a new stylesheet or decide to roll you own as described on in the Hugo documentation
Change In the predefined stylesheets there was a typo and
--MENU-HOME-LINK-HOVERED-color must be changed to
--MENU-HOME-LINK-HOVER-color. You don’t need to change anything in your custom color stylesheet as the old name will be used as a fallback.
--MENU-HOME-LINK-HOVER-color were missing in the documentation. You should add them to your custom stylesheets if you want to override the defaults.
Change Arrow navigation and
children shortcode were ignoring setting for
ordersectionsby. This is now changed and may result in different sorting order of your sub pages.
Change If hidden pages are accessed directly by typing their URL, they will be exposed in the menu.
Change A page without a
title will be treated as
New You can define the expansion state of your menus in the frontmatter. Please see further documentation for possible values and default behavior.
New New partials for defining pre/post content for menu items and the content. See documentation for further reading.
children with new parameter
New New shortcode
include to include arbitrary file content into a page.
expandwith new parameter to open on page load.
Mermaidconfig options can be set in
0.65.0 The version requirement for Hugo is the same as for the Learn theme version 2.5.0 on 2021-07-01.
New Initial fork of the Learn theme based on Learn 2.5.0 on 2021-07-01. This introduces no new features besides a global rename to
Relearn and a new logo. For the reasons behind forking the Learn theme, see this comment in the Learn issues.
Thanks to the simplicity of Hugo, this page is as empty as this theme needs requirements.
Just download at leat version 0.95.0 of the Hugo binary for your OS (Windows, Linux, Mac).
The following steps are here to help you initialize your new website. If you don’t know Hugo at all, we strongly suggest you learn more about it by following this great documentation for beginners.
Hugo provides a
new command to create a new website.
hugo new site <new_project>
Install the Relearn theme by following this documentation using Hugo’s module system.
This theme’s repository is: https://github.com/McShelby/hugo-theme-relearn.git
Alternatively, you can download the theme as .zip file and extract it in the
When building the website, you can set a theme by using
--theme option. However, we suggest you modify the configuration file (
config.toml) and set the theme as the default. You can also add the
[outputs] section to enable the search functionality.
# Change the default theme to be use when building the site with Hugo theme = "hugo-theme-relearn" # For search functionality [outputs] home = [ "HTML", "RSS", "SEARCH"]
Chapters are pages that contain other child pages. It has a special layout style and usually just contains a chapter name, the title and a brief abstract of the section.
### Chapter 1 # Basics Discover what this Hugo theme is all about and the core concepts behind it.
The Relearn theme provides archetypes to create skeletons for your website. Begin by creating your first chapter page with the following command
hugo new --kind chapter basics/_index.md
By opening the given file, you should see the property
chapter=true on top, meaning this page is a chapter.
By default all chapters and pages are created as a draft. If you want to render these pages, remove the property
draft: true from the metadata.
Then, create content pages inside the previously created chapter. Here are two ways to create content in the chapter:
hugo new basics/first-content.md hugo new basics/second-content/_index.md
Feel free to edit those files by adding some sample content and replacing the
title value in the beginning of the files.
Launch by using the following command:
You should notice three things:
titleproperties in the previously created files.
hugo serve, when the contents of the files change, the page automatically refreshes with the changes. Neat!
When your site is ready to deploy, run the following command:
public folder will be generated, containing all static content and assets for your website. It can now be deployed on any web server.
On top of Hugo global configuration, the Relearn theme lets you define the following parameters in your
config.toml (here, values are default).
Note that some of these parameters are explained in details in other sections of this documentation.
If your site is served from a subfolder, eg.
https://example.com/mysite/, you have to set the following lines to your
baseURL = "https://example.com/mysite/" canonifyURLs = true relativeURLs = true
canonifyURLs=true URLs in sublemental pages (like
rss.xml) will be generated falsly while your HTML files will still work. See https://github.com/gohugoio/hugo/issues/5226.
If you want your page served from the filesystem by using URLs starting with
file:// you’ll need the following configuration in your
relativeURLs = true
The theme will append an additional
index.html to all branch bundle links by default to make the page be servable from the file system. If you don’t care about the file system and only serve your page via a webserver you can also generate the links without this change by adding this to your
[params] disableExplicitIndexURLs = true
If you want to use the search feature from the file system using an older installation of the theme make sure to change your outputformat for the homepage from the now deprecated
SEARCH as seen below.
If not already present, add the following lines in the same
[outputs] home = ["HTML", "RSS", "SEARCH"]
SEARCH outputformat was named
JSON in previous releases but was implemented differently. Although
JSON still works, it is now deprecated.
You can add a dedicated search page for your page by adding the
SEARCHPAGE outputformat to your home page by adding the following lines in your
[outputs] home = ["HTML", "RSS", "SEARCH", "SEARCHPAGE"]
You can access this page by either clicking on the magnifier glass or by typing some search term and pressing
ENTER inside of the menu’s search box .
You can activate print support to add the capability to print whole chapters or even the complete site. Just add the
config.toml as seen below:
[outputs] home = ["HTML", "RSS", "PRINT", "SEARCH"] section = ["HTML", "RSS", "PRINT"] page = ["HTML", "RSS", "PRINT"]
This will add a little printer icon in the top bar. It will switch the page to print preview when clicked. You can then send this page to the printer by using your browser’s usual print functionality.
The resulting URL will not be configured ugly in terms of Hugo’s URL handling even if you’ve set
uglyURLs=true in your
config.toml. This is due to the fact that for one mime type only one suffix can be configured.
Nevertheless, if you’re unhappy with the resulting URLs you can manually redefine
outputFormats.PRINT in your own
config.toml to your liking.
The MathJax configuration parameters can also be set on a specific page. In this case, the global parameter would be overwritten by the local one. See Math for additional documentation.
MathJax is globally disabled. By default it won’t be loaded by any page.
You also can disable MathJax for specific pages while globally enabled.
The Mermaid configuration parameters can also be set on a specific page. In this case, the global parameter would be overwritten by the local one. See Mermaid for additional documentation.
Mermaid is globally disabled. By default it won’t be loaded by any page.
You also can disable Mermaid for specific pages while globally enabled.
disableLandingPageButton option is set to
false, a Home button will appear
on the left menu. It is an alternative for clicking on the logo. To edit the
appearance, you will have to configure two parameters for the defined languages:
[Languages] [Languages.en] ... landingPageName = "<i class='fas fa-home'></i> Home" ... [Languages.pir] ... landingPageName = "<i class='fas fa-home'></i> Arrr! Homme" ...
If those params are not configured for a specific language, they will get their default values:
landingPageName = "<i class='fas fa-home'></i> Home"
The home button is going to look like this:
The Relearn theme has been built to be as configurable as possible by defining multiple partials
themes/hugo-theme-relearn/layouts/partials/, you will find all the partials defined for this theme. If you need to overwrite something, don’t change the code directly. Instead follow this page. You’d create a new partial in the
layouts/partials folder of your local project. This partial will have the priority.
This theme defines the following partials :
header.html: the header of the page. See output-formats
footer.html: the footer of the page. See output-formats
body.html: the body of the page. The body may contain of one or many articles. See output-formats
article.html: the output for a single article, can contain elements around your content. See output-formats
menu.html: left menu. Not meant to be overwritten
search.html: search box. Not meant to be overwritten
custom-header.html: custom headers in page. Meant to be overwritten when adding CSS imports. Don’t forget to include
styleHTML tag directive in your file.
favicon.html: the favicon
heading-pre.html: side-wide configuration to prepend to pages title headings. If you override this, it is your responsibility to take the page’s
headingPresetting into account.
heading-post.html: side-wide configuration to append to pages title headings. If you override this, it is your responsibility to take the page’s
headingPostsetting into account.
logo.html: the logo, on top left hand corner
meta.html: HTML meta tags, if you want to change default behavior
menu-pre.html: side-wide configuration to prepend to menu items. If you override this, it is your responsibility to take the page’s
menuPresetting into account.
menu-post.html: side-wide configuration to append to menu items. If you override this, it is your responsibility to take the page’s
menuPostsetting into account.
menu-footer.html: footer of the the left menu
toc.html: table of contents
content.html: the content page itself. This can be overridden if you want to display page’s meta data above or below the content.
content-footer: footer below the content, has a default implementation but you can overwrite it if you don’t like it.
Create a new file in
logo.html. Then write any HTML you want.
You could use an
img HTML tag and reference an image created under the static folder, or you could paste a SVG definition!
The size of the logo will adapt automatically
If your favicon is a SVG, PNG or ICO, just drop off your image in your local
static/images/ folder and name it
If no favicon file is found, the theme will lookup the alternative filename
logo in the same location and will repeat the search for the list of supported file types.
If you need to change this default behavior, create a new file in
favicon.html. Then write something like this:
<link rel="icon" href="/images/favicon.bmp" type="image/bmp">
The Relearn theme lets you choose between some predefined color variants in light or dark mode, but feel free to add one yourself!
You can preview the shipped variants by changing them in the variant selector at the bottom of the menu.
themeVariant value with the name of your theme file. That’s it!
[params] themeVariant = "relearn-light"
In the above example your theme file has to be named
You can also set multiple variants. In this case, the first variant is the default chosen on first view and a variant switch will be shown in the menu footer.
[params] # Change default color scheme with a variant one. themeVariant = [ "relearn-light", "relearn-dark" ]
If you want to switch the syntax highlighting theme together with your color variant, generate a syntax highlighting stylesheet and configure your installation according to Hugo’s documentation, and
@import this stylesheet in your color variant stylesheet. For an example, take a look into
config.toml of the exampleSite.
If you are not happy with the shipped variants you can either copy and rename one of the shipped files from
static/css, edit them afterwards to your liking in a text editor and configure the
themeVariant parameter in your
config.toml or just use the interactive variant generator.
Certain parts of the theme can be changed for support of your own output formats. Eg. if you define a new output format
PLAINTEXT in your
config.toml, you can add a file
layouts/partials/header.plaintext.html to change the way, the page header should look like for that output format.
This interactive tool may help you to generate your own color variant stylesheet.
To get started, first select a color variant from the variant switch that fits you best as a starting point.
The graph is interactive and reflect the current colors. You can click on any of the colored boxes to adjust the respective color. The graph and the page will update accordingly.
The arrowed lines reflects how colors are inherited thru different parts of the theme if the descendent isn’t overwritten. If you want to delete a color and let it inherit from its parent, just delete the value from the input field.
To better understand this select the
neon variant and modify the different heading colors. There, colors for the heading
h4 are explicitly set.
h5 is not set and inherits its value from
h6 is also not set and inherits its value from
Once you’ve changed a color, the variant switch will show a “My custom variant” entry and your changes are stored in the browser. You can change pages and even close the browser without losing your changes.
Once you are satisfied, you can download the new variants file and copy it into your site’s
static/css directory. Afterwards you have to adjust the
themeVariant parameter in your
config.toml to your chosen file name.
Eg. if your new variants file is named
theme-my-custom-variant.css, you have to set
themeVariant='my-custom-variant' to use it.
This only works in modern browsers.
pageparameter from docs #336
No changelog for this release.
No changelog for this release.
No changelog for this release.