-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Localize the Initiatives page #3643
Comments
@alanmoo can you estimate this and accordingly put it into this milestone? |
I'm estimating with the framing that I think this is mainly a matter of adding translation hooks to the various fields. |
Right, but it will also require to localize Highlights (and I don’t know if it’s as straightforward as adding translation hooks to fields) |
@TheoChevalier after speaking with @Pomax , localizing the headers and initiative blocks is the most that can be done right now and we'll need to localize the highlights in a follow-up ticket. I believe @alanmoo and @kristinashu are currently in talks around how to approach highlights at the moment, so once that's done, we can create a follow-up ticket for localizing the highlights sections. 🙂 👍 |
Sounds good @youriwims , thanks! I’ll go ahead and expose the strings in Pontoon, minus highlights. Having the initiative blocks alone should justify deploying translations of the page |
Not a problem—sounds great! :) |
Closing this issue due to having gone stale - if this is still something we want to do, let's file a new issue with all the information necessary for triaging. |
Many fields are currently not localizable in Wagtail for this page, let’s fix that!
The text was updated successfully, but these errors were encountered: