Open wetneb opened 4 years ago
Possible solution: https://www.sylvaindurand.org/making-jekyll-multilingual/
We would probably not get automatic language selection from this, but it would be a good start.
I think a better solution now instead of Jekyll would be using Docusaurus 2 (essentially a React app) since we could easily get translations from the community now like CrowdIn, integrated search, and we have familiarity with it being used for our Docs. If customization is needed we have the ability to use React, MDX, etc. available in it at any point and a vast community experienced in those.
Later Algolia Search could be tweaked for searching across the language pages with proper configuration: https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/ https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/how-to/multilingual-search/
It would definitely make sense to use Docusaurus since we are already using it for the docs and Docusaurus itself is designed to build both an official website and the accompanying docs from the same instance.
openrefine.org should be translated in various languages, just like the software is.
This might require moving out of GitHub pages if we want to auto-detect the language from browser settings.