This message was deleted.

@gifted-leather-56422 What do you want to translate exactly? Dynamic data (those from airtable) or static data (those in Stacker, like buttons, hard-coded texts, etc.)

My plan is to split roles into RoleA-lang1, RoleA-lang2, RoleB-lang1, RoleB-lang2 Role A and Role B have their own separate templates, but then also, I will split those templates into 2 languages and have the column labels (in list view) and field labels (in detail view) translated.

Yes, it does, you want to translate what I call “dynamic content”. The way you want to do it should work out fine. It will just be harder and harder to maintain as you add more languages.

Yep, I was also waiting as long as possible to get to this point, to avoid changes on the existing templates. So what I was thinking, whether it’s possible to build a drop-down language selector to jump between languages, but I feel like it’s something a bit more complicated. Unless….. Does anybody know how quickly would the user entity update from Airtable to Stacker? Maybe I will find a way to change Airtable user record to change the language there, but then, I assume it wouldn’t be quick to propagate the change (and maybe even a log-out / login is required)

The alternative solution mentioned above won’t work, I don’t see how it could. The first solution where you build views based on the role and display relevant fields based on the role makes sense. But I don’t see how it could be done differently

Yeah, I’m probably thinking about some magic. (i.e. dynamically changing a role of a user)