A sleek, modern blog theme for Zola. See the live site demo here.
radion noun
- (physics) A scalar field in higher-dimensional spacetimes


First download this theme to your themes directory:
cd themes
git clone https://github.com/micahkepe/radion
and then enable it in your config.toml:
theme = "radion"
This theme requires your index section (content/_index.md) to be paginated to
work:
paginate_by = 5
The posts should therefore be in directly under the content folder.
The theme requires tags and categories taxonomies to be enabled in your
config.toml:
taxonomies = [
# You can enable/disable RSS
{name = "categories", feed = true},
{name = "tags", feed = true},
]
If you want to paginate taxonomies pages, you will need to overwrite the templates as it only works for non-paginated taxonomies by default.
Set a field in extra with a key of radion_menu:
radion_menu = [
{url = "$BASE_URL", name = "Home"},
{url = "$BASE_URL/categories", name = "Categories"},
{url = "$BASE_URL/tags", name = "Tags"},
{url = "https://google.com", name = "Google"},
]
If you put $BASE_URL in a url, it will automatically be replaced by the actual
site URL.
The site title is shown on the homepage. As it might be different from the
<title> element that the title field in the config represents, you can set
the radion_title instead.
You may define the author(s) of a page in either the root config.toml file, or
on a per-page basis in the page's frontmatter.
The order of precedence for determining the author shown in a page’s footer is:
page.extra.author (highest precedence)page.authorspage.config.author (lowest precedence, default)config.tomlIn config.toml:
[extra]
author = "John Smith"
At the top of a page in its frontmatter (wrap this in +++):
title = "..."
date = 1970-01-01
[extra]
author = "John Smith"
Alternatively, you can define the page.authors variable with a single entry:
title = "..."
date = 1970-01-01
authors = ["John Smith"]
title = "..."
date = 1970-01-01
authors = ["John Smith", "Joe Schmoe", "Jane Doe"]
[!NOTE] Do not define both
extra.authorandauthorsin the same page unless you wantextra.authorto take precedence.
To change the default favicon:
Create your own favicon folder with the following site: RealFaviconGenerator
/icons/favicon/Unzip the created folder
Create a static/icons/ directory if it does not already exist
Place the unzipped favicon/ directory in static/icons/.
By default, favicons are enabled, however, if for some reason you would like to
disable favicons, set the following in your config.toml:
[extra]
favicon = false
To enable a GitHub reference link in the header, set the following in your
config.toml:
[extra]
github = "https://github.com/your-github-link"
[markdown]
# Whether to do syntax highlighting
# Theme can be customized by setting the `highlight_theme` variable to a theme
# supported by Zola
highlight_code = true
# For a complete list of themes, see:
# https://www.getzola.org/documentation/getting-started/configuration/#syntax-highlighting
highlight_theme = "one-dark"
[extra]
codeblock = true
[!NOTE] Ligatures are disabled by default as defined in the _theme.scss file.
To enable LaTeX support with MathJax, set the following in your config.toml:
[extra]
latex = true
To enable a searchbar at the top of the page navigation, set the following in
your config.toml:
build_search_index = true
[search]
index_format = "elasticlunr_json"
[extra]
enable_search = true
To set the color theme of the site, set the following in your config.toml:
[extra]
theme = "toggle" # options: {light, dark, auto, toggle}
There are four options for the theme field:
light: Always light modedark: Always dark modeauto: Automatically switch between light and dark mode based on the user's
system preferencestoggle: Allow the user to toggle between light and dark modeTo enable a table of contents on a page, add the following to the front matter of the page:
[extra]
toc = true
[!NOTE] Giscus comments assumes that you are hosting the blog site via GitHub Pages and thus have access to GitHub Discussions.
First, follow the instructions at giscus.app.
This includes installing the Giscus app and enabling discussions on the
GitHub repository that you host the website code. Additionally, fill in the
repository path in the prompt. Then, from the generated script, fill in the
corresponding values in the config.toml:
[extra]
comments = true # {true, false}; sets global enabling of comments by default
giscus_repo = "FILL ME IN"
giscus_repo_id = "FILL ME IN"
giscus_data_category_id = "FILL ME IN"
# giscus_data_category = "General" # Default to "General"
Comments can be enabled or disabled on a per page basis by editing the page's front matter. For example, to disable comments on a specific post:
[extra]
comments = false
The config.toml value for comments takes precedence and priority. For
example, if you globally disable comments in your config.toml by setting
comments = false, then trying to enabling comments through a page's front
matter will have no effect.
To enable revision history links that allow readers to view the commit history
for individual posts, configure the following in your config.toml:
[extra]
# Enable revision history globally
revision_history = true
# Your blog's GitHub repository URL
blog_github_repo_url = "https://github.com/username/repository-name"
Revision history can be enabled or disabled on a per-page basis by adding the following to a page's front matter:
[extra]
revision_history = true # or false to disable for this page
When enabled, a "(revision history)" link will appear in the page footer that links directly to the GitHub commit history for that specific content file, allowing readers to see how the post has evolved over time.
Open Graph is a standard for embedding rich previews of content on the Internet. It is used by social media platforms like Facebook, Twitter, and LinkedIn to display a preview of a page when a user shares the page on their social media network.
For example, to set the Open Graph image for a post my-post to be the page
asset cover.png, add the following to the front matter of the post:
Make sure the image is located in the page's content directory (i.e.
content/my-post/. For example:
content/
└── my-post/
├── index.md
├── cover.png # Your cover image
└── assets/
└── other-image.jpg
or
content/
└── my-post/
├── index.md
└── assets/
├── other-image.jpg
└── cover.png # Your cover image
Add the following to the front matter of the post:
[extra]
cover_image = "cover.png"
[!NOTE] The image must be located within the page's content directory and
cover_imageexpects just the filename of the image (e.g.,"cover.png", not a path like"assets/cover.png"). The first filename match will be used.
Currently three font CDN sites are supported:
"googlefont"): Fonts from fonts.google.com"fontsource"): Self-hosted fonts from fontsource.org. Uses WOFF2 files."zeoseven"): Fonts from
fonts.zeoseven.com. Requires a font_id for URL construction.To configure, add entries under [extra] in your config.toml:
| Option | Type | Default | Description |
|---|---|---|---|
font_cdn | String | "googlefont" | Font provider: "googlefont", "fontsource", "zeoseven", or "custom" |
font_name | String | "JetBrains Mono" | Font family name (e.g., "Inter", "Roboto") |
font_weights | Array | (See below) | Weights to load (provider-specific format) |
font_display | String | "swap" | CSS font-display value: "swap", "block", "auto", etc. |
font_id | Number | None | ZeoSeven only: Numeric ID from font URL |
font_css_urls | Array | None | Custom only: Array of CSS URLs for font definitions |
| Provider | Format | Example |
|---|---|---|
| Google Fonts | Array of numbers | [400, 700] |
| Fontsource | Array of strings | ["main"] |
| ZeoSeven | Array of numbers | [400, 700] |
# Google Fonts
[extra]
font_cdn = "googlefont"
font_name = "Inter"
font_weights = [300, 400, 500, 700]
font_display = "swap"
# Fontsource
[extra]
font_cdn = "fontsource"
font_name = "JetBrains Mono"
font_weights = ["main"]
# ZeoSeven
[extra]
font_cdn = "zeoseven"
font_name = "Custom Font"
font_id = 443
font_weights = [400, 700]
# Custom CSS
[extra]
font_cdn = "custom"
font_name = "My Custom Font"
font_css_urls = [
"https://example.com/fonts/custom-font.css",
"https://cdn.example.com/typography.css"
]
Lots of inspiration and code snippets taken from these awesome Zola themes:
redux by
SeniorMars.