I wanted to start working on a Turkish translation for a while and unfortunately I’ve just read “…we are focused to have translations only in the 5 additional languages as you see on the contributing doc…because of the operational logistics…”
I was wondering if it’s possible to add a feature giving user an option to use some custom external JSON API source to fetch translated version of challenge/guide data.
- Languages other than officially supported five can be maintained by their respective community with minimum operational overhead to FCC staff.
- When/if a language is to be officially supported, base translations would be ready.
- FCC will be accessible to more people. I admire FCC as a social project. It enables people in difficult situations from different professions to change their career path. In the specific case of Turkish translation, there are thousands of people dismissed from their jobs in Turkey currently, who aren’t allowed to leave country either Their situation gets even worse as the time passes. In my online discussion with some of those people, they were willing to self-study to switch their career so that they can work freelance, however resources in Turkish language is a bit limited. So, that’s my personal answer for “why the hurry?” question.
My initial thought was creating a gatsby repository to store markdown files and building static json files on there automatically with each commit (probably on Github Pages/Surge etc.). However, I’m not sure how to glue these to FCC site. I considered using Tampermonkey to hack around, yet I realized it would require too many hacks and wouldn’t function reliably still.
I went through FCC codebase and gatsby docs&tutorials. I decided accomplishing this all by myself is over my head as I don’t have much experience with most frameworks used in FCC development. TBH, I’m not sure if this is an applicable idea either.
What do you think? Is this feasible? If it is so, I can try implementing necessary parts given somebody point me in the right direction.