Issue #2342πŸ’¬ AnsweredOpened October 18, 2019by senchden0 reactions

Localisable component text based on page language

Quick answerby artf

I18n module is already in the roadmap

Read full answer below ↓

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)

artfβ€’ October 19, 2019

I18n module is already in the roadmap

senchdenβ€’ October 21, 2019

Does this module have any tentative date of implementation?

varaderoβ€’ November 6, 2019

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 tha...

Related Questions and Answers

Continue research with similar issue discussions.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins β†’
Premium option

Premium plugins ship with support, regular updates, and production-ready features β€” save days of integration work.

Browse premium plugins β†’

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.