Problem
currently instatic is only usable for websites that "speak" one language. but most websites need more languages. for that it would be a great addition to have built in l10n and even better i18n.
Proposed solution
that contains (just a few examples):
having a language picker module for both frontend and backend.
having the option so place an api key for any translation service of choice.
having to push auto translation for all content
having the ability to edit translations manually within cms fields (mandatory) or even witihin visual builder (optional)
and of course change language tags in code output, also translate structured data like json ld etc.
could be a great use case for an instatic plugin though.
Alternatives considered
No response
Area
Content workspace
Problem
currently instatic is only usable for websites that "speak" one language. but most websites need more languages. for that it would be a great addition to have built in l10n and even better i18n.
Proposed solution
that contains (just a few examples):
having a language picker module for both frontend and backend.
having the option so place an api key for any translation service of choice.
having to push auto translation for all content
having the ability to edit translations manually within cms fields (mandatory) or even witihin visual builder (optional)
and of course change language tags in code output, also translate structured data like json ld etc.
could be a great use case for an instatic plugin though.
Alternatives considered
No response
Area
Content workspace