You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Epic for Wagtail Localization. The spike ticket can be found at #6671
All the below tasks are split into tickets in this epic, with the step number in the title so we don't get too far ahead of ourselves and need to spend time backtracking.
The localization branch we're using in this repo is the wagtail-localize-2021branch. Note: Please keep the original wagtail-localize branch as it has code we may want to reference in there while we work on localization.
Step 1. Upgrade Django ato Django 3, and Wagtail to 2.12 #6702 We really should, but don't have to, upgrade to Wagtail 2.13 and Django 3.2 before adding wagtail-localize. I think the last dry run I did up to Wagtail 2.13rc1 required me to do some model-translation work.
Upgrade Wagtail to 2.12.* and upgrade Django to 3.0.*
Upgrade Wagtail to 2.13 and upgrade Django to 3.2.*
Add in wagtail-localize into the requirement dependencies
Merge into review branch and let CI run for higher future-merge confidence
Step 5. List out which models and fields need translating #6707 List out which fields should be TranslatableField and which fields should be SynchronizedField. @TheoChevalier we can really use your help here. A list of models/pages with which fields should be Translatable Vs Synchronized would be a life saver for implementation.
We might end up at a point where we need to work on just tests for a while. I recall some of these being rather tricky. First up: Make sure cypress tests for redirects work.
Make sure redirect tests continue to redirect to the appropriate language
Write documentation on how to implement and support pontoon with any gotchas documented as well. Might be useful to put this in the wagtail-localize.org docs.
We said we'd write docs for moving away from wagtail-modeltranslation and contribute it back to wagtail-localize. Lets write documentation on how we moved away from wagtail-modeltranslation to wagtail-localize, and commit the changes to the wagtail-localize docs
TRACKING DEPLOYMENT ISSUES
Use #7233 to report any issues you find while we're stage testing.
Merge requirements
make sure wagtail-localize-2021 is up to date with current master
Epic for Wagtail Localization. The spike ticket can be found at #6671
All the below tasks are split into tickets in this epic, with the step number in the title so we don't get too far ahead of ourselves and need to spend time backtracking.
The localization branch we're using in this repo is the
wagtail-localize-2021
branch. Note: Please keep the originalwagtail-localize
branch as it has code we may want to reference in there while we work on localization.Helpful resources:
Steps needed to [re]implement wagtail-localize
thing_en=
in the source code and remove the_en
translatable_fields = [ .. ]
set on themrequest
object, particularly around redirects.TRACKING DEPLOYMENT ISSUES
Use #7233 to report any issues you find while we're stage testing.
Merge requirements
wagtail-localize-2021
is up to date with current masterwagtail-localize-2021
into masterPre-deploy steps
Post deploy steps (#6713)
foundation-localize
heroku appThings we'll need to secure before getting started:
Helpful code snippets for future reference:
The text was updated successfully, but these errors were encountered: