When a theme has no translations for its Headstart annotations, Headstart will return a set of default translated content. This content is totally different from the theme demo site or previews!
As a result, the content will be mismatched with the preview in both SPT, and in the theme switch when replacing homepage content.
See this example in SPT:
We should offer a more obvious fallback. I see some options:
I've heard a strong argument in favor of option two from @AtrumGeost
Obviously this is just a stop-gap measure while we make sure that the themes _do_ have correct translations to show.
We also need to do make sure that translations exist for these themes:
I have verified that each of the other recommended themes _do_ have translated headstart content.
Update October 22: All of the above themes have been submitted for translations.
Update November 13: I deployed the final translations for all of the listed themes.
As offered, we talked about this in our last ES Hangout ( p7SG42-uY-p2 ). We agreed that for a localized user (who'll end up replacing the Page Layout content with their own) it is better to get a Page Layout in English than nothing.
Thank you!
thanks for that feedback!
I've verified that the translations are in the i18n pipeline for these themes now. Unsure how long it will take to get them on wpcom, but at least are being worked on now!
Fix for the fallback issue here: D51621-code.
This is fixed now. I verified the fix with maywood in the ES locale. All of the caches will invalidate over the next 24 hours, so let me know if we are still seeing issues with this after then!
We sent these out for translation on November 1 and all languages were delivered at the beginning of last week. I checked the page layouts for these themes and it looks like these are still showing up in English. https://d.pr/i/ofVDWp/BTeb7uKH2O
Normally, the translations need to be manually deployed by the developer. You should have received an email about how to deploy these. I believe the command you run needs to be something like wp linguine headstart-deploy [strand id]
Here are the strand IDs
Maywood - strand 68488
Balasana - strand 68489
Shawburn - strand 68490
Twenty Twenty - strand 68491
Seedlet - strand 68375
Nice, thanks @emilyaudela. Unfortunately, I did not get an email, but I will look into that and make sure they are deployed!
Alright, they should all be deployed now. The new content should make its way to the SPT selector within 24 hours as caches invalidate.