WeWeb supports multilingual pages, where page structure stays identical and only the textual contents of elements are replicated and displayed according to the user selected language.
This is good because it makes it easier to create and maintain multilingual sites without page or element duplication.
At the same time, it seems that there is a challenge with RTL languages such as (Arabic, Azeribaijani, Divehi, Fula, Hebrew, Kurdish, Persian, Urdu and others).
The particular challenge is the display and alignment of elements on RTL language pages, which at this time appears to be coupled to a generic LTR display mode adopted across WeWeb pages.
In light of the current challenge described above, how can I display LTR and RTL contet on the same WeWeb site without having to duplicate all elements and add conditional display logic to each element to appear based on language selection?
PS: duplicating all elements and adding conditional logic is something that I think needs to be completely avoided, as it is not a practical solution at all.
Can WeWeb add additional internal presets for alignment and position to be from right-to-left for pages of RTL languages?
Correct display of RTL content in RTL language pages (should be): Manual changes made: 1. Aligment of container: right 2. Alignment of headlines: right 3. Sizing of headlines: |<->| instead of ->|<- 4. Alignment of button: right
The challenge descibed here becomes more clearly apparent when switching language back to an LTR one (en), where you can see that the changes I made to correct the RTL display are persisting also for LTR.
For now this is something we do not support. Container direction are RTL compliant, but not margin/padding etc.
We need to go through all our components to check we use RTL compliant properties + have a way to ignore/force (like vuetify).
This require a lot of work on dev and UX design, and i understand this can be an important feature.
I have push this to the product team, but this is not on our roadmap for the moment.
Feel free to use this subject to push us suggestion for when we implement this feature