In the C# Playground section, several lessons display incomplete or missing Spanish translations within the instruction panels. While the interface and lesson titles are localized, the instructional text remains partially or entirely in English, creating inconsistency for Spanish-speaking users.
🧪 Steps to Reproduce
Navigate to learn.spikersoft.com/tools/csharp-playground.
Open any lesson (e.g., ¡Hola, Mundo!).
Observe the INSTRUCCIONES section.
Notice that the content is written in English despite the interface being in Spanish.
✅ Expected Behavior
All instructional text should be fully translated into Spanish, maintaining consistency with the localized interface.
Example:
“Console.WriteLine is how C# sends text to the screen — your program’s way of talking to whoever is watching.”
→ “Console.WriteLine es cómo C# envía texto a la pantalla — la forma en que tu programa se comunica con quien lo observa.”
❌ Actual Behavior
Lesson instructions remain in English.
Some technical terms are untranslated or mixed between languages.
The learning flow feels inconsistent for Spanish-speaking users.
📸 Evidence
The attached screenshot shows the lesson ¡Hola, Mundo! with English instructions under the Spanish interface.
🧠 Possible Root Cause
Missing translation keys in the lesson content database.
Static English text not linked to localization files.
Partial implementation of language switching for instructional content.
### 🧩 Summary
In the **C# Playground** section, several lessons display **incomplete or missing Spanish translations** within the instruction panels. While the interface and lesson titles are localized, the instructional text remains partially or entirely in English, creating inconsistency for Spanish-speaking users.
### 🧪 Steps to Reproduce
1. Navigate to `learn.spikersoft.com/tools/csharp-playground`.
2. Open any lesson (e.g., *¡Hola, Mundo!*).
3. Observe the **INSTRUCCIONES** section.
4. Notice that the content is written in English despite the interface being in Spanish.
### ✅ Expected Behavior
All instructional text should be fully translated into Spanish, maintaining consistency with the localized interface.
Example:
- “Console.WriteLine is how C# sends text to the screen — your program’s way of talking to whoever is watching.”
→ **“Console.WriteLine es cómo C# envía texto a la pantalla — la forma en que tu programa se comunica con quien lo observa.”**
### ❌ Actual Behavior
- Lesson instructions remain in English.
- Some technical terms are untranslated or mixed between languages.
- The learning flow feels inconsistent for Spanish-speaking users.
### 📸 Evidence
The attached screenshot shows the lesson **¡Hola, Mundo!** with English instructions under the Spanish interface.
### 🧠 Possible Root Cause
- Missing translation keys in the lesson content database.
- Static English text not linked to localization files.
- Partial implementation of language switching for instructional content.
Triage: root cause confirmed while fixing #215 (C# Hello World). The Spanish curriculum files (SpikerSoft.Business/Domain/Lessons/Translations/es/*.json) only contain title + description for every lesson — zero lessons in any track have translated instructions or hints, which is exactly why the INSTRUCCIONES panel stays English under a Spanish UI. This same gap underlies the whole #196–#203 cluster.
spikerj/spikersoft-backend#7 unblocks this: the locale overlay now supports {seedKey} tokens so even randomized lessons can be translated, and lesson 100 ships as the first fully-translated lesson establishing the pattern. The remaining work for this issue is filling in Spanish instructions/hints for the rest of the C# track in es/csharp.json — pure content authoring, no further code changes needed.
Triage: root cause confirmed while fixing #215 (C# Hello World). The Spanish curriculum files (`SpikerSoft.Business/Domain/Lessons/Translations/es/*.json`) only contain `title` + `description` for every lesson — zero lessons in any track have translated `instructions` or `hints`, which is exactly why the INSTRUCCIONES panel stays English under a Spanish UI. This same gap underlies the whole #196–#203 cluster.
spikerj/spikersoft-backend#7 unblocks this: the locale overlay now supports `{seedKey}` tokens so even randomized lessons can be translated, and lesson 100 ships as the first fully-translated lesson establishing the pattern. The remaining work for this issue is filling in Spanish `instructions`/`hints` for the rest of the C# track in `es/csharp.json` — pure content authoring, no further code changes needed.
Re-verified against current master. Lesson 100 (¡Hola, Mundo!) now has full Spanish instructions/hints in es/csharp.json, matching the example translation given in this report verbatim ("Console.WriteLine es la forma en que C# envía texto a la pantalla...").
Resolved by spikersoft-backend PR #25 (merged to master, part of the #279 → #296 localization effort). Closing.
Re-verified against current `master`. Lesson 100 (`¡Hola, Mundo!`) now has full Spanish `instructions`/`hints` in `es/csharp.json`, matching the example translation given in this report verbatim ("`Console.WriteLine` es la forma en que C# envía texto a la pantalla...").
Resolved by spikersoft-backend PR #25 (merged to `master`, part of the #279 → #296 localization effort). Closing.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
🧩 Summary
In the C# Playground section, several lessons display incomplete or missing Spanish translations within the instruction panels. While the interface and lesson titles are localized, the instructional text remains partially or entirely in English, creating inconsistency for Spanish-speaking users.
🧪 Steps to Reproduce
learn.spikersoft.com/tools/csharp-playground.✅ Expected Behavior
All instructional text should be fully translated into Spanish, maintaining consistency with the localized interface.
Example:
→ “Console.WriteLine es cómo C# envía texto a la pantalla — la forma en que tu programa se comunica con quien lo observa.”
❌ Actual Behavior
📸 Evidence
The attached screenshot shows the lesson ¡Hola, Mundo! with English instructions under the Spanish interface.
🧠 Possible Root Cause
Triage: root cause confirmed while fixing #215 (C# Hello World). The Spanish curriculum files (
SpikerSoft.Business/Domain/Lessons/Translations/es/*.json) only containtitle+descriptionfor every lesson — zero lessons in any track have translatedinstructionsorhints, which is exactly why the INSTRUCCIONES panel stays English under a Spanish UI. This same gap underlies the whole #196–#203 cluster.spikerj/spikersoft-backend#7 unblocks this: the locale overlay now supports
{seedKey}tokens so even randomized lessons can be translated, and lesson 100 ships as the first fully-translated lesson establishing the pattern. The remaining work for this issue is filling in Spanishinstructions/hintsfor the rest of the C# track ines/csharp.json— pure content authoring, no further code changes needed.Re-verified against current
master. Lesson 100 (¡Hola, Mundo!) now has full Spanishinstructions/hintsines/csharp.json, matching the example translation given in this report verbatim ("Console.WriteLinees la forma en que C# envía texto a la pantalla...").Resolved by spikersoft-backend PR #25 (merged to
master, part of the #279 → #296 localization effort). Closing.