i18n Content Slots Fallback to default culture

[fotakis]

In order to ease the translation and i18n of a website, it would be useful if apostrophe can fall back to the default culture for the content slots.

The current workflow is the following:

1.) Create content/pages/slots in English (Complex Navigation)
2.) Switch culture
3.) Rename page ( For each navigation item )
4.) Switch to default culture
5.) Per slot jot down the slots and content

5.1) In case of a slideshow, we have to recreate it per culture

6.) Switch culture
7.) Recreate all the slots and write content for each. (Possibly look to 5)

By adding the functionality of the default culture fallback the workflow would change as follows

1.) Create content/pages/slots in English
2.) Switch culture
3.) Translate the page name
4.) For each content slot start translating.

This feature would also help with the navigation, because at the moment once the culture switches if the pages do not have a corresponding translation for user culture, they are not shown anywhere, so you need to keep switching.

[boutell]

This is an interesting idea but how would we handle areas? They might not have the same number of slots in them in a different translation. Would you like us to copy them on first edit in a new language? That would break the connection to the default language going forward, but it wouldn't happen until you'd made some kind of a change to some slot in that area.

[boutell]

We'll keep thinking about this, but you don't have to jot things down. (: Use a different browser to keep the other language open. That is a reasonable workflow for now, we'll be looking at elegant ways to offer a peek at the default language (or any language) in 1.1