Translations
The Translations page lets you override every piece of storefront copy and every transactional email your marketplace sends — for the locale configured under Localization. No language files to publish, no deployments to run.
Open the Translations page
- Go to Sites in the admin panel
- Click on your site to open its Home page
- In the sidebar, expand Build → General and click Translations
Permissions
Only team members with permission to update a site can change its translations. See Account settings for team roles.
How translation works
Yclas Neo ships with base translations for English, Spanish, German, and French. Each row on the Translations page represents a single string that appears somewhere in your storefront or in an email notification.
For each row, three values are at play:
- Display text — what visitors actually see, taking your override into account
- Baseline — the default value for the site's locale (for example, the official Spanish translation)
- Your override — the value you set on this page (empty unless you've customized it)
When you set an override, the storefront uses it. When you clear an override, the baseline takes over again.
Translations follow your locale
The Translations page edits strings for the locale configured under Localization. To translate a different locale, switch your site's locale first — then return here to edit.
Editing a string
- Click any row to open it for editing
- Type the new value (or clear the field to revert to the baseline)
- Click Save to apply, or Cancel to discard
Changes apply immediately to your storefront and transactional emails — there is no separate publish step.
Reverting a string
Rows you've overridden show a green Customized badge. Click Revert on any customized row to restore the baseline value.
Regional fallback
Locales often come in regional variants — es_MX (Spanish, Mexico) versus es (Spanish, generic). Yclas Neo walks a fallback chain so visitors never see raw keys:
- If you set your locale to
es_MX, we look for anes_MXtranslation first - If none exists, we fall back to the parent language (
es) - If that's missing too, we fall back to English (
en)
You only need to override the strings that don't fit your audience — the rest take care of themselves.
What gets translated
The Translations page lists every string the storefront and email notifications use, grouped by area:
- Storefront navigation — buttons, menus, and links in the header and footer
- Listings — labels on cards, detail pages, and the create/edit form
- Messages — inbox, conversation view, and empty states
- Account — login, register, password reset, and profile pages
- Emails — confirmation, password reset, listing expiration, and message notifications
Renaming English strings
Overrides aren't limited to other languages. If you want the "Post listing" button to say "Publish ad" instead, edit that row on an English-locale site — it works exactly the same way.
Default values
New marketplaces start with no overrides. The storefront renders the baseline translation for the site's locale, falling back to English when no translation exists.