···214214215215### Approach
216216217217-- All user-facing strings should use translation keys via `$t()` in templates or `t()` in script
217217+- All user-facing strings should use translation keys via `$t()` in templates and script
218218- Translation files live in `i18n/locales/` (e.g., `en.json`)
219219- We use the `no_prefix` strategy (no `/en/` or `/fr/` in URLs)
220220- Locale preference is stored in cookies and respected on subsequent visits
···233233 Or in script:
234234235235 ```typescript
236236- const { t } = useI18n()
237237- const message = t('my.translation.key')
236236+ <script setup lang="ts">
237237+ const message = computed(() => $t('my.translation.key'))
238238+ </script>
238239 ```
2392402402413. For dynamic values, use interpolation: