Feature request - Add multi-lingual content feature

[exponentcms]

This feature would allow the site to better support multi-lingual content (we already support a multi-lingual admin interface).

Rough thinking would be some sort of dispatcher that would reference a 'content_expLang' record lookup for a assoc piece with the requested language. e.g., you ask for text item id =1, you are viewing on a secondary language of DE, and pull up the expLang where model = text and id = 1 to get a new text item id # for the DE version otherwise you go with the requested one.

There would need to be:

• an interface to describe the base language since it wouldn't always be English
• a setting to 'turn on' multi-lingual content
• an interface to easily edit various language versions of an item...while a tabbed edit would be the most intuitive, it would make updating objects difficult based on how it's done now
• a widget to select desired user language
• a 'hack' to not only dispatch to pull the desired language variation of the requested item(s), but also for the menus

[exponentcms]

As a note, this might be possible using a variation of the new workflow/revisions code. The simpler approach is to make them mutually exclusive whereby the revision_id is also the language_id, it would be much more complex to update the database layer to handle both mutli-languages and multi-revisions simultaneously.

[exponentcms]

[bulk edit]

[exponentcms]

[bulk edit]

[exponentcms]

[bulk edit]

[exponentcms]

As a note...we'd also want to have separate search indexes

[exponentcms]

Also...would need to factor in multi-lingual SEO

• would need to add parsing 1st sef url parameter of language such as http://exponent.org/es/blog/show/title/test
• would require adding hreflang to pages
• would need to allow for multi-lingual SEO Meta info for an item (title, description, keywords), but NOT change the sef_url...or would we?

We would probably NEVER pursue multi-lingual ecommerce since it would require some sort of union between most of the many product fields, but we shouldn't try to do any on-the-fly price, etc... conversions

[exponentcms]

Lighthouse URL: https://exponentcms.lighthouseapp.com/projects/61783/tickets/970