1
Internationalization (i18n) Architecture for Supabase Studio
Source: supabase/supabase#41896 · opened by @aiyi404
Title: [Proposal] Internationalization (i18n) Architecture for Supabase Studio Hi Supabase Team and Community, I am a huge fan of Supabase and have been using it extensively. As the community continues to grow globally, I believe adding Internationalization (i18n) support to the Supabase Studio (Dashboard) would be a significant step forward. It would lower the barrier to entry for non-English speakers and further boost Supabase's adoption in regions like East Asia, Latin America, and Europe. I understand that apps/studio is a large Next.js application and that retrofitting i18n is a massive undertaking. Therefore, I am proposing a gradual, non-disruptive strategy to implement this, and I am willing to volunteer to set up the infrastructure. 🐛 The Problem Currently, all UI strings in the Studio are hardcoded in English within the .tsx files. This makes it impossible to support other languages without forking the project, which limits accessibility for global develope…
No pledges yet. Be the first to back this.
Comments
Similar requests
Self-Hosted: User Authentication Context and Auditability in Supabase Studio
3 votes · 0 comments
Local supabase studio and supabase dashboard looks too similar.
3 votes · 0 comments
Self-hosting version need i18n support
2 votes · 0 comments
Edge functions not showing in local Supabase Studio
15 votes · 0 comments
Request: Internationalization for Authentication Email Templates
58 votes · 0 comments
No comments yet.