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

Add support for other languages #14

Open
natebass opened this issue Aug 12, 2023 · 0 comments
Open

Add support for other languages #14

natebass opened this issue Aug 12, 2023 · 0 comments

Comments

@natebass
Copy link
Member

natebass commented Aug 12, 2023

Translate the website to other languages to increase awareness in non-English speaking communities. This could help foster relationships with non-English media outlets and local journalists.

This would require translating static text (non-data related) into multiple files, like en.json and es.json, that the application would inject into the page when a language is selected. We would need to coordinate volunteers to help to do this. We could do some of the translation automatically, but the process shouldn't be totally automated.

To officially support a language, I think we should have a fluent speaker overview the changes. Instead of manually clicking through the site, we could create a list of all links that need to be checked. These links would then be signed off ✅ or marked for changes ❌. We should consider a document type, form, or other type of application that could help with facilitating this.

Svelte library we could use: https://github.com/kaisermann/svelte-i18n.

Routes for languages could look like this:

Indicating language in links: https://www.w3.org/International/questions/qa-link-lang

@natebass natebass self-assigned this Aug 13, 2023
jeremiak added a commit that referenced this issue Oct 15, 2023
We don't support these features (maybe other cities #1, definitely other languages #14) so I'm hiding from the UI to avoid confusion/set appropriate expectations for users
jeremiak added a commit that referenced this issue Oct 16, 2023
* Comment out location and language toggles

We don't support these features (maybe other cities #1, definitely other languages #14) so I'm hiding from the UI to avoid confusion/set appropriate expectations for users

* Use bootstrap classes for responsive <Nav />

Bootstrap provides a Navbar component set of styles (https://getbootstrap.com/docs/5.3/components/navbar/) and since we're already including it by virtue of using Tabler we might as well just do the thing and only have custom CSS when absolutely required?

* Add margin top to <Footer />

* Use bootstrap classes for block totals of upcoming election, city, and county

Trying to use Bootstrap when possible since it's more documented than our burgeoning style scheme and simplified the layout with three blocks and no more total (since it doesn't really matter just how much is in the system when we are doing elections that change over time)
@createHernandez createHernandez moved this to Issue Approval in Sacramento Campaign Finance Oct 21, 2023
@createHernandez createHernandez moved this from Issue Approval to Todo in Sacramento Campaign Finance Oct 21, 2023
@createHernandez createHernandez moved this from Todo to In Progress in Sacramento Campaign Finance Oct 21, 2023
@jeremiak jeremiak moved this from In Progress to Wish List in Sacramento Campaign Finance Oct 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant