Different languages? about covidtrends

[edg2s]

I would recommend using i18n files rather than maintaining parallel branches. You could use a plugin such as https://kazupon.github.io/vue-i18n/, then keep all the messages in separate files i18n/en.json, i18n/fr.json etc.

[aatishb]

I would love to see translations! Thank you for suggesting this.

Currently I am imaging parallel branches of this website with the content translated, hosted on other peoples github accounts. We can create a translations page over here that links to sites with translations of this page in different languages, and then link to this translations page in the footer of the website. Or if there are fewer languages, we can just link directly in the footer.

Open to other thoughts on how to go about this.

[edg2s]

As an open source project you would even be able to get your translations done for free by the TranslateWiki community. This is the same site that does translations for Wikipedia, OpenStreetMap and others. However this might be a bit too much effort to setup and maintain.

[aatishb]

Interesting! Let's look into these options. cc @mustpax

[aatishb]

Labeling this as a question so we can gather input on how best to implement translations (and as a note to self to look more into the options above)

[CharsiBabu]

I second the opinion to added lib for handling translations.
Since the number of text entries would be relatively low, we could start with single js/json for all languages.

Not sure where would the language selector go. (header / footer / aside)