Summary
Several translated documentation files under docs/i18n contain incorrect relative links to internal project docs. This causes dead links for non-English users trying to access setup, architecture, contributing, security, and license pages.
Problem
Internal links in translated files are using paths that do not resolve from the docs/i18n directory depth.
Confirmed examples in Spanish translation:
[es.md:252]
[es.md:286]
[es.md:291]
Impact
Non-English users hit dead links during onboarding.
Core trust/safety pages (security, license) are not reachable from translated docs.
Documentation quality appears inconsistent across languages.
Expected behavior
All internal markdown links in docs/i18n/*.md should resolve correctly based on the docs/i18n folder location.
Scope
Fix broken internal links in translated docs (starting with Spanish and then all other i18n files).
Keep external links unchanged.
Ensure consistency of internal link style across translations.
Acceptance criteria
All internal links in docs/i18n/*.md point to existing files.
Verified paths for:
Getting Started
Configuration
Architecture
Contributing
Security
License
Spot-check complete for:
zh-CN
es
hi
pt
ja
ru
ko
Suggested implementation
Use correct relative paths from docs/i18n (typically Terddy.LAPTOP-CVSRCLGL for root-level docs and ../ for sibling docs under docs).
Definition of done
PR updates broken links in translation files.
A quick local markdown-link check reports zero broken internal links for docs/i18n.
Summary
Several translated documentation files under docs/i18n contain incorrect relative links to internal project docs. This causes dead links for non-English users trying to access setup, architecture, contributing, security, and license pages.
Problem
Internal links in translated files are using paths that do not resolve from the docs/i18n directory depth.
Confirmed examples in Spanish translation:
[es.md:252]
[es.md:286]
[es.md:291]
Impact
Non-English users hit dead links during onboarding.
Core trust/safety pages (security, license) are not reachable from translated docs.
Documentation quality appears inconsistent across languages.
Expected behavior
All internal markdown links in docs/i18n/*.md should resolve correctly based on the docs/i18n folder location.
Scope
Fix broken internal links in translated docs (starting with Spanish and then all other i18n files).
Keep external links unchanged.
Ensure consistency of internal link style across translations.
Acceptance criteria
All internal links in docs/i18n/*.md point to existing files.
Verified paths for:
Getting Started
Configuration
Architecture
Contributing
Security
License
Spot-check complete for:
zh-CN
es
hi
pt
ja
ru
ko
Suggested implementation
Use correct relative paths from docs/i18n (typically Terddy.LAPTOP-CVSRCLGL for root-level docs and ../ for sibling docs under docs).
Definition of done
PR updates broken links in translation files.
A quick local markdown-link check reports zero broken internal links for docs/i18n.