Customization

Configuration

If set, jump over to the config.toml file and start configuring your site.

This section will mainly cover settings that are unique to this theme. If something is not covered here (or elsewhere in this file), there's a good chance it is covered in this Hugo docs page.

Global Parameters

These options set global values that some pages or all pages in the site use by default.

ParameterValue TypeOveridable on Page
authorstringno
twitterstringno
largeTwitterCardbooleanno
ga_analyticsstringno
descriptionstringyes
introDescriptionstringno
numberOfTagsShownintegerno
fallBackOgImagefile path (string)no
codeMaxLinesintegeryes
codeLineNumbersbooleanyes
mainSectionsarray/stringno
centerLogobooleanno
logofile path (string)no
mobileNavigationstringno
figurePositionShowbooleanyes
figurePositionLabelstringno
customCSSarray of file path (string)no
customJSarray of file path (string)no
enforceLightModebooleanN/A
enforceDarkModebooleanN/A
titleSeparatorstringno
commentbooleanno

Page Parameters

These options can be set from a page frontmatter or via archetypes.

ParameterValue TypeOverrides Global
titlestringN/A
datedateN/A
descriptionstringN/A
draftbooleanN/A
featuredbooleanN/A
tagsarray/stringN/A
categoriesarray/stringN/A
tocbooleanN/A
thumbnailfile path (string)N/A
featureImagefile path (string)N/A
shareImagefile path (string)N/A
codeMaxLinesintegeryes
codeLineNumbersbooleanyes
figurePositionShowbooleanyes
figurePositionLabelstringno
commentbooleanno

To add, remove, or reorganize top menu items, edit this YAML file. These menu items also display any categories (taxonomies) that might be configured for articles.

Social media

To edit your social media profile links, edit this YAML file.

If you wish to globally use a large Twitter summary card when sharing posts, set the global parameter largeTwitterCard to true.

Search engine

If using Google Analytics, configure the ga_analytics global parameter in your site with your ID.

Forcing light or dark mode

By default, sites authored using Clarity will load in the browser with the user's system-wide settings. I.e., if the underlying OS is set to dark mode, the site will automatically load in dark mode. Regardless of the default mode, a UI control switch exists to override the theme mode at the user's discretion.

In order to override this behavior and force one mode or another, add either enforceLightMode or enforceDarkMode to your config.toml file. If neither value is present, add it.

To enforce Light Mode by default, turn enforceLightMode to true.

To enforce Dark Mode by default, turn enforceDarkMode to true

1[params]
2...
3enforceLightMode = true # Force the site to always load in light mode.
4...

Please note that you cannot enforce both modes at the same time. It wouldn't make sense, would it?

Please also note that the mode toggle UI will remain in place. That way, if a user prefers dark mode, they can have their way. The best of both worlds.

I18N

This theme supports Multilingual (i18n / internationalization / translations)

The exampleSite gives you some examples already. You may extend the multilingual functionality by following the official documentation.

Things to consider in multilingual:

  • supported languages are configured in config/_default/languages.toml
  • add new language support by creating a new file inside i18n directory. Check for missing translations using hugo server --i18n-warnings
  • taxonomy names (tags, categories, etc...) are translated in i18n as well (translate the key)
  • menus are translated manually in the config files config/_default/menus/menu.xx.toml
  • menu's languages list are semi-hardcoded. You may chose another text for the menu entry with languageMenuName. Please, do better and create a PR for that.
  • content must be translated individually. Read the official documentation for information on how to do it.

note: if you do NOT want any translations (thus removing the translations menu entry), then you must not have any translations. In the exampleSite that's as easy as removing the extra translations from the config/_default/... or executing this onliner:

sed '/^\[pt]$/,$d' -i config/_default/languages.toml   &&   rm config/_default/menus/menu.pt.toml

Comments

Clarity supports Hugo built-in Disqus partial, you can enable Disqus simply by setting disqusShortname in your configuration file.

disqusShortname should be placed in root level of configuration.

You can also create a file named layouts/partials/comments.html for customizing the comments, checkout Comments Alternatives for details.