Right now, translations are limited to the UI and emails. It should be possible to access a function like context.i18n('path.to.translation') and load translations on the server, too. Helpful for server-side error messages that eventually make it back to the client.
Best way to do this is to just load the current i18n/<language>.js file into the context, relative to either the default app language or if there's a user, the user language.
Right now, translations are limited to the UI and emails. It should be possible to access a function like
context.i18n('path.to.translation')
and load translations on the server, too. Helpful for server-side error messages that eventually make it back to the client.