Skip to content
This repository has been archived by the owner on Apr 6, 2023. It is now read-only.

Translate README to pt-BR #55

Closed
alexandreramosdev opened this issue May 20, 2019 · 15 comments
Closed

Translate README to pt-BR #55

alexandreramosdev opened this issue May 20, 2019 · 15 comments

Comments

@alexandreramosdev
Copy link

alexandreramosdev commented May 20, 2019

Olá @diego3g, I would like to know if I can do the translation of the README to have an i18n improve! What do you think?

@diego3g
Copy link
Contributor

diego3g commented May 20, 2019

@alexandreramosdev Hi Alexandre, we want to keep all issues and contributions to this repo in english so can you please translate the original message here?

We have thoughts about i18n but nothing decided yet. Maybe we could create an docs website instead of using only Github because here we have really poor support for i18n as new markdowns would be created for every language.

@danilosales
Copy link

I suggest create others docs translated on folder translated, and in the README link to the doc translated.

@pellizzetti pellizzetti changed the title Translate pt-BR o readme Translate README to pt-BR May 22, 2019
@leonardobrito
Copy link
Contributor

For docs website, maybe we can use Docusaurus, they allows easy translation and localization and the site can be host by github pages. Sound good?

@diego3g
Copy link
Contributor

diego3g commented May 23, 2019

@leonardobrito Sounds great. We are using Docosaurus here: http://docs.rocketseat.dev

Repository: https://github.com/rocketseat/docs

@leonardobrito
Copy link
Contributor

Nice @diego3g , how to proceed with that? We have to send a pull request to https://github.com/rocketseat/docs or unform will have his own repository/website of docs. Or is too early to do that. If possible i will like to contribute with that chore.

@diego3g
Copy link
Contributor

diego3g commented May 23, 2019

@leonardobrito I think Unform can have it's own documentation

@leonardobrito
Copy link
Contributor

So the @Rocketseat will create another repository for his documentation? With a docusaurus project.

@diego3g
Copy link
Contributor

diego3g commented May 24, 2019

@leonardobrito Maybe will be better if we have a docs folder inside the same repo.

@alexandreramosdev
Copy link
Author

alexandreramosdev commented May 24, 2019

@diego3g The Rockeatseat have the styleguide for create website doc do unform! I like about think that create website with Docosaurus in folder docs inside this repor.

Structure similar
|── Root
{ Folders unform }
|── Docs
├── Dockerfile
├── README.md
├── docker-compose.yml
├── docs
│ ├── doc1.md
│ ├── doc2.md
│ ├── doc3.md
└── website
├── blog
│ ├── 2016-03-11-blog-post.md
│ ...

@leonardobrito
Copy link
Contributor

@alexandreramosdev i guess a folder named docs or documentation, like the example folder will be great. What do you folks think?

@MiguelMachado-dev
Copy link

I have seen others repositories and docs folder would be great.
Inside that folder we can create a readme for each language

@leonardobrito
Copy link
Contributor

If is okay for all, i can publish an PR with it soon, the folder docs with Docusaurus project and the initial documentation.

@diego3g
Copy link
Contributor

diego3g commented Jun 5, 2019

This issue is being treated in #80.

@brendonguedes
Copy link

brendonguedes commented Aug 18, 2019

Google itself, I believe other browsers also allow the user to add an extension for automatic translation of other languages, such as English to Brazilian Portuguese.

@jpedroschmitz
Copy link
Member

Hey guys, we have decided now to keep our efforts on the Unform API, so the docs will keep in English. As the project grows, we are going to focus on i18n. As we finish it we will create new docs where you all can contribute (in any language). We really appreciate your efforts in making this happen 💜

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

No branches or pull requests

7 participants