Language folder in pattern
warning A warning says what Statac did instead, and the build goes on.
An address pattern for a language’s pages opens with that language’s
folder. On a site in several languages, a permalink: on a page in
content/en/, and tags.permalink and series.permalink for the English
tags and series, are read from /en/, the folder’s own address: the
pattern /{year}/{slug}/ lands an English post at /en/2026/post-1/.
Written as /en/{year}/{slug}/, the folder would be in the address twice.
What you’ll see
warning Language folder in pattern: `/en/{year}/{slug}/` is read from `/en/` already
Write it as `/{year}/{slug}/`.
More: https://statac.dev/e/language-folder-in-pattern/
In the terminal the message also names the file and line where there is one, and marks the exact text.
Why Statac warns
Statac is sure what was meant: an address with the folder in it once. It
reads the pattern without the folder, so the post lands at
/en/2026/post-1/, and says so, because the same pattern is read from
/ on the main language’s pages at the top of content/.
How to fix it
Write the pattern without the language’s folder. A pattern for every
language, written once in statac.yaml, then lands each language’s pages
beneath its own folder.
Example
In content/en/index.md:
pages.permalink: /en/{year}/{slug}/
Without the folder, English posts still land at /en/2026/post-1/:
pages.permalink: /{year}/{slug}/
Its name
| Name | language-folder-in-pattern |
|---|---|
| In the terminal | statac explain language-folder-in-pattern |
| To stop showing it | quiet: [language-folder-in-pattern] in statac.yaml, once you have understood it. Statac still counts it. |
Something unclear or wrong? Open an issue on GitHub.