[MGNLMULTPA-42] Provide generic i18n keys for Pages apps Created: 27/Nov/23  Updated: 01/Dec/23  Resolved: 01/Dec/23

Status: Closed
Project: Multiple Pages Apps
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0.0

Type: Improvement Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Chuong Doan Huy
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLMULTPA-54 Implement Sub-task Completed Chuong Doan Huy  
Template:
Acceptance criteria:
Empty
Epic Link: Multiple Pages App LD
Sprint: DevX 52
Story Points: 2
Team: DeveloperX
Work Started:

 Description   

Currently, if you do not supply i18n keys - then most of your custom pages apps will show the keys. We would like the app to look good and be ready to use without having to supply keys, like the Content-type driven apps do. 

As with the Content-type driven apps - we should provide a set of generic translations for the aspects of Pages apps. The translations can be things like "Add item"

Then if a developer wants to - they can still provide custom keys for the app. To provide things like "Add banner".

 

Tech notes:

An attempt: https://git.magnolia-cms.com/users/czimmermann/repos/page-fragments-demo/browse/magnolia/light-modules/banner-lm/i18n/generic-pages-app-messages_en.properties

For the beta release - the keys could be in this module.

In the future - it would probaably be best to put the keys wherever the contenttype-app keys are stored.


Generated at Mon Feb 12 10:21:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.