---
title: v0.11.0
description: "Fix AVIF image processing errors and add i18n support for shortcode callout labels."
date: 2026-03-18
tags:
- fix
---

## AVIF Image Processing Fix

seite no longer attempts to decode `.avif` files in the image processing pipeline. The `image` crate's `avif` feature only enables AVIF *encoding* (generating AVIF variants from PNG/JPG/WebP sources), not *decoding*. Previously, `.avif` files in `static/` would trigger a `The image format Avif is not supported` warning on every build.

AVIF files are still copied to `dist/` and served correctly — they just skip the resize/optimize step. Since AVIF is already heavily compressed, re-processing provides no benefit.

## Translatable Callout Shortcode Labels

The built-in `callout` shortcode now supports i18n. Previously, callout titles (`Info`, `Tip`, `Warning`, `Danger`) were hardcoded in English regardless of the site language.

Shortcode templates now receive the `{{ t }}` translation object, matching the convention used by page templates. Callout labels use these new UI string keys:

- `callout_info` (default: "Info")
- `callout_tip` (default: "Tip")
- `callout_warning` (default: "Warning")
- `callout_danger` (default: "Danger")

Override them in `data/i18n/{lang}.yaml`:

```yaml
# data/i18n/de.yaml
callout_info: "Hinweis"
callout_tip: "Tipp"
callout_warning: "Warnung"
callout_danger: "Gefahr"
```

You can also pass a `title` argument to any callout for a one-off override:

```markdown
{{% callout(type="tip", title="Pro-Tipp") %}}
Custom title regardless of language.
{{% end %}}
```

User-defined shortcode templates can now use `{{ t.any_key }}` to access translated UI strings.
