-
Notifications
You must be signed in to change notification settings - Fork 334
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
Summarise approach and decisions for internationalisation in the Design System backlog #2749
Comments
From mid-sprint review:
|
Draft sent for comment and review. |
This reads really well to me, thanks for sharing @claireashworth. @romaricpascal please can you also review. |
That was some thorough gathering of all the I18n related issues! Cheers @claireashworth! Added a couple of comments on the doc so we can clarify a few things and then we should be in a good place. |
We just need to decide where we're publishing this information. I previously suggested adding it to this conversation thread - alphagov/govuk-design-system-backlog#99 |
I think the backlog issue makes as much sense as anywhere. I have added a few (hopefully minor!) comments to the Google Doc, but generally think it's looking really good. Thanks for doing all the hard work to pull all of that together, @claireashworth! 🙌🏻 |
Comments completed and summary published on #99 'Supporting multiple languages'. |
What
Write up a summary of our final approach for internationalisation and why we decided to follow that approach. Might also be a good opportunity to talk about the other things we tried and explain why those don't work. Also anything we've decided not to do (e.g: because it's not part of our MVP solution; because it's out of scope).
Why
We should try and be transparent about the decisions we make, to help people understand why we've done things a certain way.
This may also help as somewhere to refer people to if we get questions on support.
Who needs to work on this
Content, Developer
Who needs to review this
Content, Developer
Done when
The text was updated successfully, but these errors were encountered: