[GH-ISSUE #2141] docs: move translated READMEs into a dedicated directory #701

Closed
opened 2026-10-15 18:27:31 +00:00 by bsakaguchi · 4 comments
Owner

Originally created by @N0zoM1z0 on GitHub (Oct 12, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/2141

Originally assigned to: @N0zoM1z0 on GitHub.

Problem

REA currently has an English README.md and 18 translated READMEs in the repository root. Keeping the translations together would make the root easier to browse while preserving language access from the main README.

Both layouts exist in other projects. RustDesk stores translated READMEs under docs/, and Coding Interview University uses translations/. OpenCode keeps them in the root. A dedicated directory is a useful organization choice for REA's current number of translations.

Proposal

Keep the English README.md in the root and move existing translations into docs/readme/, preserving their filenames and language codes.

README.md
docs/
  readme/
    README_zh.md
    README_zh-TW.md
    README_fr.md
    ...

Acceptance criteria

  • All languages remain accessible from the English README and translated language navigation.
  • Relative guide links, images, license links, and links back to English resolve from their new locations.
  • Documentation consistency checks continue to cover every translation and compare resolved link targets.
  • Website language metadata and README discovery use the new paths.
  • CI change classification continues to recognize translated README changes.
  • Existing references and compatibility expectations for old file URLs are reviewed.

Translation wording can stay unchanged apart from path updates. English remains the canonical content source; translation accuracy and synchronization still require their existing maintenance checks.

This issue records the agreed layout. The file migration will be handled separately from the current English documentation audit.

Originally created by @N0zoM1z0 on GitHub (Oct 12, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/2141 Originally assigned to: @N0zoM1z0 on GitHub. ## Problem REA currently has an English `README.md` and 18 translated READMEs in the repository root. Keeping the translations together would make the root easier to browse while preserving language access from the main README. Both layouts exist in other projects. [RustDesk](https://github.com/rustdesk/rustdesk/blob/master/README.md) stores translated READMEs under `docs/`, and [Coding Interview University](https://github.com/jwasham/coding-interview-university/blob/main/README.md) uses `translations/`. [OpenCode](https://github.com/anomalyco/opencode/blob/dev/README.md) keeps them in the root. A dedicated directory is a useful organization choice for REA's current number of translations. ## Proposal Keep the English `README.md` in the root and move existing translations into `docs/readme/`, preserving their filenames and language codes. ```text README.md docs/ readme/ README_zh.md README_zh-TW.md README_fr.md ... ``` ## Acceptance criteria - All languages remain accessible from the English README and translated language navigation. - Relative guide links, images, license links, and links back to English resolve from their new locations. - Documentation consistency checks continue to cover every translation and compare resolved link targets. - Website language metadata and README discovery use the new paths. - CI change classification continues to recognize translated README changes. - Existing references and compatibility expectations for old file URLs are reviewed. Translation wording can stay unchanged apart from path updates. English remains the canonical content source; translation accuracy and synchronization still require their existing maintenance checks. This issue records the agreed layout. The file migration will be handled separately from the current English documentation audit.
Author
Owner

@aimalexe commented on GitHub (Oct 12, 2026):

I'd suggest placing the translated READMEs under docs/, as this is a common convention in many open-source projects

<!-- gh-comment-id:6123292001 --> @aimalexe commented on GitHub (Oct 12, 2026): I'd suggest placing the translated READMEs under `docs/`, as this is a common convention in many open-source projects
Author
Owner

@aimalexe commented on GitHub (Oct 12, 2026):

I’d like to work on this issue if that’s okay @N0zoM1z0

<!-- gh-comment-id:6123344537 --> @aimalexe commented on GitHub (Oct 12, 2026): I’d like to work on this issue if that’s okay @N0zoM1z0
Author
Owner

@N0zoM1z0 commented on GitHub (Oct 13, 2026):

Thanks for taking this on and opening #2165, @aimalexe! We'll review the PR and help resolve the conflicts.

<!-- gh-comment-id:6139354380 --> @N0zoM1z0 commented on GitHub (Oct 13, 2026): Thanks for taking this on and opening #2165, @aimalexe! We'll review the PR and help resolve the conflicts.
Author
Owner

@aimalexe commented on GitHub (Oct 13, 2026):

Thanks! I appreciate the help. Let me know if anything needs to be changed @N0zoM1z0

<!-- gh-comment-id:6140078713 --> @aimalexe commented on GitHub (Oct 13, 2026): Thanks! I appreciate the help. Let me know if anything needs to be changed @N0zoM1z0
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#701
No description provided.