-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write english version #7
Comments
Gimme the CSS! |
unfortunately, I am not good in English |
Thanks, @idmarjr! Sorry, @andersonweb. Thank you anyway. |
I'll accompanying perhaps not roll some help: P @fernahh ! |
I'll translate the JavaScript part. |
Thanks, @rwillrich! 😄 |
I'll pick the Semantics page! |
Thanks, @lcandiago! o/ |
@fernahh Anny news about Middleman I18? |
@idmarjr I created a branch for this work. Send the PR for it, ok? |
Awesome! Thanks @fernahh |
I'll be doing the How do I suppose to do that? Should I override the Portuguese version or create a new file |
@bukinoshita In my fork I copy/past the pt-br version to the same file in i18n branch and make the first commit of it (idmarjr@9e26bcb). I use it as reference to translate. |
@idmarjr ty |
😄 |
The flags indicate the current language and offers link to inverse language. - Add pry for Ruby Debug; - Create methods to list links; - Create logic with JavaScript to style of flags.
Look guys! I created it with CSS Filters! 😍 |
@fernahh ohh, cool! 😎 |
Just some thoughts ...Are we sticking with Also, instead of using |
@bukinoshita I believe that there are other paths to follow. I also think that this is not the absolute truth about where to start. Right? :) |
have something left to be translated? |
@lorbicki I started to translate the JavaScript session but haven't had much time. You can see what is still missing here #8. |
🇬🇧 Hey guys. I created this issue to plan the english version of Front-end Path. 🇬🇧
Tasks
Topics
If each of you pick a topic, this process would be amazing!
(cc @rwillrich @Jesm @idmarjr @andersonweb @lcandiago)
Thanks!
The text was updated successfully, but these errors were encountered: