You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've always had a hard time getting English-speaking groups to use Hackfolder, and it seems to mostly be a reflection of the non-English language communicating "this is not for you".
I'd like to discuss how multilingual support (i18n) might be possible :)
Here are some thoughts -- 🔍 facts, feelings ❤️ and 💡 ideas -- related to this issue:
🔍 hackfoldr is totally client-side
🔍 Multilingual support on same page can hurt SEO.
🔍 The recommended tactic for best SEO is to use different routes for each language: example.com/en/:slug
🔍 No pages of hackholdr.org or subdomains are indexed in Google right now.
❤️ I feel that perhaps we could ignore SEO advice because we already aren't very SEO-compatible.
I've always had a hard time getting English-speaking groups to use Hackfolder, and it seems to mostly be a reflection of the non-English language communicating "this is not for you".
I'd like to discuss how multilingual support (i18n) might be possible :)
Here are some thoughts -- 🔍 facts, feelings ❤️ and 💡 ideas -- related to this issue:
example.com/en/:slug
i18next
is a popular multilingual JS framework.navigator
property to auto-detect language.The text was updated successfully, but these errors were encountered: