[Feature request] Localisable component text based on page language
Question
It would be great to create pages that would share the component layout, but allow to edit text for each component based on language value set externally (one page per language). Not sharing layout per language is not optimal since if a user edits not only the component text, but also the page layout, all pages in other languages must be edited to use the new layout, which is not easily maintainable. Personally, I envision this as component inner text not being propagated to HTML inner text on export, but rather as pairs of component id (or text key) and text values.
Answers (3)
I18n module is already in the roadmap
Does this module have any tentative date of implementation?
Looking at the branch named i18n and i18n module code here: https://github.com/artf/grapesjs/tree/i18n/src/i18n it looks like this module is not for localizing page content that the users are creating but just the GapesJS interface itself, is that right @artf ? We also would like to have module that will enable the users to provide different texts of the pages they create for different languages. If the i18n module on the roadmap is not about supporting different page languages, do you have an idea how can we implement it in a "GrapesJS" way ?
Related Questions and Answers
Continue research with similar issue discussions.
Issue #3608
FEAT: Disable Dragging
What are you trying to add to GrapesJS? I have implemented an alternative text editing component (not based on RTE). I want people to be ab...
Issue #3076
QUESTION: Set component's empty state
Hi @artf , How would you recommend giving a component an empty state? Say, for instance, I have a layout component (ie. a column) which sho...
Issue #2744
[QUESTION] Disable a block drag&drop
Hello everyone, I would like to make forbidden the drop of one block before another specific one. Context : i've create a new trait for som...
Issue #1004
[FEATURE REQUEST] Enhance "draggable" attribute of components in order to allow excluding certain components when wildcard "*" is set for draggable components
Hi. I wish to enhance "draggable" attribute of components in order to allow excluding certain components when wildcard "*" is set for dragg...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.