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>
2.8 KiB
How-To at a glance
Maligayang pagdating sa Free-Programming-Books!
Tinatanggap namin ang mga bagong kontribyutor; kahit na ang mga gumagawa ng kanilang pinakaunang Pull Request (PR) sa GitHub. Kung isa ka sa mga iyon, narito ang ilang mapagkukunan na maaaring makatulong:
- About Pull Requests (in english)
- Creating a pull request (in english)
- GitHub Hello World (in english)
- YouTube - GitHub Tutorial For Beginners (in english)
- YouTube - How To Fork A GitHub Repo and Submit A Pull Request (in english)
- YouTube - Markdown Crash Course (in english)
Huwag mag-atubiling magtanong; bawat kontribyutor ay nagsimula sa isang unang PR. Maaaring ikaw ang aming ika-libo!
Click to see the growth users vs. time graphs.
Kahit na isa kang makaranasang open source na nag-ambag, may mga bagay na maaaring magalit sa iyo. Sa sandaling naisumite mo na ang iyong PR, ang GitHub Actions ay magpapatakbo ng isang linter, kadalasang nakakahanap ng maliliit na isyu sa spacing o alphabetization. Kung nakakuha ka ng berdeng button, handa na ang lahat para sa pagsusuri, ngunit kung hindi, i-click ang "Mga Detalye" sa ilalim ng tseke na nabigong malaman kung ano ang hindi nagustuhan ng linter. Ayusin ang problema at magdagdag ng commit sa iyong PR.
Panghuli, kung hindi ka sigurado na ang resource na gusto mong idagdag ay angkop para sa Free-Programming-Books, basahin ang mga alituntunin sa CONTRIBUTING. (translations)