mirror of
https://github.com/EbookFoundation/free-programming-books.git
synced 2025-01-17 22:38:55 +01:00
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 7ee485bb3b1f16cd58aa4aacef3f8af19fb588ea 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>
35 lines
3.3 KiB
Markdown
35 lines
3.3 KiB
Markdown
# Primeros pasos
|
|
|
|
<div align="right" markdown="1">
|
|
|
|
*[Lea esto en otros idiomas](README.md#translations)*
|
|
|
|
</div>
|
|
|
|
**¡Sea bienvenido(a) a `Free-Programming-Books`!**
|
|
|
|
Siempre damos una calurosa bienvenida a los nuevos colaboradores; incluso a aquellos que realizan su primera Pull Request (PR) en GitHub. Si es usted uno de ellos, aquí van algunos recursos que quizás le pueden ayudar:
|
|
|
|
* [Acerca de las pull requests](https://docs.github.com/es/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)
|
|
* [Creando una pull request](https://docs.github.com/es/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)
|
|
* [GitHub Hola Mundo](https://docs.github.com/es/get-started/quickstart/hello-world)
|
|
* [YouTube - Tutorial GitHub para principiantes](https://www.youtube.com/watch?v=0fKg7e37bQE) *(en inglés)*
|
|
* [YouTube - Como bifurcar un repositorio GitHub y Enviar una Pull Request](https://www.youtube.com/watch?v=G1I3HF4YWEw) *(en inglés)*
|
|
* [YouTube - Curso intensivo de Markdown](https://www.youtube.com/watch?v=HUBNt18RFbo) *(en inglés)*
|
|
|
|
|
|
No se quede nunca con dudas, ni tenga miedo de hacer preguntas; todo buen colaborador que usted puede ver en el repositorio, comenzó en su día con una primera PR. Así que... ¿qué tal si se une a [nuestra extensa y creciente](https://www.apiseven.com/en/contributor-graph?chart=contributorOverTime&repo=ebookfoundation/free-programming-books) communidad?
|
|
|
|
<details align="center" markdown="1">
|
|
<summary>Click para detalle gráfico sobre dicho crecimiento (usuarios vs. tiempo)</summary>
|
|
|
|
[![EbookFoundation/free-programming-books's Contributor over time Graph](https://contributor-overtime-api.apiseven.com/contributors-svg?chart=contributorOverTime&repo=ebookfoundation/free-programming-books)](https://www.apiseven.com/en/contributor-graph?chart=contributorOverTime&repo=ebookfoundation/free-programming-books)
|
|
|
|
[![EbookFoundation/free-programming-books's Monthly Active Contributors graph](https://contributor-overtime-api.apiseven.com/contributors-svg?chart=contributorMonthlyActivity&repo=ebookfoundation/free-programming-books)](https://www.apiseven.com/en/contributor-graph?chart=contributorMonthlyActivity&repo=ebookfoundation/free-programming-books)
|
|
|
|
</details>
|
|
|
|
Incluso si ya tiene algo de experiencia como colaborador en otros proyectos de código abierto, hay algunas cosas que pueden hacerle dar un traspiés. Una vez enviada su PR, ***GitHub Actions* ejecutará un *linter*; el cuál se encarga a menudo de encontrar pequeños problemas con el espaciado, enlaces, sintaxis o la alfabetización**. Si al finalizar este proceso de integración continua se enciende la luz verde, es que todo está listo para su revisión; pero si no, haga clic en el enlace de "Detalles" proporcionado para averiguar qué fue exactamente lo que falló. Solucione dicho problema y agregue los cambios a su PR mediante un nuevo commit sobre la rama con la que inició la petición de cambios.
|
|
|
|
Por último, si no está del todo seguro de si el recurso que desea agregar es apropiado para `Free-Programming-Books`, lea detenidamente las pautas que puede encontrar en [CONTRIBUTING](CONTRIBUTING-es.md) (también [traducido a otros idiomas](README.md#translations)).
|