28ec79103b
* 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 EbookFoundation/free-programming-books#6590
* 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 #5351. 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>
3.0 KiB
How-To at a glance
Selamat datang di Free-Programming-Books!
Kami menyambut kontributor baru; bahkan untuk mereka yang membuat Pull Request (PR) pertama kali di GitHub. Jika Anda adalah salah satunya, berikut adalah beberapa sumber yang mungkin bisa membantu:
- Tentang Pull Requests (Dalam Bahasa Inggris)
- Membuat sebuah pull request (Dalam Bahasa Inggris)
- GitHub Hello World (Dalam Bahasa Inggris)
- YouTube - GitHub Tutorial Untuk Pemula (Dalam Bahasa Inggris)
- YouTube - Cara Melakukan Fork Pada GitHub Repositori dan Mengirimkan Sebuah Pull Request (Dalam Bahasa Inggris)
- YouTube - Kursus Kilat Markdown (Dalam Bahasa Inggris)
Jangan ragu untuk bertanya; setiap kontributor memulainya dengan PR yang pertama. Anda bisa menjadi yang keseribu! So... why not join our large, growing community.
Click to see the growth users vs. time graphs.
Bahkan jika Anda seorang kontributor open source yang berpengalaman, ada hal-hal yang mungkin membuat Anda bingung. Setelah Anda mengirimkan PR Anda, GitHub Actions akan menjalankan linter, dan sering sekali menemukan sedikit masalah dengan spasi atau abjad. Jika Anda mendapatkan tombol hijau, semuanya siap untuk ditinjau, tetapi jika tidak, klik "Detail" di bawah centang yang gagal untuk mengetahui apa yang tidak disukai linter. Perbaiki masalah dan tambahkan commit ke PR Anda.
Terakhir, jika Anda tidak yakin bahwa sumber daya yang ingin Anda tambahkan sesuai untuk Free-Programming-Books, bacalah panduan di BERKONTRIBUSI. (translations)