-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Localization for client-side route announcements #20801
Comments
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. Thanks for being a part of the Gatsby community! 💪💜 |
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here. Thanks for being a part of the Gatsby community! 💪💜 |
Hey again! It’s been 60 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Thanks again for being part of the Gatsby community! 💪💜 |
Hello! We are very interested in getting this feature working. As an MVP solution, would it be possible to add a manual message somehow with a config or such? We only use one language at our site (which is not Englisht) |
Summary
Support localization for the "Navigated to" portion of the route announcement in the
gatsby-announcer
div.Motivation
This announcement is to increase the accessibility of Gatsby. Serving users content in a way that is adapted to their language & culture is part of that mission.
Related
This builds on work done in #19290
The text was updated successfully, but these errors were encountered: