Review language/translation controls

[hunvreus]

Right now, we're not accounting for one of the key actions you may want to perform; translate content from a language to another.

In light of this, I'm proposing the following;

1. New entry; you can select the language. No translations menu.
2. Saved entry (no translation); language is locked (readonly) and there's a "Translations" menu button that allows you to translate the entry to other language.
3. Translate to (new entry); when creating a translation using the "Translate to" link in the translations menu, you land on that page. Language is locked. We may want to still display the "Translations" menu (although not necessarily), if at least to display the link to the entry you're translating (suggestions welcome here).
4. Saved entry with translations; same as 2., but there's a new category with the existing translations.

[hunvreus]

In the end, only two cases;

If you're creating a new entry (from scratch)

You're then asked to pick a language.

If you're translating or editing

Language is locked.

Caveat

We'll need to document this, because it means that if you mess up the language you need to;

1. Translate the file,
2. Delete the original file (or rectify the translations to the proper language).

I do think however that this sets a strong/guarded workflow and will prevent any nasty error.

[woodpig07]

Implemented, example /products/master/_products/teavana.md

[woodpig07]

Done, closing