[FEATURE] Enable multi-language editing in Visual Editor#106
Draft
Kanti wants to merge 1 commit into
Draft
Conversation
Add a multi-language editing experience to the Visual Editor so editors can work with translated pages in one place instead of switching back and forth between separate language views. Editors can keep the regular single-language workflow when they only want to focus on one language. On TYPO3 14, they can also switch the module to multi-language mode and select multiple available languages. The editor then shows the selected language previews next to each other, making it easier to compare content, spot missing translations, review layout differences, and keep related language versions aligned while working on a page. The selected language views behave as one editor workspace. Loading feedback is shown while previews navigate, save state is coordinated across the open language frames, and related editor interactions stay in sync where this helps the user keep orientation. This includes preserving the editing position, mirroring relevant focus and movement changes, and keeping the editor from feeling disconnected when several language previews are open at the same time. When a selected language belongs to another site origin, the module now guides editors to open the backend on the matching origin instead of leaving them with a broken or confusing preview. This keeps browser security boundaries intact while still explaining what the editor needs to do next. The change also includes bug fixes around the editor module behavior that became visible while making the multi-language workflow usable, so the feature works more consistently during navigation, saving, and translated-page editing.
0538595 to
de78359
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a multi-language editing experience to the Visual Editor so editors can work with translated pages in one place instead of switching back and forth between separate language views.
Editors can keep the regular single-language workflow when they only want to focus on one language. On TYPO3 14, they can also switch the module to multi-language mode and select multiple available languages. The editor then shows the selected language previews next to each other, making it easier to compare content, spot missing translations, review layout differences, and keep related language versions aligned while working on a page.
The selected language views behave as one editor workspace. Loading feedback is shown while previews navigate, save state is coordinated across the open language frames, and related editor interactions stay in sync where this helps the user keep orientation. This includes preserving the editing position, mirroring relevant focus and movement changes, and keeping the editor from feeling disconnected when several language previews are open at the same time.
When a selected language belongs to another site origin, the module now guides editors to open the backend on the matching origin instead of leaving them with a broken or confusing preview. This keeps browser security boundaries intact while still explaining what the editor needs to do next.
The change also includes bug fixes around the editor module behavior that became visible while making the multi-language workflow usable, so the feature works more consistently during navigation, saving, and translated-page editing.