cc/ @QuincyLarson
Our community has translated many of our challenges. If we don't have a translation for a challenge, it will be in English.
@QuincyLarson As per the discussion in #11469 please can you expand on the issue and what the required outcome would be
Hi @Bouncey yes - here is a more detailed explanation of what I envision happening:
1) Camper switches their language option to Spanish.
2) Camper visits a challenge which does not yet have a Spanish translation.
3) The camper sees the English version of that challenge. They also see at the top of the page a note:
"We have not yet translated this challenge into Spanish. Would you like to help us with this?" with a link to an open translation-based issue for that challenge block. Initially, we could just link to https://github.com/FreeCodeCamp/TranslationExpansion/issues
@BerkeleyTrue first we would need to decide how we plan to continue work on translations. Since we are expanding our curriculum, many of these issues will be out of date. Also, are we sure we want to have a separate repo for this considering that the code for these translations - as with curriculum expansion - will be in the freecodecamp/freecodecamp repo?
Instead of a long message i'd like to see a simple toast with a short message and a link as the call to action.
No translation found <link>info</link>
We've moved away from alerts and we don't want this message to be as intrusive as an alert as it will get tiring soon.
@QuincyLarson @BerkeleyTrue, is there a consensus? Personally I like the idea of a toast, the Alert IMO is very intrusive on the UI.
If we got the toast route, what about We have not yet translated this challenge into {user lang}. <link>More info</link>
Yes, we should stick to toasts where possible.
We don't need to mention the language.
We have not translated this challenge yet.
Just had a quick look over Toasts.jsx and it seems that the onClick event handler is tied into dispatch.
What is the best way of doing a target='_blank' link to the forum through actions? Would it have to be an epic?
We'll need to change the set up to accept links
Small change in the comment to make it more conversational?
We haven't translated this challenge yet.
@erictleung yes - I agree. That reads much better and is unambiguous. I agree with @BerkeleyTrue about wanting to keep these as short as possible, and I think your copy is a good happy medium.
@BerkeleyTrue instead of "info" we should put "Help us." and that can be a link to an article on the wiki explaining how.
PR refactored to use toasts :+1:
Most helpful comment
@erictleung yes - I agree. That reads much better and is unambiguous. I agree with @BerkeleyTrue about wanting to keep these as short as possible, and I think your copy is a good happy medium.
@BerkeleyTrue instead of "info" we should put "Help us." and that can be a link to an article on the wiki explaining how.