Could you add instructions to the documentation on how to change colors?
For example, I'm trying to change the default link color and can't seem to get it to work.
I also tried a change like this one for changing the colors of publication list headlines, but the teal variant CSS classes never make it into the CSS even if I run npx tailwindcss -i styles/styles.css -o static/styles/styles.css ...

will you create a 404 page ? (docs => https://www.getzola.org/documentation/templates/404/)
I can't really do it myself, I have absolutly no idea how tailwind works.

I can try but I can't guarantee a good result

I'm new to Zola, using 0.17.2, which is what you get with the current installation instructions.

After failing for a while to get bibtex working in my attempt at my own site (though other aspects of the theme work very nicely so far), I tried to just confirm if I could get kodama-theme to work correctly by itself. Bibtex files are not read correctly.

Steps to reproduce:

• Clone this repository somewhere new
• Install zola; the latest instructions get version 0.17.2 on a Mac
• Enter the kodama-theme directory for this fresh checkout
• zola serve and go to the local url
• Navigate to the page for "paper1" by clicking its title in the list of recent publications

Expected results:

• I expect to see a page like https://adfaure.github.io/kodama-theme/publications/paper1/, which at present has the abstract and other details extracted from the bib file in the repository, and includes the bibtex itself on the page.

Observed results:

• The site builds and is served, but instead of expected behavior, I see the attached screenshot:

I'm on a mac, with a fresh install of zola 0.17.2. Poking around the GH actions, I see the demo site appears to be built using nix, and the logs suggest the last build of the demo used 0.15.3 (https://github.com/adfaure/kodama-theme/actions/runs/4924207168/jobs/8796965946#step:4:219).

When trying to use this theme I cannot get it to function properly. The following are the steps I took and the results.

$ zola init mysite
Welcome to Zola!
Please answer a few questions to get started quickly.
Any choices made can be changed by modifying the `config.toml` file later.
> What is the URL of your site? (https://example.com): 
> Do you want to enable Sass compilation? [Y/n]: 
> Do you want to enable syntax highlighting? [y/N]: 
> Do you want to build a search index of the content? [y/N]: 

Done! Your site was created in /home/user/website/mysite

Get started by moving into the directory and using the built-in server: `zola serve`
Visit https://www.getzola.org for the full documentation.

$ cd mysite
$ mkdir themes
mkdir: cannot create directory ‘themes’: File exists

$ cd themes & git clone https://github.com/adfaure/kodama-theme
[1] 3861984
Cloning into 'kodama-theme'...
remote: Enumerating objects: 857, done.
remote: Counting objects: 100% (16/16), done.
remote: Compressing objects: 100% (16/16), done.
remote: Total 857 (delta 2), reused 7 (delta 0), pack-reused 841
Receiving objects: 100% (857/857), 13.16 MiB | 2.96 MiB/s, done.
Resolving deltas: 100% (474/474), done.
[1]+  Done                    
$ cd themes

updated config.toml as described in readme.

$ zola serve
Building site...
Checking all internal links with anchors.
> Successfully checked 0 internal link(s) with anchors.
-> Creating 0 pages (0 orphan) and 0 sections
Error: Failed to serve the site
Error: Failed to render section '/home/dad/website/mysite/content/_index.md'
Error: Reason: Failed to render 'index.html' (error happened in 'base.html').
Error: Reason: Function call 'resize_image' failed
Error: Reason: `resize_image`: Cannot find file: static/img/avatar.jpg

I have attached config.toml (as a .txt).

Maybe helpful to add a license

Hello,

I am trying to migrate my page from hugo + academic to zola + kodama.
My page is in two languages. That is why I'm work on adding i18n support (see https://www.getzola.org/documentation/content/multilingual/) to your template.
My fork is here: https://github.com/beling/kodama-theme
Must changes are in nav.html.

Basic support is already working and functional. Please feel free to merge it if you wish.
My fork should not change anything if the page is one language only.

My page, which still uses hugo+academic: http://pbeling.w8.pl/
(however it is partially broken after upgrading hugo and forced upgrading academic; that is why I migrate from academic; it requires too much work after each upgrade and becomes over-complicated)

Best regards and thank you for your great work!
Piotr Beling