diff --git a/.gitignore b/.gitignore
index 2d37a3f..e5dc477 100644
--- a/.gitignore
+++ b/.gitignore
@@ -7,6 +7,7 @@
 # Generated files
 .docusaurus
 .cache-loader
+.claude
 
 # Misc
 .DS_Store
diff --git a/docs/introduction.md b/docs/introduction.md
index dd9a20c..3d8f455 100644
--- a/docs/introduction.md
+++ b/docs/introduction.md
@@ -24,6 +24,12 @@ This is a completely open API. **No authentication is required to query and get
 
 There is a limit of 10,000 requests per second per IP. This is subject to change if something more practical needs to be enforced.
 
+## Multilingual Support
+
+API responses are available in multiple languages. Append `?lang={code}` to any resource request to receive translated content (e.g. `?lang=de` for German). English is always the default and fallback — untranslated fields are returned in English automatically.
+
+See the [Multilingual Support](./reference/multilingual) reference for the full list of supported languages, response behavior, and how to contribute a translation.
+
 ## GraphQL
 
 This API also supports [GraphQL](https://graphql.org/). The GraphQL endpoint is:
diff --git a/docs/reference/multilingual.md b/docs/reference/multilingual.md
new file mode 100644
index 0000000..d668ed1
--- /dev/null
+++ b/docs/reference/multilingual.md
@@ -0,0 +1,130 @@
+---
+sidebar_position: 1
+---
+
+# Multilingual Support
+
+The D&D 5e SRD API supports multilingual responses, allowing you to request translated content in supported languages. English is always the default and fallback — if a translation is incomplete or unavailable, fields fall back to English individually, so responses are always complete documents.
+
+## Requesting a Language
+
+### Query Parameter (recommended)
+
+Append `?lang={code}` to any resource request. This is the recommended approach because it is explicit and cache-friendly.
+
+```
+GET /api/2014/spells/acid-arrow?lang=de
+```
+
+### Accept-Language Header
+
+The `Accept-Language` request header is also supported per [RFC 5646](https://www.rfc-editor.org/rfc/rfc5646). If both a `lang` query parameter and an `Accept-Language` header are present, the query parameter takes precedence.
+
+```
+Accept-Language: de
+```
+
+Language codes follow the [BCP 47](https://www.rfc-editor.org/rfc/rfc5646) standard (e.g. `de`, `fr`, `pt-BR`).
+
+## Response Behavior
+
+- Translated fields are merged over the base English document on a **per-field basis**.
+- Untranslated fields always retain their English value — responses are never partial.
+- The `Content-Language` response header reflects the requested language when at least one field was translated, or `en` when no translation exists for that document.
+
+## Translatable Fields
+
+Only human-readable text fields are translated. Structural fields (indexes, URLs, numeric values, cross-references) always come from the English base document.
+
+| Field | Translatable |
+|---|---|
+| `name` | Yes |
+| `desc` | Yes |
+| `higher_level` | Yes |
+| `equipment_category.name` | Yes |
+| `index` | No |
+| `url` | No |
+| Numeric values (HP, range, duration, etc.) | No |
+| API reference objects | No |
+
+## Discovering Supported Languages
+
+:::note
+`/api/{year}/languages` lists D&D in-world game languages (Common, Elvish, etc.). `/api/{year}/locales` is the endpoint for API translation support.
+:::
+
+### List all supported locales
+
+```
+GET /api/{year}/locales
+```
+
+Returns all languages that have at least some translated content for the given ruleset year.
+
+```json
+{
+  "count": 2,
+  "results": [
+    { "lang": "de", "url": "/api/2014/locales/de" },
+    { "lang": "fr", "url": "/api/2014/locales/fr" }
+  ]
+}
+```
+
+### Get a specific locale
+
+```
+GET /api/{year}/locales/{lang}
+```
+
+Returns `404` if no translations exist for the requested language.
+
+```json
+{
+  "lang": "de",
+  "url": "/api/2014/locales/de"
+}
+```
+
+## GraphQL
+
+The optional `lang` argument is available on entity queries:
+
+```graphql
+query {
+  spell(index: "acid-arrow", lang: "de") {
+    name
+    desc
+  }
+}
+```
+
+Translation resolution is identical to REST — translated fields are merged before the resolver returns, with English as the per-field fallback.
+
+## Contributing Translations
+
+Translations are entirely community-driven. No database access or special tooling is required.
+
+1. Fork the [5e-database](https://github.com/5e-bits/5e-database) repository
+2. Create or edit a file at `src/{year}/{lang}/5e-SRD-{Collection}.json`
+3. Include only the translatable fields for each entry — non-translatable fields are sourced from the English base automatically
+4. Open a PR — CI validates your translation against the English source
+
+**Example — German spell translation entry:**
+
+```json
+[
+  {
+    "index": "acid-arrow",
+    "name": "Säurepfeil",
+    "desc": [
+      "Ein glitzernder grüner Pfeil schießt auf ein Ziel..."
+    ],
+    "higher_level": [
+      "Wenn du diesen Zauber mit einem Zauberplatz der 3. Stufe oder höher wirkst..."
+    ]
+  }
+]
+```
+
+See [`CONTRIBUTING.md`](https://github.com/5e-bits/5e-database/blob/main/CONTRIBUTING.md) in the database repository for full guidelines.
diff --git a/tsconfig.json b/tsconfig.json
index 8e17a18..a7edf1c 100644
--- a/tsconfig.json
+++ b/tsconfig.json
@@ -2,7 +2,6 @@
   // This file is not used in compilation. It is here just for a nice editor experience.
   "extends": "@docusaurus/tsconfig",
   "compilerOptions": {
-    "baseUrl": ".",
     "esModuleInterop": true
   }
 }