free-programming-books/docs/HOWTO-vi.md
David Ordás 28ec79103b
docs(howto): Homogenize HowTo's format across translated files ()
* Homogenize HowTo's

- Add H1 header
- `Read this` ... right alignmements
- Split a bit first paragraph to highlight welcome.
- Introduce Pull Request acronym.
- trademarks / typos: GitHub, YouTube, Pull Request
- Update GitHub links urls. `help`/`guides` subdomain was moved to `docs` so now a 301 Redirect is skipped.
- Details block added, with center align. When clicked, the contributor graphs is toggled.
- Some bolds to highlight common resources formating issues (like in CONTRIBUTING)
- Repo name in monospace font
- Re-worded last part of 4th paragraph to explain that no new PR is needed to open if there are linter errors or changes are requested. Now it's more clear, I thought.

Via EbookFoundation/free-programming-books#6590

* Rewording to be more meaningful

* Add H1 header + `Read this` ... aligned to right

Via EbookFoundation/free-programming-books#6590

* remove trailing spaces

* Split a bit first paragraph to highlight welcome.

Via EbookFoundation/free-programming-books#6590

* homogenize `1-2` newlines amount between paragraphs

* Update Github documentation links list

- Update GitHub links urls. `help`/`guides` subdomain was moved to `docs` so now a 301 Redirect is skipped.
- Remove flag emojis from link, perhaps use text in notes format to give accesibility locale context

Via EbookFoundation/free-programming-books#6590

* GitHub trademark typos

* YouTube trademark typos

* `Welcome to fpb!` in bold style

* Repo name backticked in monospace font

(non-translatable)

* reword es-en graph summary

* Add a centered details block with graphs about contributions (users vs. time)

Detail blocks are toggleable sections in GitHub

Provided graphs by apiseven:
- Contributor over time Graph
- Monthly Active Contributors graph

* GitHub trademark typos

* Fix pull request typos and introduce it acronym

* Update Github documentation links list

- Update GitHub links urls. `help`/`guides` subdomain was moved to `docs` so now a 301 Redirect is skipped.
- Remove flag emojis from link, perhaps use text in notes format to give accesibility locale context

The forgot rest addressed on 7ee485bb3b commit
Via 

* Some bolds to highlight common resources formating issues (like in CONTRIBUTING)

* Fix typos suggested by AhmedElTabarani

Co-authored-by: أحمد الطبراني <eltabaraniahmed@gmail.com>

* Add paragrah from . Need language translation

* New strings translated to `it` Italian

Co-authored-by: ImVector <59611597+LuigiImVector@users.noreply.github.com>

* use languages not countries. `in Egyptian Arabic`

* use languages not countries. `in Algerian Arabic`

* remove notes from details block containing graphs about contributions (users vs. time)

* Fix spanish typos

Co-authored-by: Wonjang Son <sondaniel.88@gmail.com>

* Fix korean typos

Co-authored-by: Wonjang Son <sondaniel.88@gmail.com>

* New strings translated to `ar` Arabic

Co-authored-by: أحمد الطبراني <eltabaraniahmed@gmail.com>

* New strings translated to `fr` French

Co-authored-by: Loic Beylot <loic.beylot@gmail.com>

Co-authored-by: أحمد الطبراني <eltabaraniahmed@gmail.com>
Co-authored-by: ImVector <59611597+LuigiImVector@users.noreply.github.com>
Co-authored-by: Wonjang Son <sondaniel.88@gmail.com>
Co-authored-by: Loic Beylot <loic.beylot@gmail.com>
2022-02-28 11:04:55 -05:00

3.2 KiB

How-To at a glance

Chào mừng tới Free-Programming-Books!

Chúng tôi chào đón những người đóng góp mới, kể cả khi những người đóng góp lần đầu thực hiện trên GitHub. Nếu bạn là một trong số họ, đây là một số nguồn có thể giúp:

Đừng do dự khi đặt câu hỏi; mọi người đóng góp đã bắt đầu với Pull Request (PR) đầu tiên. Bạn có thể là người tiếp theo! So... why not join our large, growing community.

Click to see the growth users vs. time graphs.

EbookFoundation/free-programming-books's Contributor over time Graph

EbookFoundation/free-programming-books's Monthly Active Contributors graph

Nếu bạn là một người đóng góp có kinh nghiệm với mã nguồn mở, có nhiều điều bạn có thể phát triển. Một khi bạn gửi PR của bạn, GitHub Actions sẽ kiểm tra tra bằng cách sử dụng linter, thường tìm thấy những lỗi nhỏ với khoảng trống hoặc chính tả. Nếu bạn đặt tích xanh, mọi thứ đã sẵn sàng cho việc đánh giá, nếu không, nhấn vào "Details" dưới phần kiểm tra lỗi để tìm kiếm sai sót. Sửa vấn đề và thêm một commit tới PR của bạn.

Cuối cùng, nếu bạn không chắc rằng nguồn bạn muốn thêm phù hợp cho Free-Programming-Books, đọc qua hướng dẫn trong Đóng Góp. (translations)