Problem/Motivation
Noticed while reviewing #2301317: MenuLinkNG part4: Conversion
People who want to translate "Menus" are not going to realize they need to translate 3 different ways and enable 3 different translation modules.
Documenting now to translate Custom menu links on the menu_link_content module help page... is not a pattern we use. (We do not document how to translate nodes (articles) on the node help page. We do it on the Content translation help page... but by then, someone has already figured out to install (enable) the module, they can see the help.
Proposed resolution
Document (expose) how to enable translation for Menu Things (Menus/Configuration translation, (Plugin) menu links/User interface translation, Custom menu links/Content translation)
by:
making a general translate menu docs page on d.o
- change the UI so that all menu things have a translate drop down operation (would mean have the plug-in menu links have a translate operation that would link to the User interface translation page?)
- ?
Remaining tasks
- Think more about the problem and possible solutions.
- Move to the proper component once a solution is decided.
- Put the text from the various related module hook_helps here so we can see what we are talking about
- ?
User interface changes
?
API changes
No?
Comments
Comment #1
YesCT CreditAttribution: YesCT commented