Internationalization (i18n) for Chef

We should start preparing Chef for internationalization.
As a first step, let’s add two translation files (en and es) for common UI text, even if the app still defaults to English.

Tasks

Create locales/en/ui.json with a few basic keys (e.g., Home, Save, Cancel).

Create locales/es/ui.json with Spanish equivalents. or even more

Add a simple utility to load these JSON files (even hardcoded import is fine for now).

Verify that components can use the translations via a small helper (e.g., t('home')).

Example translation file

locales/en/ui.json

{
"nav": {
"home": "Home"
},
"common": {
"save": "Save",
"cancel": "Cancel"
}
}

locales/es/ui.json

{
"nav": {
"home": "Inicio"
},
"common": {
"save": "Guardar",
"cancel": "Cancelar"
}
}
i can provide more context if you like and please assign me this issue if you like

Start by locating the component entry points and the existing project structure around locales/. Review the requested locales/en/ui.json and locales/es/ui.json examples, then determine where the translation-loading utility and helper belong. Done means both locale files exist, the helper can resolve keys such as home, save, and cancel, and a component can use the translations.

Written by the indexing model from the issue text.