Problem/Motivation
Well this is obviously some low-hanging fruit. (Kidding, this is going to be very complicated.)
Currently recipes are not translatable. They may have hard-coded strings that are presented to users (e.g., during input collection), or saved in config in some way. These strings need to be translatable. But there's no way to do it, or at least no clear way. We have no mechanism to extract translatable strings from recipe.yml files, and even if we did, we don't necessarily have a mechanism for shipping recipe translations, or displaying/using those translations when they're needed.
This needs to be figured out.
Proposed resolution
Honestly, I have no idea. @alexpott said he had some thoughts. But I expect the approach(es) we take to be interesting, and to evolve over time.
Remaining tasks
TBD.
User interface changes
TBD.
Introduced terminology
TBD.
API changes
TBD.
Data model changes
Probably none, but who knows.
Release notes snippet
TBD.