Explore a CMS flow/UX that ensures core pages are all sent for translation

[stevejalim]

The refreshed site will have a set of core pages which should be localized in to all core languages.

Ideally, @stephaniehobson is keen for this to happen automatically - this would avoid the risk of someone forgetting to sent a particular page for localization, avoids the risk of partial localization of a page, and avoids the need to tell editors how to do it.

One suggestion is that we automate the steps of clicking translate this page, selecting all the locales, then the Send to Smartling button, then Submit. This has a lot of value but it's TBC whether we can make the equivalent steps all happen smoothly, as that user journey has a few touchpoints internally in Wagtail and isn't a single API call.

Other things to work out, beyond initial feasability:

• When do we want to this to happen? It might have to be that we still need to click the 'Translate this page' trigger as a clear signal the page is definitely ready, as saving Drafts/Previews and even Publishing a page aren't guarantees they should immediately go to translation
• How do we communicate to Wagtail which pages are "core" and which are not? The position/heirarchy in the page tree isn't going to be reliable enough, but we could start using tags on pages, and if a page is tagged core and Translate this page is hit, that could trigger the fast-track behaviour. However, this would bring in a need for some more editor-education, and if we're doing that, it's not that much more to just explain how do to it manually, given the relatively small number of core pages envisioned