Duckquill

Duckquill is an opinionated, modern, pretty, and clean Zola theme that has the purpose of greatly simplifying the process of rolling up your blog. It aims to provide all the necessary options for comfortable writing, while keeping the balance of simplicity.

With it, you can change some configuration variables, tweak some of the included graphics, and have a nice blog up in minutes!

Some of the features Duckquill has to offer:

Nota

Although Duckquill is made based on the needs of my website, I am very open to feature requests as long as they are somewhat useful to others, so if you need a feature/configuration that does not exist, feel free to open an issue, or better yet, a pull request!

Tip

If you use Duckquill and enjoy it, or just like my work, please consider buying me a coffee, it would mean the world to me ^^.

Installation

First, if you already have Git setup, add this theme as a submodule:

git submodule init
git submodule add https://codeberg.org/daudix/duckquill.git themes/duckquill

Otherwise, simply clone it to your themes directory:

git clone https://codeberg.org/daudix/duckquill.git themes/duckquill

Penting

It is highly recommended to switch from the main branch to the latest release:

cd themes/duckquill
git checkout tags/v5.4.0

Then, enable it in your config.toml:

theme = "duckquill"

To update the theme, simply switch to a new tag:

git submodule update --remote --merge
cd themes/duckquill
git checkout tags/v5.4.0

Penting

Check the changelog for all versions after the one you are using; there may be breaking changes that require manual involvement.

Options

Duckquill offers some configuration options to make it fit you better; most options have pretty descriptive comments, so it should be easy to understand what they do.

Front Matter

Duckquill has some front matter variables that you can use by setting them in the [extra] section:

Global

Configuration variables from config.toml that can be set/overriden per page/section:

Other variables:

Blog post specific:

In [extra.comments] section:

Localization

Duckquill ships with a localization system based on one used in tabi, it’s very easy to use and quite flexible at the same time.

To add a translation, simply create a file in your site’s i18n directory called LANG_CODE.toml, e.g fr.toml. The language code should be either ISO 639-1 or BCP 47.

Inside that file, copy-paste one of the existing translations from Duckquill and adapt it to your needs. You can also check tabi translation files for reference.

Additionally to translating Duckquill, you can also override the English stings by copy-pasting en.toml from Duckquill to the i18n directory of your website and adjusting the values to your liking.

Custom Styles

To add your own or override existing styles, create a custom style and add it in the config.toml:

[extra]
styles = [
  "YOUR_STYLE.css",
  "ALSO_YOUR_STYLE.css"
]

Additional styles are expected it to be in the static directory. If you are using Sass they will be compiled there by default.

If for some reason overridden style is not respected, try using !important (don’t use it unless needed). You can import styles from Duckquill using:

@use "../themes/duckquill/sass/NEEDED_FILE.scss";

You can also load styles per page/section by setting them inside page’s front matter:

[extra]
styles = [
  "YOUR_PAGE_STYLE.css"
]

Accent Color

Duckquill respects chosen accent color everywhere. To use your own, simply change it in config.toml:

[extra]
accent_color = "#3584e4"

Additionally, you can set a separate color for dark mode:

[extra]
accent_color_dark = "#ff7800"

Favicon

Files named favicon.png and apple-touch-icon.png are used as favicon and Apple Touch Icon respectively. For animated favicon you can use APNG with the png file extension.

In the Wild

This list is starting to get long, so click on it to expand it.

In Credits

Assets Sources

All sources for Duckquill’s assets are available here and licensed under CC BY-SA 4.0. The reason for not putting the sources in the same repo as Duckquill itself is simple: I want it to be as small as possible, so that repo cloning is fast and doesn’t make the site significantly heavier; this is also why the demo uses remote images instead of local copies.

Credits

Tools Used

As for the code formatter I use built-in VSCodium one. Prettier is good but I don’t like how it tries to make code fit in a very narrow column, this can be changed of course, but built-in formatter does it’s job so I don’t bother doing so.

Thanks To