Brazilian Portuguese Translation about getbem.github.io HOT 11 CLOSED

@freitaseduardo of course! We still not have working plan, how to maintain translations, but some work was done in #73. I'm sure we figure something out.

from getbem.github.io.

Alright! Can we get the subdomain br.getbem.com?
I'm keeping the translated version on a fork until it's ready to ship, ok?

I noticed we have broken links in the licenses located on footer.js, is this something you can fix, or should i just remove the links?

Thanks!

from getbem.github.io.

@freitaseduardo

Alright! Can we get the subdomain br.getbem.com?

Sure.

I'm keeping the translated version on a fork until it's ready to ship, ok?

Let's start with this. Can yo send PR to branch br-lang afterwards?

I noticed we have broken links in the licenses located on footer.js, is this something you can fix, or should i just remove the links?

I forgot to add licenses 😊 - now it's fixed.

from getbem.github.io.

Let's start with this. Can yo send PR to branch br-lang afterwards?

I may need help with some git stuff, currently i forked the repo and made a new branch called br-lang. Let's say i'm ready to deploy, what should i do?

from getbem.github.io.

@freitaseduardo you should create PR into br-lang branch in this repo. Make sure you change subdomain to br.getbem.com here - https://github.com/getbem/getbem.com/blob/cn-lang/package.json#L37 and name of branch to br-lang here - https://github.com/getbem/getbem.com/blob/master/.travis.yml#L8

After PR is merged site should be available on br.getbem.com.

from getbem.github.io.

Perfect, thank you! 😁

from getbem.github.io.

@freitaseduardo any news on this? I'm also willing to help! (:

from getbem.github.io.

Hi @lucasbento 😃
I'm still on the mission, it's a bit slow but i'm making progress.
Maybe we can get in touch somewhere else to see how we can work together on this?
Thanks in advance 👊🏾

from getbem.github.io.

@freitaseduardo send me an email, it's available on my profile.

Hope we get started soon! :D

from getbem.github.io.

@floatdrop maybe we could organize it as babel-handbook. It appears to be a better approach than branches.

from getbem.github.io.

To be resolved in #287

from getbem.github.io.