fix: move i18n languages for best practices

.github/workflows/crowdin-upload-sources.yml

@@ -2,10 +2,10 @@ name: Crowdin Upload Sources Action
 
 on:
   push:
-    # Monitor all .json files within the /src/i18n/locales/en/ directory.
+    # Monitor all .json files within the /i18n/locales/en/ directory.
     # This ensures the workflow triggers if any the English namespace files are modified on the main branch.
     paths:
-      - "/src/i18n/locales/en/*.json"
+      - "/i18n/locales/en/*.json"
     branches: [main]
   workflow_dispatch: # Allow manual triggering
 

CONTRIBUTING_I18N_DEVELOPER_GUIDE.md

@@ -13,8 +13,7 @@ your needs already exists. Many common labels like "Save," "Cancel," "Name,"
 "Description," "Loading...," or "Error" are likely already present, especially
 in the common.json namespace. Reusing existing keys prevents duplication and
 ensures consistency across the application. Using your code editor's search
-function across the /src/i18n/locales/en/ directory is an effective way to do
+function across the /i18n/locales/en/ directory is an effective way to do this.
-this.
 
 ### Key Naming and Structure Rules
 
@@ -58,7 +57,7 @@ when creating new keys in the JSON files.
 ### Namespace Rules
 
 We use namespaces to organize keys. All source keys are added to the English
-(`en`) files located at `/src/i18n/locales/en/`. Place your new keys in the
+(`en`) files located at `/i18n/locales/en/`. Place your new keys in the
 appropriate file based on these rules:
 
 - `common.json`:

crowdin.yml

@@ -6,5 +6,5 @@ base_url: "https://meshtastic.crowdin.com/api/v2"
 preserve_hierarchy: true
 
 files:
-  - source: "/src/i18n/locales/en/*.json"
+  - source: "/i18n/locales/en/*.json"
-    translation: "/src/i18n/locales/%locale%/%original_file_name%"
+    translation: "/i18n/locales/%locale%/%original_file_name%"