Write english version

[fernahh]

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

Tasks

• Configure Middleman I18n - @fernahh
• Add flags to indicate current language - @fernahh

Topics

• Introduction (pt-br) - @bukinoshita
• Accessibility (pt-br) - @bukinoshita
• Semantics (pt-br) - @lcandiago
• CSS (pt-br) - @idmarjr
• JavaScript (pt-br) - @rwillrich

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

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

Thanks!

[idmarjr]

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

[andersoonweb]

unfortunately, I am not good in English ⚠️

[fernahh]

Thanks, @idmarjr!

Sorry, @andersonweb. Thank you anyway.

[andersoonweb]

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

[rwillrich]

I'll translate the JavaScript part.

[fernahh]

Thanks, @rwillrich! 😄

[lcandiago]

I'll pick the Semantics page!

[fernahh]

Thanks, @lcandiago! o/

[idmarjr]

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

[fernahh]

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

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

[idmarjr]

Awesome! Thanks @fernahh

[bukinoshita]

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]

@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