# This is NOT the Next.js you know This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in `node_modules/next/dist/docs/` before writing any code. Heed deprecation notices. # Translations and Locale Management Rule - All translation files must be located in `src/translations/` (NOT `src/i18n/`). - Inside `src/translations/locales/`, there are NO subdirectories. Each language has a single, flat key-value JSON file (`ar.json`, `az.json`, `bn.json`, `zh.json`, `da.json`, `de.json`, `en.json`, `es.json`, `fa.json`, `fr.json`, `gu.json`, `ha.json`, `he.json`, `hi.json`, `id.json`, `ks.json`, `pt.json`, `ru.json`, `sw.json`, `tg.json`, `tr.json`, `ul.json`, `ur.json`, `uz.json`). - Registration form structure data is kept separately in `src/data/questions/`. - CRITICAL AUTOMATION RULE: Whenever any new static text, data, field, component label, tooltip, help description, key, or text item is added or updated in the project, its translation key and values MUST automatically be added/updated in ALL 24 locale JSON files (`src/translations/locales/` & `src/data/questions/`). - QUESTION HELP & TOOLTIPS RULE: All question help texts, tooltips, and modal descriptions must be stored with key-value entries in the respective locale JSON files, ensuring complete synchronization across all supported languages.