Permalinks

Permalink settings control how content URLs are built — the post URL prefix, where the domain root points, and (per language) any prefix overrides. Everything here lives under Settings → Permalinks and always triggers a rebuild on save, so what you set is what ships.

The post URL prefix

Posts live under a URL prefix — blog by default — so a post reads /en/blog/my-post/. The prefix field:

• Accepts lowercase letters, digits, and hyphens. Anything else is stripped on save.
• Falls back to blog if the field ends up empty.
• Can be overridden per language — each configured language gets its own prefix field, and clearing an override falls that language back to the site default (useful for localized blog paths, e.g. noticias under es).

Changing the prefix (old URLs follow)

When you change the prefix, the next build writes automatic redirects from every old post URL to its new address — the old prefix is remembered at save time and used for exactly one transition, then cleared. Old URLs 301 for visitors and search engines alike, so changing your mind about blog vs articles doesn’t strand anything.

Historical caveat that pairs with this: the setup flow writes the first value; a fresh database without a prefix set behaves as blog everywhere by default until you set it.

The home redirect

The home redirect setting decides what serves a language’s root URL (/en/, or / for a monolingual site) when no page already occupies it:

• blog (the default) — the root redirects to the blog listing (skipped entirely if the post prefix is empty, since the root IS the blog in that configuration).
• A page slug — your named page owns the root directly: its built homepage renders at / (and no separate redirect file is generated, because the page is the home page).
• Empty — no root redirect is generated.

If you point it at a slug that no published page matches, the build warns you by name and simply doesn’t emit the redirect — nothing breaks, but the root serves nothing until corrected.

Because domain-root targets must also redirect to per-language roots, the builder writes a small meta-refresh page at each language root pointing at the chosen destination (blog index or the chosen page), with a click-through link — the shape works on any static host. Category, author archives, sitemaps, RSS, and canonical URLs all honor the same prefix/slug rules, so tags, SEO values, and feeds stay consistent with what’s actually published.

Rebuild expectations

Websites reflect these changes only after a build. The Permalinks tab always dispatches one on save, and the build log reports the root-redirect lines (/ → /en/blog/) once generated. Re-publishing content without touching prefix settings never disturbs URLs — those are decided by the settings you set here, not by editing content.