[PAGES-26] As an editor, I want a i18n systemtext-app out of the box, to create multisite and multilanguage websites. Created: 19/Jun/15  Updated: 23/Aug/22

Status: Open
Project: Magnolia pages module
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Orlando Maier Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Team: AuthorX

 Description   

Almost every website project needs a possibility for editing and translating system texts (such as "read more", "close", "back"), that can be placed throughout templates.
This should be provided out of the box, supporting multisite and multilanguage websites as well.



 Comments   
Comment by Antti Hietala [ 11/May/17 ]

Status update 2017-05-11: MGNLDEMO-212 provides a best practice example and establishes a file naming convention for organizing template labels ("Read more", "Close", "Back" etc.) into a separate message bundle. We will use the travel demo as an example module.

Comment by Orlando Maier [ 17/May/17 ]

Our main problem we had is the missing possibility, to edit these „template labels / system texts“ on the fly by our editors. We need to edit and translate these strings by our editors, in Magnolia. Because they can't access message bundles.

Comment by Antti Hietala [ 17/May/17 ]

omaier, you are quite right that template labels are intended for visitors and therefore have different localization requirements. However, this group of text has typically been rather small in projects that we have seen – a few items at most such as "Read more" and "You are here". Handing a message bundle file to a translator and getting it back into the project has typically worked OK.

In your project, do you change template labels often? Do you edit them many times during a project or mainly in the beginning? If there's a need to edit/add labels frequently then I can see how a different editing experience would be beneficial. We just need to understand better what kind of projects would benefit from a separate app.

Comment by Orlando Maier [ 18/May/17 ]

Currently we are using about 120 template labels in our project for 60 sites. These 60 sites are using 27 different languages.
No, we don't change template labels often. The typical process for introducing a new template label works like this:
1. We implement a new feature, that can be used by all editors/sites. The new feature/component/whatever is using a template label
2. We release a new version of our customized Magnolia, including the new feature
3. We provide the new template label in English and German in Magnolia
4. We inform our editors about the new feature and that they have to translate the template label if they want to use the feature
5. Anytime between now and then some editors will use the feature and therefore they have to translate the template label.

Generated at Mon Feb 12 06:14:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.