Problem/Motivation
We want to showcase Drupal's multilingual capabilities in Umami, but Umami currently only imports content in one language.
This issue is to change the structure of files and folders under demo_umami_content to better store multiple languages.
Proposed resolution
Add a subfolder demo_umami_content/default_content/languages/en
Move article_body, recipe_instructions, articles.csv, pages.csv, recipes.csv folders within this new folder
Move the term definitions to their own CSV files per vocabulary so they can be referenced by row number, making it possible to cross reference terms across languages.
Update content import code to use this new structure.
After implementation, the imported content should be identical to as it would be without this patch. But it we can then proceed in another issue to start adding the corresponding es folder and updating the content import to import translated content.
Remaining tasks
None
User interface changes
None
API changes
None
Data model changes
None
Release notes snippet
None
Comments
Comment #3
markconroy commentedAdding
OOTB Arabictag.Comment #5
markconroy commentedWe've discussed this on OOTB weekly meeting and for now the best way to work on the content translation itself is keeping it in Google Docs.
Thank you for the amazing work you do!
The last decision regarding multilingual in Umami was to avoid adding more languages since it proved difficult to maintain. Instead, the solution would be improving
potxmodule, which already provides all interface string translations to any language.Once #3048283: Read content from Drupal 8 core's demo_umami feature will be added, #3048295: [PP-1] Install Umami in any language (import content from https://localize.drupal.org) can be completed, that allows Umami to support any language in a sustainable way.