You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CLAUDE.md
+29Lines changed: 29 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,6 +28,35 @@ When creating or modifying any page, module, or data:
28
28
-**DRY principle for translations:** Before creating new translation keys, search existing translation modules thoroughly to reuse existing terms and phrases
29
29
-**Consistency:** Use the same translation keys across similar contexts
30
30
31
+
### Translation File Organization
32
+
33
+
Follow the detailed architecture rules in [docs/I18N-ARCHITECTURE-RULES.md](docs/I18N-ARCHITECTURE-RULES.md) for organizing translation resources.
34
+
35
+
**Core Principles:**
36
+
1.**Page translations**: Each page or page group should have its own JSON file (e.g., `ides.json`, `ide-detail.json`)
37
+
2.**Component translations**: Organize by component directory:
-`components/navigation.json` - All navigation/* components
40
+
-`components/controls.json` - All controls/* components
41
+
-`components/sidebar.json` - All sidebar/* components
42
+
-`components/product.json` - All product/* components
43
+
3.**Minimize `@:` references**: Use `tPage + tShared` or `tComponent + tShared` patterns in code instead of cross-namespace references in JSON
44
+
4.**Metadata placement**: Co-locate page metadata (title, description, etc.) with page translations under a `meta` object
45
+
5.**Multi-language workflow**: New translation keys should initially use English placeholders across all locales, with proper translation in a separate batch step
0 commit comments