Skip to content
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

Open
4 of 7 tasks
fernahh opened this issue Aug 30, 2015 · 21 comments
Open
4 of 7 tasks

Write english version #7

fernahh opened this issue Aug 30, 2015 · 21 comments

Comments

@fernahh
Copy link
Owner

fernahh commented Aug 30, 2015

🇬🇧 Hey guys. I created this issue to plan the english version of Front-end Path. 🇬🇧

english

Tasks

Topics

If each of you pick a topic, this process would be amazing!

(cc @rwillrich @Jesm @idmarjr @andersonweb @lcandiago)

Thanks!

@fernahh fernahh changed the title 🇬🇧 Write english version 🇬🇧 Write english version Aug 30, 2015
@idmarjr
Copy link

idmarjr commented Aug 31, 2015

Gimme the CSS!
I'm going start it on Tuesday. 😬

@andersoonweb
Copy link
Contributor

unfortunately, I am not good in English ⚠️

@fernahh
Copy link
Owner Author

fernahh commented Aug 31, 2015

Thanks, @idmarjr!

Sorry, @andersonweb. Thank you anyway.

@andersoonweb
Copy link
Contributor

I'll accompanying perhaps not roll some help: P @fernahh !

@rwillrich
Copy link
Contributor

I'll translate the JavaScript part.

@fernahh
Copy link
Owner Author

fernahh commented Aug 31, 2015

Thanks, @rwillrich! 😄

@lcandiago
Copy link

I'll pick the Semantics page!

@fernahh
Copy link
Owner Author

fernahh commented Sep 1, 2015

Thanks, @lcandiago! o/

@idmarjr
Copy link

idmarjr commented Sep 2, 2015

@fernahh Anny news about Middleman I18?
I would like to commit it directly to the final structure if it possible. 😅

@fernahh
Copy link
Owner Author

fernahh commented Sep 2, 2015

@idmarjr I created a branch for this work. Send the PR for it, ok?

https://github.com/fernahh/frontendpath/tree/I18n

@idmarjr
Copy link

idmarjr commented Sep 2, 2015

Awesome! Thanks @fernahh

@bukinoshita
Copy link

I'll be doing the Introduction and Accessibility.

How do I suppose to do that? Should I override the Portuguese version or create a new file index-en.html.erb

@idmarjr
Copy link

idmarjr commented Oct 15, 2015

@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.
Beside that I'm trying to make one commit to each section or topic of the content, this way is easy to find a specific translation if needed. Ex: idmarjr@f77bb23

@bukinoshita
Copy link

@idmarjr ty

@idmarjr
Copy link

idmarjr commented Oct 16, 2015

😄

fernahh added a commit that referenced this issue Oct 17, 2015
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.
@fernahh
Copy link
Owner Author

fernahh commented Oct 17, 2015

Look guys! I created it with CSS Filters! 😍

I18n Flags

@bukinoshita
Copy link

@fernahh ohh, cool! 😎

@bukinoshita
Copy link

Just some thoughts ...

Are we sticking with A correct path to Front-end Development or should we change to The right path to Front-end Development?

Also, instead of using the-accessibility.html.md, we should use accessibility.html.md. Get rid off the the.

@fernahh
Copy link
Owner Author

fernahh commented Oct 23, 2015

@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? :)

@lhonardo
Copy link

have something left to be translated?

@rwillrich
Copy link
Contributor

@lorbicki I started to translate the JavaScript session but haven't had much time. You can see what is still missing here #8.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants