Home /Integrations /Multilingual SvelteKit /Translating a SvelteKit Blog

Translating a SvelteKit Blog

Multilingual SvelteKit6 articles

A complete implementation guide for adding Portuguese and Spanish to a SvelteKit markdown blog - architecture decisions, route design, content index changes, on-demand translation, and KV caching.

Start here 1 essential article
Essential
26 min concept

Why Standard i18n Approaches Fail for Technical Blogs

Most i18n strategies duplicate or mistranslate. Learn the overlay model: prose-only translation for Markdown blogs at any scale.

Read article →
All articles 5 in this topic
  1. 02
    The i18n Foundation: Config, Types, and Route Architecture Build a multilingual SvelteKit blog foundation: locale config, TypeScript types, locale detection, route matcher, and the (locale)/[lang=locale] route group.
    28 min tutorial
  2. 03
    Making the Content Index Locale-Aware Extend the SvelteKit content index with getContent(locale) - marks articles as isFallback when no translation exists, plus +page.svelte for translated routes.
    26 min tutorial
  3. 04
    On-Demand Article Translation with the Claude API Translate SvelteKit markdown articles on first request using the Claude API: API key setup, prose extraction, and server-side rendering.
    34 min tutorial
  4. 05
    Caching Translations with Upstash Redis Cache SvelteKit translations in Upstash Redis: pre-rendered HTML, permanent TTL for complete, 2-hour retry for incomplete, and instant streaming.
    40 min tutorial
  5. 06
    Dev Tooling, CLI Scripts, and Batch API Catalog Translation Preview translations locally, pre-translate pillar articles with a CLI script, run a Batch API catalog translation, and invalidate stale Redis entries.
    36 min tutorial

The Hackpile © 2026