From e16c1b7437ffdb555907b7aa2c0f50c1789613ef Mon Sep 17 00:00:00 2001 From: Shir Goldberg <3937986+shirgoldbird@users.noreply.github.com> Date: Tue, 28 Jul 2026 14:57:30 -0400 Subject: [PATCH 1/4] Move feature comparison table to the customize overview MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The "Choosing the right feature" table lived on the context parameter guide, where it compared context against customization features. Move it to the customize overview, split custom instructions into its own column, and add translation memories. The context guide now links to the table instead. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- docs/customize/overview.mdx | 14 ++++++++++++++ .../how-to-use-context-parameter.mdx | 16 +++------------- 2 files changed, 17 insertions(+), 13 deletions(-) diff --git a/docs/customize/overview.mdx b/docs/customize/overview.mdx index 9964c7e5..0840bcc5 100644 --- a/docs/customize/overview.mdx +++ b/docs/customize/overview.mdx @@ -23,6 +23,20 @@ Glossaries, style rules, custom instructions, and translation memories work with Glossaries and style rules are unique to each of DeepL's global data centers and are not shared between them. Clients using [regional endpoints](/docs/getting-started/regional-endpoints) can't access glossaries or style rules created in the UI at this time. +## Choosing the right feature + +Each feature solves a different problem, and the [`context` parameter](/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter) overlaps with them: it isn't a stored customization, but it's often the right tool for ambiguous or short text. Use this table to decide which feature fits your use case. + +| Use case | Context parameter | Glossaries | Style rules | Custom instructions | Translation memories | +| :---- | :----: | :----: | :----: | :----: | :----: | +| **Ambiguous words or short snippets** | ✅ | ❌ | ❌ | ❌ | ❌ | +| **Consistent gender or name spelling** | ✅ | ❌ | ❌ | ❌ | ❌ | +| **Consistent domain-specific terminology** | ❌ | ✅ | ❌ | ❌ | ❌ | +| **Brand and product names** | ❌ | ✅ | ❌ | ❌ | ❌ | +| **Formatting conventions (dates, numbers, punctuation)** | ❌ | ❌ | ✅ | ❌ | ❌ | +| **Tone and phrasing** | ❌ | ❌ | ❌ | ✅ | ❌ | +| **Reusing previously approved translations** | ❌ | ❌ | ❌ | ❌ | ✅ | + ## Feature guides diff --git a/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter.mdx b/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter.mdx index bd01cf7e..00a2fe2f 100644 --- a/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter.mdx +++ b/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter.mdx @@ -7,7 +7,7 @@ public: true **This guide shows you:** - When to use `context` (and when not to) - How to use `context` to resolve ambiguous words, genders, or transliterations -- How to choose between `context`, Glossaries, and Style Rules +- Where to find a comparison of `context` with DeepL's customization features --- @@ -225,19 +225,9 @@ curl -X POST 'https://api.deepl.com/v2/translate' \ --- -## Choosing the right feature for your needs +## Choosing the right feature -Different DeepL features solve different problems. Use this table to decide which best suits your use case. - -| Use Case | Context Parameter | Glossaries | Style Rules | -|----------|:----------------:|:----------:|:-----------:| -| **Ambiguous words** | ✅ | ❌ | ❌ | -| **Consistent gender or spelling** | ✅ | ❌ | ❌ | -| **Consistent domain-specific terminology** | ❌ | ✅ | ❌ | -| **Brand names** | ❌ | ✅ | ❌ | -| **Tone and style** | ❌ | ❌ | ✅ | -| **Formatting rules** | ❌ | ❌ | ✅ | -| **Translation instructions** | ❌ | ❌ | ✅ | +The `context` parameter is one of several ways to influence translation output. For a comparison of `context` with glossaries, style rules, custom instructions, and translation memories, see [Choosing the right feature](/docs/customize/overview#choosing-the-right-feature) on the Customize overview. --- From a0b8039cedef5117a9486c3e17b33d745f87dfb1 Mon Sep 17 00:00:00 2001 From: Shir Goldberg <3937986+shirgoldbird@users.noreply.github.com> Date: Tue, 28 Jul 2026 15:01:10 -0400 Subject: [PATCH 2/4] Put the context parameter last in the comparison table Lead with the customization features since this is their overview page, and introduce the context parameter as the non-customization extra rather than framing the section around it. --- docs/customize/overview.mdx | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/customize/overview.mdx b/docs/customize/overview.mdx index 0840bcc5..54ed200a 100644 --- a/docs/customize/overview.mdx +++ b/docs/customize/overview.mdx @@ -25,17 +25,17 @@ Glossaries and style rules are unique to each of DeepL's global data centers and ## Choosing the right feature -Each feature solves a different problem, and the [`context` parameter](/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter) overlaps with them: it isn't a stored customization, but it's often the right tool for ambiguous or short text. Use this table to decide which feature fits your use case. +Use this table to decide which feature fits your use case. It also covers the [`context` parameter](/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter), which isn't a customization feature but is often the right tool for ambiguous or short text. -| Use case | Context parameter | Glossaries | Style rules | Custom instructions | Translation memories | +| Use case | Glossaries | Style rules | Custom instructions | Translation memories | Context parameter | | :---- | :----: | :----: | :----: | :----: | :----: | -| **Ambiguous words or short snippets** | ✅ | ❌ | ❌ | ❌ | ❌ | -| **Consistent gender or name spelling** | ✅ | ❌ | ❌ | ❌ | ❌ | -| **Consistent domain-specific terminology** | ❌ | ✅ | ❌ | ❌ | ❌ | -| **Brand and product names** | ❌ | ✅ | ❌ | ❌ | ❌ | -| **Formatting conventions (dates, numbers, punctuation)** | ❌ | ❌ | ✅ | ❌ | ❌ | -| **Tone and phrasing** | ❌ | ❌ | ❌ | ✅ | ❌ | -| **Reusing previously approved translations** | ❌ | ❌ | ❌ | ❌ | ✅ | +| **Consistent domain-specific terminology** | ✅ | ❌ | ❌ | ❌ | ❌ | +| **Brand and product names** | ✅ | ❌ | ❌ | ❌ | ❌ | +| **Formatting conventions (dates, numbers, punctuation)** | ❌ | ✅ | ❌ | ❌ | ❌ | +| **Tone and phrasing** | ❌ | ❌ | ✅ | ❌ | ❌ | +| **Reusing previously approved translations** | ❌ | ❌ | ❌ | ✅ | ❌ | +| **Ambiguous words or short snippets** | ❌ | ❌ | ❌ | ❌ | ✅ | +| **Consistent gender or name spelling** | ❌ | ❌ | ❌ | ❌ | ✅ | ## Feature guides From e0e1b0e11f6a10814618102b669a13d58c80662c Mon Sep 17 00:00:00 2001 From: Shir Goldberg <3937986+shirgoldbird@users.noreply.github.com> Date: Tue, 28 Jul 2026 15:03:49 -0400 Subject: [PATCH 3/4] Reword the comparison table intro --- docs/customize/overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/customize/overview.mdx b/docs/customize/overview.mdx index 54ed200a..b1184a2c 100644 --- a/docs/customize/overview.mdx +++ b/docs/customize/overview.mdx @@ -25,7 +25,7 @@ Glossaries and style rules are unique to each of DeepL's global data centers and ## Choosing the right feature -Use this table to decide which feature fits your use case. It also covers the [`context` parameter](/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter), which isn't a customization feature but is often the right tool for ambiguous or short text. +Here's when to use each customization feature for the best results. The [`context` parameter](/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter) can also be used to improve translations of ambiguous or short text. | Use case | Glossaries | Style rules | Custom instructions | Translation memories | Context parameter | | :---- | :----: | :----: | :----: | :----: | :----: | From 1765d9dc0414b68be461b43a898e37cc462fc243 Mon Sep 17 00:00:00 2001 From: Shir Goldberg <3937986+shirgoldbird@users.noreply.github.com> Date: Tue, 28 Jul 2026 15:04:22 -0400 Subject: [PATCH 4/4] Drop redundant link location from the context guide --- .../examples-and-guides/how-to-use-context-parameter.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter.mdx b/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter.mdx index 00a2fe2f..297b9aaf 100644 --- a/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter.mdx +++ b/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter.mdx @@ -227,7 +227,7 @@ curl -X POST 'https://api.deepl.com/v2/translate' \ ## Choosing the right feature -The `context` parameter is one of several ways to influence translation output. For a comparison of `context` with glossaries, style rules, custom instructions, and translation memories, see [Choosing the right feature](/docs/customize/overview#choosing-the-right-feature) on the Customize overview. +The `context` parameter is one of several ways to influence translation output. For a comparison of `context` with glossaries, style rules, custom instructions, and translation memories, see [Choosing the right feature](/docs/customize/overview#choosing-the-right-feature). ---