Freecodecamp: The APIs and Microservices Certification is now missing from curriculum and translations

[QuincyLarson]

The APIs and Microservices Certification is now missing from curriculum and translations:

We need to add this certification and its translations back in.

[Fordco]

Should this issue be closed since a solution was merged?

[RandellDawson]

@QuincyLarson @beaucarnes's PR (#24794) addressed part of this issue. It seems that the only thing left to do is make translations for each of the challenges? Can these be automatically translated like the other challenges were and put each set of the same language on a separate PR? Then we could close this issue. The other option is to close this issue and create a new issue concerning just the translations of these challenges.

[QuincyLarson]

@beaucarnes Were you able to run this certification through the translator?

If you haven't, of course, be very careful as it can get expensive quickly if you make a mistake.

Once these are translated, could you open a new PR adding these translations to the repo?

[beaucarnes]

This has not been done yet. I will start working on it.

[RandellDawson]

@beaucarnes Please make a separate PR for each set of language translations, so they are not all tied together. That way, the translators can focus on their own specific language PR and not hold up the others.

[moT01]

Do we want someone who can speak these languages to review them? Or is it safe for me to merge them? I glanced at them and they look good to me.

[RandellDawson]

@moT01 I believe we can go ahead an merge these translations now as long as there are no other earlier PRs for them (which there should not be).

FYI - I was given permission by Quincy to merge any non-English curriculum PRs as long as after reviewing, I did not see anything in appropriate (spam, referral links, etc.) after running the translations through Google translate. For these this is a non-issue, because they have only been run through Google translate. We still want to apply a high-level review because even though the translations will never be moved to production, they will still be present in the repo in case someone else forked the repo to continue working on what was started. We want to want spam or other such things in the repo.