Skip to content
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

Closed
1 task
Tracked by #1708
vanitabarrett opened this issue Aug 8, 2022 · 7 comments
Closed
1 task
Tracked by #1708

Comments

@vanitabarrett
Copy link
Contributor

vanitabarrett commented Aug 8, 2022

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

@kellylee-gds
Copy link
Contributor

kellylee-gds commented Dec 6, 2022

From mid-sprint review:

  • Look through Google Drive for relevant documentation related to i18n. Pull information from docs we think will be useful to users
  • Check whether we have guidance in internal docs about how to translate components (if not, this feels like it's own card tbh)
  • Use decision summaries published previously as a template for recording this information (eg Cookie Banner)

@claireashworth

@claireashworth
Copy link
Contributor

Draft sent for comment and review.

@kellylee-gds
Copy link
Contributor

This reads really well to me, thanks for sharing @claireashworth. @romaricpascal please can you also review.

@romaricpascal
Copy link
Member

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.

@claireashworth
Copy link
Contributor

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
Any other thoughts?

@stevenjmesser stevenjmesser moved this from Blocked ⛔ to In progress 📝 in GOV.UK Design System cycle board Feb 8, 2023
@36degrees
Copy link
Contributor

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! 🙌🏻

@claireashworth
Copy link
Contributor

Comments completed and summary published on #99 'Supporting multiple languages'.

@claireashworth claireashworth moved this from In progress 📝 to Done 🏁 in GOV.UK Design System cycle board Feb 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

5 participants