Localization
Objective — Expand to new locales without forking vendor Blade — language files, locale middleware, and payment methods per region.
Assessment 👤
Section titled “Assessment 👤”- Rank markets by revenue potential, support cost, and regulatory burden.
- List UI strings scope (admin vs customer-facing) before quoting translation.
Laravel i18n 💻
Section titled “Laravel i18n 💻”- Store strings in
lang/{locale}/— never hardcode in vendor views; use@langor__()in customizations. - Locale switcher + session/
app()->setLocale()middleware. - Fallback locale defined; missing keys log in staging only
graph LR EN["lang/en/*.php"] --> FR["lang/fr/*.php"] FR --> UI["Blade / JSON responses"] UI --> SEO["hreflang + regional URLs"]Translation workflow 🔀
Section titled “Translation workflow 🔀”- Export keys → vendor or CAT tool → import → QA in staging per locale.
- Freeze string freeze window before major releases.
Regional SEO & payments
Section titled “Regional SEO & payments”hreflangtags and locale-prefixed URLs or subdomain strategy (pick one).- Local payment methods (Stripe Payment Methods API) where checkout supports them.
Customizations playbook Mark vendor view overrides when locale-specific UI is unavoidable.