The Spiker Stack Manual contains multiple untranslated sections when the website language is set to Spanish. Large portions of the documentation, chapter titles, headings, and body content remain in English, resulting in a mixed-language experience.
Issue Description
When accessing the manual through the Spanish version of the website (/es/manual), the user is presented with a partially translated interface. While navigation elements such as Descargar, Comprar, Manual, and Capítulos are correctly localized, the documentation content itself largely remains in English.
This results in a mixed-language manual where users selecting Spanish still receive English documentation.
Environment
Property
Value
Application
Spiker Stack Website
Module
Manual
Environment
Production
Browser
Firefox
Operating System
Windows 11
Device
Desktop
Language
Spanish
Preconditions
Website language is set to Spanish.
User navigates to the Manual section.
Steps to Reproduce
Open spikerstack.com/es/manual.
Ensure Spanish is selected in the language selector.
Observe the chapter list and documentation content.
Review chapter titles, headings, and body text.
Expected Result
All manual content should be translated into Spanish, including:
Chapter names.
Page titles.
Headings.
Body paragraphs.
Navigation breadcrumbs.
Reference documentation.
Actual Result
Multiple documentation elements remain in English.
Examples visible in the screenshot:
Chapter Navigation
Welcome
Capture
Images
Align
Crop
Stack
Touch up
Finish
The adjustment matrix
Settings
Reference
Page Content
Welcome
How a focus stack works
Body Text
Entire documentation paragraphs remain in English.
Evidence
The attached screenshot shows:
URL path: /es/manual
Spanish navigation interface.
English documentation content.
English chapter navigation.
English headings and explanatory text.
This confirms that localization is either incomplete or not being applied to manual content.
Impact
Reduces accessibility for Spanish-speaking users.
Creates an inconsistent multilingual experience.
Makes the documentation difficult to consume for users expecting localized content.
Gives the appearance of incomplete localization.
Frequency
Always
Reproducibility
100%
Severity
Medium
Notes
This issue appears to affect both:
Navigation chapters.
Documentation article content.
A localization review should be performed for the entire documentation system, as other chapters may be affected in the same way.
Suggested Fix
Add Spanish translations for all manual chapters.
Localize article titles and headings.
Translate all body content and reference documentation.
Ensure documentation content follows the selected language rather than falling back to English.
Implement localization validation to detect untranslated documentation pages before deployment.
## Summary
The **Spiker Stack Manual** contains multiple untranslated sections when the website language is set to **Spanish**. Large portions of the documentation, chapter titles, headings, and body content remain in English, resulting in a mixed-language experience.
## Issue Description
When accessing the manual through the Spanish version of the website (`/es/manual`), the user is presented with a partially translated interface. While navigation elements such as **Descargar**, **Comprar**, **Manual**, and **Capítulos** are correctly localized, the documentation content itself largely remains in English.
This results in a mixed-language manual where users selecting Spanish still receive English documentation.
## Environment
| Property | Value |
|-----------|--------|
| Application | Spiker Stack Website |
| Module | Manual |
| Environment | Production |
| Browser | Firefox |
| Operating System | Windows 11 |
| Device | Desktop |
| Language | Spanish |
## Preconditions
- Website language is set to **Spanish**.
- User navigates to the **Manual** section.
## Steps to Reproduce
1. Open **spikerstack.com/es/manual**.
2. Ensure Spanish is selected in the language selector.
3. Observe the chapter list and documentation content.
4. Review chapter titles, headings, and body text.
## Expected Result
All manual content should be translated into Spanish, including:
- Chapter names.
- Page titles.
- Headings.
- Body paragraphs.
- Navigation breadcrumbs.
- Reference documentation.
## Actual Result
Multiple documentation elements remain in English.
Examples visible in the screenshot:
### Chapter Navigation
- Welcome
- Capture
- Images
- Align
- Crop
- Stack
- Touch up
- Finish
- The adjustment matrix
- Settings
- Reference
### Page Content
- Welcome
- How a focus stack works
### Body Text
Entire documentation paragraphs remain in English.
## Evidence
The attached screenshot shows:
- URL path: `/es/manual`
- Spanish navigation interface.
- English documentation content.
- English chapter navigation.
- English headings and explanatory text.
This confirms that localization is either incomplete or not being applied to manual content.
## Impact
- Reduces accessibility for Spanish-speaking users.
- Creates an inconsistent multilingual experience.
- Makes the documentation difficult to consume for users expecting localized content.
- Gives the appearance of incomplete localization.
## Frequency
Always
## Reproducibility
100%
## Severity
Medium
## Notes
This issue appears to affect both:
- Navigation chapters.
- Documentation article content.
A localization review should be performed for the entire documentation system, as other chapters may be affected in the same way.
## Suggested Fix
- Add Spanish translations for all manual chapters.
- Localize article titles and headings.
- Translate all body content and reference documentation.
- Ensure documentation content follows the selected language rather than falling back to English.
- Implement localization validation to detect untranslated documentation pages before deployment.
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
The Spiker Stack Manual contains multiple untranslated sections when the website language is set to Spanish. Large portions of the documentation, chapter titles, headings, and body content remain in English, resulting in a mixed-language experience.
Issue Description
When accessing the manual through the Spanish version of the website (
/es/manual), the user is presented with a partially translated interface. While navigation elements such as Descargar, Comprar, Manual, and Capítulos are correctly localized, the documentation content itself largely remains in English.This results in a mixed-language manual where users selecting Spanish still receive English documentation.
Environment
Preconditions
Steps to Reproduce
Expected Result
All manual content should be translated into Spanish, including:
Actual Result
Multiple documentation elements remain in English.
Examples visible in the screenshot:
Chapter Navigation
Page Content
Body Text
Entire documentation paragraphs remain in English.
Evidence
The attached screenshot shows:
/es/manualThis confirms that localization is either incomplete or not being applied to manual content.
Impact
Frequency
Always
Reproducibility
100%
Severity
Medium
Notes
This issue appears to affect both:
A localization review should be performed for the entire documentation system, as other chapters may be affected in the same way.
Suggested Fix
# [Bug] Missing Spanish Translations in Spiker Stack Manualto # [Bug] [Medium] Missing Spanish Translations in Spiker Stack Manualreported this again already but with much more efficency, so this one is getting close