Problem/Motivation
Creating many UIs for translation tools, needs high-level review to recommend a cohesive user experience.
Proposed resolution
Simple design of three different interfaces to make translating consistent across different interfaces, CSS changes, may need some larger changes, will see.
Add direct links to "Language" (admin/config/regional/language) configuration page to other multilingual pages - such as:
Content Language Settings (Add / Edit Content Types and other Entities that need to be translated) = admin/config/regional/content-language
User Interface Translation (Directly translate parts of the Drupal User Interface) = admin/config/regional/translate
Add a joy ride to explain different editing options. (See issue: http://drupal.org/node/1998516)
Remaining tasks
Recommendations and layouts as needed.
User interface changes
This is what we're working on!
API changes
TBD
Related Issues
#1836086: [meta] Entity Translation UI improvements
#1832836: Discuss how to view original translation from translation form
#1952394: Add configuration translation user interface module in core
#1998516: Please: more help after installing second language
Important to Note
There seems to be a consensus that having all translation functionality for one language (or even for all of Drupal) in one place would be the most user friendly ("I've added Spanish, now I want to change everything to Spanish - where can I see that?"). However, this is not likely to happen for core because of the need for context in translations (Where is this string coming from?). Instead we will need to rely on "education" and good documentation to help people make sure they have changed everything. A good tutorial in documentation is essential.
Reference Links:
node/1#overlay=admin/config/regional/translate
node/1#overlay=node/1/translations&overlay-context=node/1
en/admin/config/regional/language/detection/url