From 0cb671943f060277a8b7a9d34698c7bb7db2bc53 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ulises=20Gasc=C3=B3n?= <ulisesgascongonzalez@gmail.com>
Date: Sat, 9 Sep 2023 14:45:53 +0200
Subject: [PATCH 01/16] fix: remove broken link

---
 _articles/de/how-to-contribute.md | 1 -
 _articles/el/how-to-contribute.md | 1 -
 _articles/es/how-to-contribute.md | 1 -
 _articles/fa/how-to-contribute.md | 1 -
 _articles/fr/how-to-contribute.md | 1 -
 _articles/how-to-contribute.md    | 1 -
 _articles/hu/how-to-contribute.md | 1 -
 _articles/id/how-to-contribute.md | 1 -
 _articles/ja/how-to-contribute.md | 1 -
 _articles/ko/how-to-contribute.md | 1 -
 _articles/ms/how-to-contribute.md | 1 -
 _articles/nl/how-to-contribute.md | 1 -
 _articles/pl/how-to-contribute.md | 1 -
 _articles/pt/how-to-contribute.md | 1 -
 _articles/ro/how-to-contribute.md | 1 -
 _articles/ru/how-to-contribute.md | 1 -
 _articles/tr/how-to-contribute.md | 1 -
 17 files changed, 17 deletions(-)

diff --git a/_articles/de/how-to-contribute.md b/_articles/de/how-to-contribute.md
index 07a283b05e7..6dc1ed10d40 100644
--- a/_articles/de/how-to-contribute.md
+++ b/_articles/de/how-to-contribute.md
@@ -231,7 +231,6 @@ Weiterhin, können Sie auf folgenden Seiten neue Projekte zum Beitragen entdecke
 * [CodeTriage](https://www.codetriage.com/)
 * [24 Pull Requests](https://24pullrequests.com/)
 * [Up For Grabs](https://up-for-grabs.net/)
-* [Contributor-ninja](https://contributor.ninja)
 * [First Contributions](https://firstcontributions.github.io)
 * [SourceSort](https://web.archive.org/web/20201111233803/https://www.sourcesort.com/)
 
diff --git a/_articles/el/how-to-contribute.md b/_articles/el/how-to-contribute.md
index e63ec27bd4c..e82a9d922c0 100644
--- a/_articles/el/how-to-contribute.md
+++ b/_articles/el/how-to-contribute.md
@@ -211,7 +211,6 @@ related:
 * [CodeTriage](https://www.codetriage.com/)
 * [24 Pull Requests](https://24pullrequests.com/)
 * [Up For Grabs](https://up-for-grabs.net/)
-* [Contributor-ninja](https://contributor.ninja)
 * [First Contributions](https://firstcontributions.github.io)
 * [SourceSort](https://web.archive.org/web/20201111233803/https://www.sourcesort.com/)
 
diff --git a/_articles/es/how-to-contribute.md b/_articles/es/how-to-contribute.md
index d6ba5d58d41..25c330fd3f7 100644
--- a/_articles/es/how-to-contribute.md
+++ b/_articles/es/how-to-contribute.md
@@ -207,7 +207,6 @@ Puedes tambi&eacute;n utilizar algunos de los siguientes recursos para ayudarte
 * [CodeTriage](https://www.codetriage.com/)
 * [24 Pull Requests](https://24pullrequests.com/)
 * [Up For Grabs](https://up-for-grabs.net/)
-* [Contributor-ninja](https://contributor.ninja)
 * [First Contributions](https://firstcontributions.github.io)
 * [SourceSort](https://web.archive.org/web/20201111233803/https://www.sourcesort.com/)
 
diff --git a/_articles/fa/how-to-contribute.md b/_articles/fa/how-to-contribute.md
index 6bfdf1ffb77..d78fbdb7c8b 100644
--- a/_articles/fa/how-to-contribute.md
+++ b/_articles/fa/how-to-contribute.md
@@ -214,7 +214,6 @@ related:
 * [CodeTriage](https://www.codetriage.com/)
 * [24 Pull Requests](https://24pullrequests.com/)
 * [Up For Grabs](https://up-for-grabs.net/)
-* [Contributor-ninja](https://contributor.ninja)
 * [First Contributions](https://firstcontributions.github.io)
 * [SourceSort](https://www.sourcesort.com/)
 
diff --git a/_articles/fr/how-to-contribute.md b/_articles/fr/how-to-contribute.md
index 79d9c25edf3..a9e2939e919 100644
--- a/_articles/fr/how-to-contribute.md
+++ b/_articles/fr/how-to-contribute.md
@@ -207,7 +207,6 @@ Vous pouvez également utiliser l'une des ressources suivantes pour vous aider 
 * [CodeTriage](https://www.codetriage.com/)
 * [24 Pull Requests](https://24pullrequests.com/)
 * [Up For Grabs](https://up-for-grabs.net/)
-* [Contributor-ninja](https://contributor.ninja)
 * [First Contributions](https://firstcontributions.github.io)
 * [SourceSort](https://web.archive.org/web/20201111233803/https://www.sourcesort.com/)
 
diff --git a/_articles/how-to-contribute.md b/_articles/how-to-contribute.md
index 17a04ad9821..bd1ae3d6a5a 100644
--- a/_articles/how-to-contribute.md
+++ b/_articles/how-to-contribute.md
@@ -213,7 +213,6 @@ You can also use one of the following resources to help you discover and contrib
 * [CodeTriage](https://www.codetriage.com/)
 * [24 Pull Requests](https://24pullrequests.com/)
 * [Up For Grabs](https://up-for-grabs.net/)
-* [Contributor-ninja](https://contributor.ninja)
 * [First Contributions](https://firstcontributions.github.io)
 * [SourceSort](https://web.archive.org/web/20201111233803/https://www.sourcesort.com/)
 
diff --git a/_articles/hu/how-to-contribute.md b/_articles/hu/how-to-contribute.md
index e7be38930e1..0b8e185cef2 100644
--- a/_articles/hu/how-to-contribute.md
+++ b/_articles/hu/how-to-contribute.md
@@ -209,7 +209,6 @@ Az alábbiakban találsz néhány oldalt, amelyek segítenek abban, hogy felfede
 * [CodeTriage](https://www.codetriage.com/)
 * [24 Pull Requests](https://24pullrequests.com/)
 * [Up For Grabs](https://up-for-grabs.net/)
-* [Contributor-ninja](https://contributor.ninja)
 * [First Contributions](https://firstcontributions.github.io)
 * [SourceSort](https://web.archive.org/web/20201111233803/https://www.sourcesort.com/)
 
diff --git a/_articles/id/how-to-contribute.md b/_articles/id/how-to-contribute.md
index b3d2cb2c763..6e25291ca99 100644
--- a/_articles/id/how-to-contribute.md
+++ b/_articles/id/how-to-contribute.md
@@ -207,7 +207,6 @@ Anda juga bisa menggunakan salah satu dari beberapa sumber daya berikut untuk me
 * [CodeTriage](https://www.codetriage.com/)
 * [24 Pull Requests](https://24pullrequests.com/)
 * [Up For Grabs](https://up-for-grabs.net/)
-* [Contributor-ninja](https://contributor.ninja)
 * [First Contributions](https://firstcontributions.github.io)
 * [SourceSort](https://web.archive.org/web/20201111233803/https://www.sourcesort.com/)
 
diff --git a/_articles/ja/how-to-contribute.md b/_articles/ja/how-to-contribute.md
index dfecc9a1157..3b95817e956 100644
--- a/_articles/ja/how-to-contribute.md
+++ b/_articles/ja/how-to-contribute.md
@@ -207,7 +207,6 @@ README を読んで、壊れたリンクやタイポを見つけるかもしれ
 * [CodeTriage](https://www.codetriage.com/)
 * [24 Pull Requests](https://24pullrequests.com/)
 * [Up For Grabs](https://up-for-grabs.net/)
-* [Contributor-ninja](https://contributor.ninja)
 * [First Contributions](https://firstcontributions.github.io)
 * [SourceSort](https://web.archive.org/web/20201111233803/https://www.sourcesort.com/)
 
diff --git a/_articles/ko/how-to-contribute.md b/_articles/ko/how-to-contribute.md
index 58ab9493e0c..d775b1dbb66 100644
--- a/_articles/ko/how-to-contribute.md
+++ b/_articles/ko/how-to-contribute.md
@@ -209,7 +209,6 @@ README를 스캔하여 깨진 링크나 오타를 찾을 수 있습니다. 또
 * [CodeTriage](https://www.codetriage.com/)
 * [24 Pull Requests](https://24pullrequests.com/)
 * [Up For Grabs](https://up-for-grabs.net/)
-* [Contributor-ninja](https://contributor.ninja)
 * [First Contributions](https://firstcontributions.github.io)
 * [SourceSort](https://web.archive.org/web/20201111233803/https://www.sourcesort.com/)
 
diff --git a/_articles/ms/how-to-contribute.md b/_articles/ms/how-to-contribute.md
index ea1bc6af630..285de934529 100644
--- a/_articles/ms/how-to-contribute.md
+++ b/_articles/ms/how-to-contribute.md
@@ -213,7 +213,6 @@ Anda juga boleh menggunakan salah satu sumber berikut untuk membantu anda menemu
 * [CodeTriage](https://www.codetriage.com/)
 * [24 Pull Requests](https://24pullrequests.com/)
 * [Up For Grabs](https://up-for-grabs.net/)
-* [Contributor-ninja](https://contributor.ninja)
 * [First Contributions](https://firstcontributions.github.io)
 * [SourceSort](https://web.archive.org/web/20201111233803/https://www.sourcesort.com/)
 
diff --git a/_articles/nl/how-to-contribute.md b/_articles/nl/how-to-contribute.md
index 4d561689084..cc07950d858 100644
--- a/_articles/nl/how-to-contribute.md
+++ b/_articles/nl/how-to-contribute.md
@@ -221,7 +221,6 @@ U kunt ook een van de volgende bronnen gebruiken om u te helpen bij het ontdekke
 * [CodeTriage](https://www.codetriage.com/)
 * [24 Pull Requests](https://24pullrequests.com/)
 * [Up For Grabs](https://up-for-grabs.net/)
-* [Contributor-ninja](https://contributor.ninja)
 * [First Contributions](https://firstcontributions.github.io)
 * [SourceSort](https://web.archive.org/web/20201111233803/https://www.sourcesort.com/)
 
diff --git a/_articles/pl/how-to-contribute.md b/_articles/pl/how-to-contribute.md
index 399cd50af2f..fd9c07fb69c 100644
--- a/_articles/pl/how-to-contribute.md
+++ b/_articles/pl/how-to-contribute.md
@@ -221,7 +221,6 @@ Możesz także skorzystać z jednego z następujących zasobów, aby pomóc ci o
 * [CodeTriage](https://www.codetriage.com/)
 * [24 Pull Requests](https://24pullrequests.com/)
 * [Up For Grabs](https://up-for-grabs.net/)
-* [Contributor-ninja](https://contributor.ninja)
 * [First Contributions](https://firstcontributions.github.io)
 * [SourceSort](https://web.archive.org/web/20201111233803/https://www.sourcesort.com/)
 
diff --git a/_articles/pt/how-to-contribute.md b/_articles/pt/how-to-contribute.md
index e6ee8a1c380..efad946eb21 100644
--- a/_articles/pt/how-to-contribute.md
+++ b/_articles/pt/how-to-contribute.md
@@ -207,7 +207,6 @@ Você também pode usar um dos seguintes recursos para ajudá-lo a descobrir e c
 * [CodeTriage](https://www.codetriage.com/)
 * [24 Pull Requests](https://24pullrequests.com/)
 * [Up For Grabs](https://up-for-grabs.net/)
-* [Contributor-ninja](https://contributor.ninja)
 * [First Contributions](https://firstcontributions.github.io)
 * [SourceSort](https://web.archive.org/web/20201111233803/https://www.sourcesort.com/)
 
diff --git a/_articles/ro/how-to-contribute.md b/_articles/ro/how-to-contribute.md
index ed1a435c010..3c2fcb95ebf 100644
--- a/_articles/ro/how-to-contribute.md
+++ b/_articles/ro/how-to-contribute.md
@@ -237,7 +237,6 @@ Poți de asemenea folosi una dintre următoarele resurse pentru a te ajuta să d
 * [CodeTriage](https://www.codetriage.com/)
 * [24 Pull Requests](https://24pullrequests.com/)
 * [Up For Grabs](https://up-for-grabs.net/)
-* [Contributor-ninja](https://contributor.ninja)
 * [First Contributions](https://firstcontributions.github.io)
 * [SourceSort](https://web.archive.org/web/20201111233803/https://www.sourcesort.com/)
 
diff --git a/_articles/ru/how-to-contribute.md b/_articles/ru/how-to-contribute.md
index ddef7a39287..581fb52138d 100644
--- a/_articles/ru/how-to-contribute.md
+++ b/_articles/ru/how-to-contribute.md
@@ -213,7 +213,6 @@ related:
 * [CodeTriage](https://www.codetriage.com/)
 * [24 Pull Requests](https://24pullrequests.com/)
 * [Up For Grabs](https://up-for-grabs.net/)
-* [Contributor-ninja](https://contributor.ninja)
 * [First Contributions](https://firstcontributions.github.io)
 * [SourceSort](https://web.archive.org/web/20201111233803/https://www.sourcesort.com/)
 
diff --git a/_articles/tr/how-to-contribute.md b/_articles/tr/how-to-contribute.md
index e97b7d07903..189f26e183e 100644
--- a/_articles/tr/how-to-contribute.md
+++ b/_articles/tr/how-to-contribute.md
@@ -213,7 +213,6 @@ Yeni projeleri keşfetmenize ve katkıda bulunmanıza yardımcı olmak için aş
 * [CodeTriage](https://www.codetriage.com/)
 * [24 Pull Requests](https://24pullrequests.com/)
 * [Up For Grabs](https://up-for-grabs.net/)
-* [Contributor-ninja](https://contributor.ninja)
 * [First Contributions](https://firstcontributions.github.io)
 * [SourceSort](https://web.archive.org/web/20201111233803/https://www.sourcesort.com/)
 

From efd6cc9b0ca545aa67f2250b43058f82ed2be6df Mon Sep 17 00:00:00 2001
From: Christine Belzie <shecoder30@gmail.com>
Date: Wed, 13 Sep 2023 20:56:28 -0400
Subject: [PATCH 02/16] fix: making revisions to how to contribute guide

---
 _articles/how-to-contribute.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/_articles/how-to-contribute.md b/_articles/how-to-contribute.md
index bd1ae3d6a5a..b3a7af95503 100644
--- a/_articles/how-to-contribute.md
+++ b/_articles/how-to-contribute.md
@@ -87,11 +87,11 @@ Even if you like to write code, other types of contributions are a great way to
 
 ### Do you like to write?
 
-* Write and improve the project's documentation
+* Write and improve the project's documentation, like [CBID2 did for OpenSauced's documentation](https://github.com/open-sauced/docs/pull/151)
 * Curate a folder of examples showing how the project is used
 * Start a newsletter for the project, or curate highlights from the mailing list
 * Write tutorials for the project, [like PyPA's contributors did](https://github.com/pypa/python-packaging-user-guide/issues/194)
-* Write a translation for the project's documentation
+* Write a translation for the project's documentation, like [frontendwizard did for the instructions for freeCodeCamp's CSS Flexbox challenge](https://github.com/freeCodeCamp/freeCodeCamp/pull/19077)
 
 <aside markdown="1" class="pquote">
   <img src="https://avatars.githubusercontent.com/kittens?s=180" class="pquote-avatar" alt="avatar">

From 92d72beb8d39c64fb7e6d24526633c007c0d855c Mon Sep 17 00:00:00 2001
From: Christine Belzie <shecoder30@gmail.com>
Date: Wed, 13 Sep 2023 21:16:51 -0400
Subject: [PATCH 03/16] feat: add another example of a contribution

---
 _articles/how-to-contribute.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/_articles/how-to-contribute.md b/_articles/how-to-contribute.md
index b3a7af95503..64bf474cf9e 100644
--- a/_articles/how-to-contribute.md
+++ b/_articles/how-to-contribute.md
@@ -87,11 +87,11 @@ Even if you like to write code, other types of contributions are a great way to
 
 ### Do you like to write?
 
-* Write and improve the project's documentation, like [CBID2 did for OpenSauced's documentation](https://github.com/open-sauced/docs/pull/151)
+* Write and improve the project's documentation, like [@CBID2 did for OpenSauced's documentation](https://github.com/open-sauced/docs/pull/151)
 * Curate a folder of examples showing how the project is used
-* Start a newsletter for the project, or curate highlights from the mailing list
+* Start a newsletter for the project, or curate highlights from the mailing list, like [@opensauced did for their product](https://news.opensauced.pizza/about/)
 * Write tutorials for the project, [like PyPA's contributors did](https://github.com/pypa/python-packaging-user-guide/issues/194)
-* Write a translation for the project's documentation, like [frontendwizard did for the instructions for freeCodeCamp's CSS Flexbox challenge](https://github.com/freeCodeCamp/freeCodeCamp/pull/19077)
+* Write a translation for the project's documentation, like [@frontendwizard did for the instructions for freeCodeCamp's CSS Flexbox challenge](https://github.com/freeCodeCamp/freeCodeCamp/pull/19077)
 
 <aside markdown="1" class="pquote">
   <img src="https://avatars.githubusercontent.com/kittens?s=180" class="pquote-avatar" alt="avatar">

From eb05f62a7efca3f0dcf7b8d75d6a1e08346a933e Mon Sep 17 00:00:00 2001
From: Christine Belzie <shecoder30@gmail.com>
Date: Wed, 13 Sep 2023 21:17:26 -0400
Subject: [PATCH 04/16] fix: revise sentence

---
 _articles/how-to-contribute.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_articles/how-to-contribute.md b/_articles/how-to-contribute.md
index 64bf474cf9e..6153b5f8e48 100644
--- a/_articles/how-to-contribute.md
+++ b/_articles/how-to-contribute.md
@@ -89,7 +89,7 @@ Even if you like to write code, other types of contributions are a great way to
 
 * Write and improve the project's documentation, like [@CBID2 did for OpenSauced's documentation](https://github.com/open-sauced/docs/pull/151)
 * Curate a folder of examples showing how the project is used
-* Start a newsletter for the project, or curate highlights from the mailing list, like [@opensauced did for their product](https://news.opensauced.pizza/about/)
+* Start a newsletter for the project, or curate highlights from the mailing list, [like @opensauced did for their product](https://news.opensauced.pizza/about/)
 * Write tutorials for the project, [like PyPA's contributors did](https://github.com/pypa/python-packaging-user-guide/issues/194)
 * Write a translation for the project's documentation, like [@frontendwizard did for the instructions for freeCodeCamp's CSS Flexbox challenge](https://github.com/freeCodeCamp/freeCodeCamp/pull/19077)
 

From 52a7af5888e360d60341502121b163496eaac821 Mon Sep 17 00:00:00 2001
From: Christine Belzie <shecoder30@gmail.com>
Date: Wed, 13 Sep 2023 21:18:46 -0400
Subject: [PATCH 05/16] fix: revise first sentence in Do you like to write
 subsection

---
 _articles/how-to-contribute.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_articles/how-to-contribute.md b/_articles/how-to-contribute.md
index 6153b5f8e48..acbe2e5554b 100644
--- a/_articles/how-to-contribute.md
+++ b/_articles/how-to-contribute.md
@@ -87,7 +87,7 @@ Even if you like to write code, other types of contributions are a great way to
 
 ### Do you like to write?
 
-* Write and improve the project's documentation, like [@CBID2 did for OpenSauced's documentation](https://github.com/open-sauced/docs/pull/151)
+* Write and improve the project's documentation,[like @CBID2 did for OpenSauced's documentation](https://github.com/open-sauced/docs/pull/151)
 * Curate a folder of examples showing how the project is used
 * Start a newsletter for the project, or curate highlights from the mailing list, [like @opensauced did for their product](https://news.opensauced.pizza/about/)
 * Write tutorials for the project, [like PyPA's contributors did](https://github.com/pypa/python-packaging-user-guide/issues/194)

From d0137865366974018754d3667c5061fd41432d82 Mon Sep 17 00:00:00 2001
From: Christine Belzie <shecoder30@gmail.com>
Date: Wed, 13 Sep 2023 21:21:06 -0400
Subject: [PATCH 06/16] fix: revise last point

---
 _articles/how-to-contribute.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_articles/how-to-contribute.md b/_articles/how-to-contribute.md
index acbe2e5554b..6fd16765e99 100644
--- a/_articles/how-to-contribute.md
+++ b/_articles/how-to-contribute.md
@@ -91,7 +91,7 @@ Even if you like to write code, other types of contributions are a great way to
 * Curate a folder of examples showing how the project is used
 * Start a newsletter for the project, or curate highlights from the mailing list, [like @opensauced did for their product](https://news.opensauced.pizza/about/)
 * Write tutorials for the project, [like PyPA's contributors did](https://github.com/pypa/python-packaging-user-guide/issues/194)
-* Write a translation for the project's documentation, like [@frontendwizard did for the instructions for freeCodeCamp's CSS Flexbox challenge](https://github.com/freeCodeCamp/freeCodeCamp/pull/19077)
+* Write a translation for the project's documentation, [like @frontendwizard did for the instructions for freeCodeCamp's CSS Flexbox challenge](https://github.com/freeCodeCamp/freeCodeCamp/pull/19077)
 
 <aside markdown="1" class="pquote">
   <img src="https://avatars.githubusercontent.com/kittens?s=180" class="pquote-avatar" alt="avatar">

From 3ba7e06e01f6ae9052c846cf40d76b99b9f25d13 Mon Sep 17 00:00:00 2001
From: Christine Belzie <shecoder30@gmail.com>
Date: Thu, 14 Sep 2023 21:09:50 -0400
Subject: [PATCH 07/16] feat: hyperlink names of quoted individuals

---
 _articles/how-to-contribute.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/_articles/how-to-contribute.md b/_articles/how-to-contribute.md
index 6fd16765e99..bff3bac5ab8 100644
--- a/_articles/how-to-contribute.md
+++ b/_articles/how-to-contribute.md
@@ -16,7 +16,7 @@ related:
   <img src="https://avatars.githubusercontent.com/errietta?s=180" class="pquote-avatar" alt="avatar">
   Working on \[freenode\] helped me earn many of the skills I later used for my studies in university and my actual job. I think working on open source projects helps me as much as it helps the project!
   <p markdown="1" class="pquote-credit">
-— @errietta, ["Why I love contributing to open source software"](https://www.errietta.me/blog/open-source/)
+— [@errietta](https://github.com/errietta), ["Why I love contributing to open source software"](https://www.errietta.me/blog/open-source/)
   </p>
 </aside>
 
@@ -66,7 +66,7 @@ A common misconception about contributing to open source is that you need to con
   <img src="https://avatars.githubusercontent.com/orta?s=180" class="pquote-avatar" alt="avatar">
   I’ve been renowned for my work on CocoaPods, but most people don’t know that I actually don’t do any real work on the CocoaPods tool itself. My time on the project is mostly spent doing things like documentation and working on branding.
   <p markdown="1" class="pquote-credit">
-— @orta, ["Moving to OSS by default"](https://academy.realm.io/posts/orta-therox-moving-to-oss-by-default/)
+— [@orta](https://github.com/orta), ["Moving to OSS by default"](https://academy.realm.io/posts/orta-therox-moving-to-oss-by-default/)
   </p>
 </aside>
 
@@ -502,7 +502,7 @@ If you make a polite bump and still nobody responds, it's possible that nobody w
 
 It's common that you'll be asked to make changes to your contribution, whether that's feedback on the scope of your idea, or changes to your code.
 
-When someone requests changes, be responsive. They've taken the time to review your contribution. Opening a PR and walking away is bad form. If you don't know how to make changes, research the problem, then ask for help if you need it.
+When someone requests changes, be responsive. They've taken the time to review your contribution. Opening a PR and walking away is bad form. If you don't know how to make changes, research the problem, then ask for help if you need it. A good example of this would be [the feedback that another contributor has given to @a-m-lamb on their pull request to Codecademy's Docs](https://github.com/Codecademy/docs/pull/3239#pullrequestreview-1628036286). 
 
 If you don't have time to work on the issue anymore (for example, if the conversation has been going on for months, and your circumstances have changed), let the maintainer know so they're not expecting a response. Someone else may be happy to take over.
 

From 7372ba7aea6457b67b826b083f06694553ee3dbf Mon Sep 17 00:00:00 2001
From: Christine Belzie <shecoder30@gmail.com>
Date: Sat, 16 Sep 2023 15:35:09 -0400
Subject: [PATCH 08/16] feat: add more examples

---
 _articles/how-to-contribute.md | 17 +++++++++--------
 1 file changed, 9 insertions(+), 8 deletions(-)

diff --git a/_articles/how-to-contribute.md b/_articles/how-to-contribute.md
index bff3bac5ab8..1534bdbe3c6 100644
--- a/_articles/how-to-contribute.md
+++ b/_articles/how-to-contribute.md
@@ -174,16 +174,16 @@ A project also has documentation. These files are usually listed in the top leve
 
 * **LICENSE:** By definition, every open source project must have an [open source license](https://choosealicense.com). If the project does not have a license, it is not open source.
 * **README:** The README is the instruction manual that welcomes new community members to the project. It explains why the project is useful and how to get started.
-* **CONTRIBUTING:** Whereas READMEs help people _use_ the project, contributing docs help people _contribute_ to the project. It explains what types of contributions are needed and how the process works. While not every project has a CONTRIBUTING file, its presence signals that this is a welcoming project to contribute to.
+* **CONTRIBUTING:** Whereas READMEs help people _use_ the project, contributing docs help people _contribute_ to the project. It explains what types of contributions are needed and how the process works. While not every project has a CONTRIBUTING file, its presence signals that this is a welcoming project to contribute to. A good example of an effective Contributing Guide would be the one from [Codecademy's Docs repository](https://www.codecademy.com/resources/docs/contribution-guide).  
 * **CODE_OF_CONDUCT:** The code of conduct sets ground rules for participants' behavior associated and helps to facilitate a friendly, welcoming environment. While not every project has a CODE_OF_CONDUCT file, its presence signals that this is a welcoming project to contribute to.
-* **Other documentation:** There might be additional documentation, such as tutorials, walkthroughs, or governance policies, especially on bigger projects.
+* **Other documentation:** There might be additional documentation, such as tutorials, walkthroughs, or governance policies, especially on bigger projects like [Astro Docs](https://docs.astro.build/en/contribute/#contributing-to-docs).
 
 Finally, open source projects use the following tools to organize discussion. Reading through the archives will give you a good picture of how the community thinks and works.
 
-* **Issue tracker:** Where people discuss issues related to the project.
-* **Pull requests:** Where people discuss and review changes that are in progress.
-* **Discussion forums or mailing lists:** Some projects may use these channels for conversational topics (for example, _"How do I..."_ or _"What do you think about..."_ instead of bug reports or feature requests). Others use the issue tracker for all conversations.
-* **Synchronous chat channel:** Some projects use chat channels (such as Slack or IRC) for casual conversation, collaboration, and quick exchanges.
+* **Issue tracker:** Where people discuss issues related to the project.  
+* **Pull requests:** Where people discuss and review changes that are in progress whether its to improve a contributor's line of code, grammar usage, use of images, etc. Some projects, such as [MDN Web Docs](https://github.com/mdn/content/blob/main/.github/workflows/markdown-lint-fix.yml), use certain GitHub Action flows to automate and quicken their code reviews.  
+* **Discussion forums or mailing lists:** Some projects may use these channels for conversational topics (for example, _"How do I..."_ or _"What do you think about..."_ instead of bug reports or feature requests). Others use the issue tracker for all conversations. A good example of this would be [CHAOSS' weekly Newsletter](https://chaoss.community/news/)
+* **Synchronous chat channel:** Some projects use chat channels (such as Slack or IRC) for casual conversation, collaboration, and quick exchanges. A good example of this would be [EddieHub's Discord community](http://discord.eddiehub.org/).
 
 ## Finding a project to contribute to
 
@@ -201,7 +201,7 @@ Open source isn't an exclusive club; it's made by people just like you. "Open so
 
 You might scan a README and find a broken link or a typo. Or you're a new user and you noticed something is broken, or an issue that you think should really be in the documentation. Instead of ignoring it and moving on, or asking someone else to fix it, see whether you can help out by pitching in. That's what open source is all about!
 
-> [28% of casual contributions](https://www.igor.pro.br/publica/papers/saner2016.pdf) to open source are documentation, such as a typo fix, reformatting, or writing a translation.
+> According to a study conducted by Igor Steinmacher and other Computer Science researchers,[28% of casual contributions](https://www.igor.pro.br/publica/papers/saner2016.pdf) to open source are documentation, such as  typo fixes, reformatting, or writing a translation.
 
 If you're looking for existing issues you can fix, every open source project has a `/contribute` page that highlights beginner-friendly issues you can start out with. Navigate to the main page of the repository on GitHub, and add `/contribute` at the end of the URL (for example [`https://github.com/facebook/react/contribute`](https://github.com/facebook/react/contribute)).
 
@@ -215,6 +215,7 @@ You can also use one of the following resources to help you discover and contrib
 * [Up For Grabs](https://up-for-grabs.net/)
 * [First Contributions](https://firstcontributions.github.io)
 * [SourceSort](https://web.archive.org/web/20201111233803/https://www.sourcesort.com/)
+* [OpenSauced](https://opensauced.pizza/)
 
 ### A checklist before you contribute
 
@@ -233,7 +234,7 @@ Here's a handy checklist to evaluate whether a project is good for new contribut
 
 **Project actively accepts contributions**
 
-Look at the commit activity on the main branch. On GitHub, you can see this information on a repository's homepage.
+Look at the commit activity on the main branch. On GitHub, you can see this information in the Insights tab of a repository's homepage, such as[Virtual-Coffee](https://github.com/Virtual-Coffee/virtualcoffee.io/pulse)
 
 <div class="clearfix mb-2">
   <input type="checkbox" id="cbox2" class="d-block float-left mt-1 mr-2" value="checkbox">

From 4f4e69630b998ff88fdd32f1534f1b4ce1bcee65 Mon Sep 17 00:00:00 2001
From: Christine Belzie <shecoder30@gmail.com>
Date: Fri, 22 Sep 2023 20:44:40 -0400
Subject: [PATCH 09/16] fix: revise sentences and add more examples

---
 _articles/how-to-contribute.md | 36 ++++++++++++++++------------------
 1 file changed, 17 insertions(+), 19 deletions(-)

diff --git a/_articles/how-to-contribute.md b/_articles/how-to-contribute.md
index 1534bdbe3c6..271b2b68381 100644
--- a/_articles/how-to-contribute.md
+++ b/_articles/how-to-contribute.md
@@ -431,11 +431,11 @@ Before you open an issue or pull request, or ask a question in chat, keep these
 
 Before doing anything, do a quick check to make sure your idea hasn't been discussed elsewhere. Skim the project's README, issues (open and closed), mailing list, and Stack Overflow. You don't have to spend hours going through everything, but a quick search for a few key terms goes a long way.
 
-If you can't find your idea elsewhere, you're ready to make a move. If the project is on GitHub, you'll likely communicate by opening an issue or pull request:
+If you can't find your idea elsewhere, you're ready to make a move. If the project is on GitHub, you'll likely communicate by doing the following:
 
-* **Issues** are like starting a conversation or discussion
-* **Pull requests** are for starting work on a solution
-* **For lightweight communication,** such as a clarifying or how-to question, try asking on Stack Overflow, IRC, Slack, or other chat channels, if the project has one
+* **Raising an Issue:** These are like starting a conversation or discussion
+* **Pull requests** are for starting work on a solution.
+* **Communication Channels:** If the project has a designated Discord, IRC, or Slack channel, consider starting a conversation or asking for clarification about your contribution.
 
 Before you open an issue or pull request, check the project's contributing docs (usually a file called CONTRIBUTING, or in the README), to see whether you need to include anything specific. For example, they may ask that you follow a template, or require that you use tests.
 
@@ -467,10 +467,10 @@ Tips for communicating on issues:
 
 You should usually open a pull request in the following situations:
 
-* Submit trivial fixes (for example, a typo, a broken link or an obvious error)
-* Start work on a contribution that was already asked for, or that you've already discussed, in an issue
+* Submit small fixes such a typo, a broken link or an obvious error.
+* Start work on a contribution that was already asked for, or that you've already discussed, in an issue.
 
-A pull request doesn't have to represent finished work. It's usually better to open a pull request early on, so others can watch or give feedback on your progress. Just open it as a "draft" or mark as a "WIP" (Work in Progress) in the subject line. You can always add more commits later.
+A pull request doesn't have to represent finished work. It's usually better to open a pull request early on, so others can watch or give feedback on your progress. Just open it as a "draft" or mark as a "WIP" (Work in Progress) in the subject line or "Notes to Reviewers" sections if provided (or you can just create your own. Like this: `**## Notes to Reviewer**`). You can always add more commits later.
 
 If the project is on GitHub, here's how to submit a pull request:
 
@@ -478,18 +478,16 @@ If the project is on GitHub, here's how to submit a pull request:
 * **[Create a branch](https://guides.github.com/introduction/flow/)** for your edits.
 * **Reference any relevant issues** or supporting documentation in your PR (for example, "Closes #37.")
 * **Include screenshots of the before and after** if your changes include differences in HTML/CSS. Drag and drop the images into the body of your pull request.
-* **Test your changes!** Run your changes against any existing tests if they exist and create new ones when needed. Whether tests exist or not, make sure your changes don't break the existing project.
+* **Test your changes!** Run your changes against any existing tests if they exist and create new ones when needed. It's important to make sure your changes don't break the existing project.
 * **Contribute in the style of the project** to the best of your abilities. This may mean using indents, semi-colons or comments differently than you would in your own repository, but makes it easier for the maintainer to merge, others to understand and maintain in the future.
 
 If this is your first pull request, check out [Make a Pull Request](http://makeapullrequest.com/), which @kentcdodds created as a walkthrough video tutorial. You can also practice making a pull request in the [First Contributions](https://github.com/Roshanjossey/first-contributions) repository, created by @Roshanjossey.
 
-## What happens after you submit a contribution
+## What happens after you submit your contribution
 
-You did it! Congratulations on becoming an open source contributor. We hope it's the first of many.
+Before we start celebrating, one of the following will happen after you submit your contribution:
 
-After you submit a contribution, one of the following will happen:
-
-### 😭 You don't get a response.
+### 😭 You don't get a response
 
 Hopefully you [checked the project for signs of activity](#a-checklist-before-you-contribute) before making a contribution. Even on an active project, however, it's possible that your contribution won't get a response.
 
@@ -497,24 +495,24 @@ If you haven't gotten a response in over a week, it's fair to politely respond i
 
 **Don't** reach out to that person privately; remember that public communication is vital to open source projects.
 
-If you make a polite bump and still nobody responds, it's possible that nobody will respond, ever. It's not a great feeling, but don't let that discourage you. It's happened to everyone! There are many possible reasons why you didn't get a response, including personal circumstances that may be out of your control. Try to find another project or way to contribute. If anything, this is a good reason not to invest too much time in making a contribution before other community members are engaged and responsive.
+If you give a polite reminder and still do not receive a response, it's possible that nobody will ever respond. It's not a great feeling, but don't let that discourage you! 😄 There are many possible reasons why you didn't get a response, including personal circumstances that may be out of your control. Try to find another project or way to contribute. If anything, this is a good reason not to invest too much time in making a contribution before other community members are engaged and responsive.
 
-### 🚧 Someone requests changes to your contribution.
+### 🚧 Someone requests changes to your contribution
 
 It's common that you'll be asked to make changes to your contribution, whether that's feedback on the scope of your idea, or changes to your code.
 
 When someone requests changes, be responsive. They've taken the time to review your contribution. Opening a PR and walking away is bad form. If you don't know how to make changes, research the problem, then ask for help if you need it. A good example of this would be [the feedback that another contributor has given to @a-m-lamb on their pull request to Codecademy's Docs](https://github.com/Codecademy/docs/pull/3239#pullrequestreview-1628036286). 
 
-If you don't have time to work on the issue anymore (for example, if the conversation has been going on for months, and your circumstances have changed), let the maintainer know so they're not expecting a response. Someone else may be happy to take over.
+If you don't have time to work on the issue anymore due to reasons such as the conversation has been going on for months, and your circumstances have changed or you're unable to find a solution, let the maintainer know so that they can open the issue for someone else, like [@RitaDee did for an issue at OpenSauced's app repository](https://github.com/open-sauced/app/issues/1656#issuecomment-1729353346).
 
-### 👎 Your contribution doesn't get accepted.
+### 👎 Your contribution doesn't get accepted
 
 Your contribution may or may not be accepted in the end. Hopefully you didn't put too much work into it already. If you're not sure why it wasn't accepted, it's perfectly reasonable to ask the maintainer for feedback and clarification. Ultimately, however, you'll need to respect that this is their decision. Don't argue or get hostile. You're always welcome to fork and work on your own version if you disagree!
 
-### 🎉 Your contribution gets accepted.
+### 🎉 Your contribution gets accepted
 
 Hooray! You've successfully made an open source contribution!
 
-## You did it!
+## You did it! 🎉
 
 Whether you just made your first open source contribution, or you're looking for new ways to contribute, we hope you're inspired to take action. Even if your contribution wasn't accepted, don't forget to say thanks when a maintainer put effort into helping you. Open source is made by people like you: one issue, pull request, comment, or high-five at a time.

From c04cd4a018b150e1498f525466c974a1c0aeff25 Mon Sep 17 00:00:00 2001
From: Christine Belzie <shecoder30@gmail.com>
Date: Fri, 22 Sep 2023 20:48:31 -0400
Subject: [PATCH 10/16] fix: revise formatting

---
 _articles/how-to-contribute.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_articles/how-to-contribute.md b/_articles/how-to-contribute.md
index 271b2b68381..22271a9d58e 100644
--- a/_articles/how-to-contribute.md
+++ b/_articles/how-to-contribute.md
@@ -493,7 +493,7 @@ Hopefully you [checked the project for signs of activity](#a-checklist-before-yo
 
 If you haven't gotten a response in over a week, it's fair to politely respond in that same thread, asking someone for a review. If you know the name of the right person to review your contribution, you can @-mention them in that thread.
 
-**Don't** reach out to that person privately; remember that public communication is vital to open source projects.
+**Don't reach out to that person privately**; remember that public communication is vital to open source projects.
 
 If you give a polite reminder and still do not receive a response, it's possible that nobody will ever respond. It's not a great feeling, but don't let that discourage you! 😄 There are many possible reasons why you didn't get a response, including personal circumstances that may be out of your control. Try to find another project or way to contribute. If anything, this is a good reason not to invest too much time in making a contribution before other community members are engaged and responsive.
 

From ce518ab1e77c262f55f6466d15b738248c944c81 Mon Sep 17 00:00:00 2001
From: Christine Belzie <105683440+CBID2@users.noreply.github.com>
Date: Sat, 23 Sep 2023 17:46:14 -0400
Subject: [PATCH 11/16] fix: remove trailing whitespace

Co-authored-by: Olsza <olsza@users.noreply.github.com>
---
 _articles/how-to-contribute.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_articles/how-to-contribute.md b/_articles/how-to-contribute.md
index 22271a9d58e..6e65ac964b9 100644
--- a/_articles/how-to-contribute.md
+++ b/_articles/how-to-contribute.md
@@ -501,7 +501,7 @@ If you give a polite reminder and still do not receive a response, it's possible
 
 It's common that you'll be asked to make changes to your contribution, whether that's feedback on the scope of your idea, or changes to your code.
 
-When someone requests changes, be responsive. They've taken the time to review your contribution. Opening a PR and walking away is bad form. If you don't know how to make changes, research the problem, then ask for help if you need it. A good example of this would be [the feedback that another contributor has given to @a-m-lamb on their pull request to Codecademy's Docs](https://github.com/Codecademy/docs/pull/3239#pullrequestreview-1628036286). 
+When someone requests changes, be responsive. They've taken the time to review your contribution. Opening a PR and walking away is bad form. If you don't know how to make changes, research the problem, then ask for help if you need it. A good example of this would be [the feedback that another contributor has given to @a-m-lamb on their pull request to Codecademy's Docs](https://github.com/Codecademy/docs/pull/3239#pullrequestreview-1628036286).
 
 If you don't have time to work on the issue anymore due to reasons such as the conversation has been going on for months, and your circumstances have changed or you're unable to find a solution, let the maintainer know so that they can open the issue for someone else, like [@RitaDee did for an issue at OpenSauced's app repository](https://github.com/open-sauced/app/issues/1656#issuecomment-1729353346).
 

From 5e61de612690d6938314a11a772461035fb38ab7 Mon Sep 17 00:00:00 2001
From: Christine Belzie <105683440+CBID2@users.noreply.github.com>
Date: Sat, 23 Sep 2023 17:46:55 -0400
Subject: [PATCH 12/16] fix: remove trailing whitespace part 2

Co-authored-by: Olsza <olsza@users.noreply.github.com>
---
 _articles/how-to-contribute.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_articles/how-to-contribute.md b/_articles/how-to-contribute.md
index 6e65ac964b9..cfbb476355c 100644
--- a/_articles/how-to-contribute.md
+++ b/_articles/how-to-contribute.md
@@ -180,7 +180,7 @@ A project also has documentation. These files are usually listed in the top leve
 
 Finally, open source projects use the following tools to organize discussion. Reading through the archives will give you a good picture of how the community thinks and works.
 
-* **Issue tracker:** Where people discuss issues related to the project.  
+* **Issue tracker:** Where people discuss issues related to the project.
 * **Pull requests:** Where people discuss and review changes that are in progress whether its to improve a contributor's line of code, grammar usage, use of images, etc. Some projects, such as [MDN Web Docs](https://github.com/mdn/content/blob/main/.github/workflows/markdown-lint-fix.yml), use certain GitHub Action flows to automate and quicken their code reviews.  
 * **Discussion forums or mailing lists:** Some projects may use these channels for conversational topics (for example, _"How do I..."_ or _"What do you think about..."_ instead of bug reports or feature requests). Others use the issue tracker for all conversations. A good example of this would be [CHAOSS' weekly Newsletter](https://chaoss.community/news/)
 * **Synchronous chat channel:** Some projects use chat channels (such as Slack or IRC) for casual conversation, collaboration, and quick exchanges. A good example of this would be [EddieHub's Discord community](http://discord.eddiehub.org/).

From fc98f6b37fa6012c8a64518b983b20637ec27667 Mon Sep 17 00:00:00 2001
From: Christine Belzie <105683440+CBID2@users.noreply.github.com>
Date: Sat, 23 Sep 2023 17:47:13 -0400
Subject: [PATCH 13/16] fix: remove trailing whitespace part 3

Co-authored-by: Olsza <olsza@users.noreply.github.com>
---
 _articles/how-to-contribute.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_articles/how-to-contribute.md b/_articles/how-to-contribute.md
index cfbb476355c..a46e9b53afa 100644
--- a/_articles/how-to-contribute.md
+++ b/_articles/how-to-contribute.md
@@ -174,7 +174,7 @@ A project also has documentation. These files are usually listed in the top leve
 
 * **LICENSE:** By definition, every open source project must have an [open source license](https://choosealicense.com). If the project does not have a license, it is not open source.
 * **README:** The README is the instruction manual that welcomes new community members to the project. It explains why the project is useful and how to get started.
-* **CONTRIBUTING:** Whereas READMEs help people _use_ the project, contributing docs help people _contribute_ to the project. It explains what types of contributions are needed and how the process works. While not every project has a CONTRIBUTING file, its presence signals that this is a welcoming project to contribute to. A good example of an effective Contributing Guide would be the one from [Codecademy's Docs repository](https://www.codecademy.com/resources/docs/contribution-guide).  
+* **CONTRIBUTING:** Whereas READMEs help people _use_ the project, contributing docs help people _contribute_ to the project. It explains what types of contributions are needed and how the process works. While not every project has a CONTRIBUTING file, its presence signals that this is a welcoming project to contribute to. A good example of an effective Contributing Guide would be the one from [Codecademy's Docs repository](https://www.codecademy.com/resources/docs/contribution-guide).
 * **CODE_OF_CONDUCT:** The code of conduct sets ground rules for participants' behavior associated and helps to facilitate a friendly, welcoming environment. While not every project has a CODE_OF_CONDUCT file, its presence signals that this is a welcoming project to contribute to.
 * **Other documentation:** There might be additional documentation, such as tutorials, walkthroughs, or governance policies, especially on bigger projects like [Astro Docs](https://docs.astro.build/en/contribute/#contributing-to-docs).
 

From 929218c2fb75ec967c521e735d4ff56f5194bcf8 Mon Sep 17 00:00:00 2001
From: Ulises Gascon <ulisesgascongonzalez@gmail.com>
Date: Wed, 27 Sep 2023 13:36:51 +0200
Subject: [PATCH 14/16] feat: add John F.  Kennedy image

Image generated from Wikimedia: https://upload.wikimedia.org/wikipedia/commons/c/c3/John_F._Kennedy%2C_White_House_color_photo_portrait.jpg
---
 assets/images/how-to-contribute/johnfkennedy.jpg | Bin 0 -> 6269 bytes
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 assets/images/how-to-contribute/johnfkennedy.jpg

diff --git a/assets/images/how-to-contribute/johnfkennedy.jpg b/assets/images/how-to-contribute/johnfkennedy.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..28e670fcc916855c6da58a126d7d875f1aef336e
GIT binary patch
literal 6269
zcmbW)XEYqly8!T27x5~w1W}{g=)DtG?`3s~-X(}m)F>OhCInGe_mb6@Bs$UU>d{Lq
z5pDHy^Zx($+<VUbbnkuU%zT;W%$eVr5A!_tbN8zN3QbiFRR9hS0D$vn0PgPqGRlS!
zC1X89X%=S(KDSqn&Mf{y{DLgpe!i|=&MX?5YAl-i5H%KmabcdPEZ%;$9<Hy0SmanF
z1xfA~0m=YEd;&rOd_qD3LLiWkh=hWKgqWBFL`F_Z@d!jq`v^osL(j;;O#hgTfrf_V
zDGM7X7Y{EF9W$RGAGaU}HxKtehu{E#KoTMnDiRVZZh9Je?*DV#e+5ty0T2KL9?la0
zE+q~gCC+^>fcX!S0Owx;_|L$>#rtz#AQ3UigFgvP6aZWtJUm={JOToI{6E=YfA#_R
zlmri1g_H=X3~Yf<yg|Z|X+=bA&l<i_8%`dwi`e-@5tGn7qNStf;N;@w;T07Vmync_
zR#t(is;O&e8X22FP0h?L>>V7PoLyYqd|&(d2LuKMN5{O4jf+o!rDtSjW#_#AkXu|*
zT2>CPsH|%IjA&|ZX>Duo?&<C89~c}Oo|;CXXJ+T-7uMD{Hn+BSe(qw9j!#apXXh7}
zSO2(h0C@jq{aODF`yVdKKQ3H+d^~*MKQ0{HfIkzD5}$xoi14A30npZ)>WOe95$IW3
zQNuT4HW9-^YCE4v5*l{VHIAcyX#bM^?_g2?FWG;={@b+xAjQM^^LTia00ltP(Ms=^
z#Uso3)TjE*s$?3YL7;~RioR1F;UKOB(ev?g_c2d)1>v2ddT6JZPH9SBH_Fd$i*F?5
zQD5`Al#Elpe}K!o(`tF%=fXqJTdSsS7AWM=-#yKL_ALvsPpo(qkbkP4IX+MoODk=;
z(TYE-ZU){mj*2xB3j}3)E=m{4W3$#DtyFl=LCYe31aCL^DR&rzyA6jhg1T6n?*XBv
zI&1DHFYD(wS6@<(E((l8Yu}gMXd|hmYS=Hs4*CyMWKki7L4kIjSK4Ic#>~TQ*Fht9
zPaPGy!7^*ANHKEKe!AF;S>SO6k|&TKX&)$(52vmQK<&L=5_mLGxB;X&Q=3w<X3Be2
zq8=$Mf-n_2N;k0#ku6BaGnSR9efPb!cCrx!HAQ@w9vW8)VjRZSMe8xQQ;%~QSTjcS
zKC4nA)iOpzeI(F$276ULjnda*;Bmo);nNnwxbe0+6@#+*yU?3!iPD)z%of;knCja|
zMo5rCe2IAbSun8PmmZ;gsojZL7qODrCpxV<N?IVkGR{pKZJGH%eiKP+T8P4C_gTw&
zOq*Ss<Z<2ulzo4h6nnOtSLcRuAlCb`9(4$PE$w*3UsGE~`W+1YYmW0y8RPz`xvjB<
ztQ;C38(IP@^A4c72b{VXs9E<qR<UO_Ib|;D*@0zvV03gOYV&!Cw{ot#3<gVt!j5q-
zxGk$cSe_@3k=Kj8nrrHP^Wyo3;EmRr=U}KroT%f7-yP*eM5q9M0_jWdZSNKt@0-1s
z-&Uyj5S>2md+&nA3+Crqxv+iSG!~(RvQ~qg!o-7vH(xBGwwKY4+@%r0&PAs;;hIm{
z4ApllZAuqC4}y1k^%&<a8mE?AkMT3476uB7m=J{|z4w4cg6$W>J+Z(iNazkl<IooY
zl;BS8o-FhFBpjnJ-NCwqS8tDTZPzs1=B3?zR`}Un8Ph8Z`?*hk0P(h<DI=@4r5^35
zCS+LMA?)Cj+-6llCw@Ax0j+6+4&5Fw@pOO4ef3EtDm_w@o5Bue!Hu^w<UvPq@J#Zw
zp7A2XebYvbQ&8Cy^?CP@GOCq&^$UY&Z}fTE>1fDYg738Rz>AExCcYz0RCiH{JXA@v
zg%%8Sr-{j*48unrBBz%uDJ^>)K0{>rgT%B<JDk-wQotn16#lhDKa6x13zr2im1=4s
z#!s4wB!5C2rOeHiGrbNB6n(_0Olv(Ivbw9%-5!e#ZH63!i<=?pktBo%F-%G|bklb3
zU~WD}o#`s7`PN!?WK&FPhh|zbIrt*r228T`BZ0j2n!YCOdm@XR4^6tG89IG8G|uFw
zCD)gqZdr{(K7B078UP?%Q7){(V&P?6{Yy>R$@q=IjkX(U^x_&vZRW&0WUGp?&igyA
zLYDk%i_&vvaHV-zuJ+QBN+Sgs>N0^bg#juW6ZC~GU1YY*RnL=c>|3MyW|%a6C11uj
zeumJ}hvZErBe^nqIDtDxhv?ZnP^_iDhZbH&?D?5I7JD8kcCAPGQy)Xam+5`NBU=(c
z*hST{l#)uejNMzoxp7!#nw=Wn%G-bBL&Q93b~|%(azT&29*qB<b;)cFGcc$eRR`mh
z2EzFSjot#(dAi>tjuhV(r^5gzNtVXyRC3_{JMfsmzFFm%RK3zsM3!+(z4(!!@a_T8
zujk65oq6*7F@*@70_)P7GZB^G#EExF{3>!va93sybgxs*cQTgD;N0WvfsQau3GpqK
zh^$M0Y>l;Ne6}FbBEp`!eTtmNHZ+@S>y)}=HHB1p-RS969^#eCokeMwFX|p3-QChr
zxfrYa1|zjXzS|P8hKzp~v%|s!egoDRCgN%dO*!)c|70e04faYadmsZ2oD%!}qjLyb
zeGhPKAQ|y2lF`E#5bMVj^a@J5jT21EGWxx_O_RnB4NP^sB)gGvu;mytkii?O*N%aJ
zB5IK?@CtxaS$nH}dYyk{B4wY`_G{$_w4d{=Nv7uVTb*o#0i!;-XBn;}!+L{cVLrhW
z?h|wY4*4Z=-c~K|Sk;<&g>loOf~RBawq~LX8f8n2ujM`#tEW0wGIc7|1s~XgOXDLd
zBnQg8E^=9N@T7=><og>U72^Q*C8ll(YoqgXb*zi*FruB5y70lu^~`TRW?p#QOa5%h
zJo`n*#8Pa)E9R+uUXdXtRg><`f=#<R?ryckJ1V4fN-UzI|N6wTqy<$mzGn$ARXDsO
zjQ%Fg;2{W|l2=$|qn^Yu*Yd5BVO1;x8N!qqc)Ig6|H7q#Y4YG$8XfkP{d}UHIa?UG
zv-Yd;=d7?rIRlTZX@eJ2@n`I4Qu$bI6iM!WS$saqW+3Z10R%E8Epme05MMx51<JzO
z1cW3yW%><nGx{Ex?QXX+=c_%AixaaHPn@X~d9uok7)Y`BjRZ|DK%Qz87U+qlXdm5z
z6VfEC1sdvFdRSxY6oJlZ=^+k+_ki^;n%#{^y2Y46KC^;qxaP=5XCQU4#HCJaWd7(S
zlrgCfN%T%^#2`vue}uq&_ng>QM2)I6qG(g1vR)+f3g$;O(PkH`Mlj!~Fy?k`p{l>7
zI3OkGo`?3Enf9ELG=OgA!$-#P1J0{*ZHoMYq$KE(YALN7&RdYwEhB5PSd0kGdZ|6#
zU`_R+3bG-c6CkpKKV>!KOYF-4+e_|r({jxY@mnf0V^R$<=`)KH<0B_M(#g8Zuh4Q2
zVA2np7wQr4a(mmEJ47Lr{Zvg+X7-C)gXO3_yH9_*s&RCiZ%RK>{*HP7m!ad^=5lqb
zQ?Y5?fXM<IF7m<4G-yaTzxY$7H-u`TWSQ9JR!epM0%H5On|MJs;G)UbaFl1k@h=fi
zO5wD^E+A(olQrPE7Go`XNGqhnV}K~>S(K_G7T<66td`M)&TOoJ%*1Z~fC)5o*p)m$
zC;qBHVTrmLR<!n>X|X5R1lcMKaRqs(J$nXl*CvT;14HbDxd}gZ=c(IA!j0_;6$xER
zMfHK)UE&FGCO4S6%5`*hzX_C%Z3YS9hXdo>{`PV@p3CvD>)eWqni=So#ug+Mcpibm
zdzW3~f{1IXi6s_hR+98}9=Bq^1(Uj-x*_x@JEaS93)0h&4&xOmu50v{veC`)SBoD&
zoaS+k_)ZOo8!xWg5^I5&Psw4bw%o(CR?Gt_dj@<)5@kn4$AK{zShj^t9DBbmr1t~M
z>dAo3hkF1ScIrY`N;FCLg=|Fl?gt-u9r@^}V^@M$byidB{L49<L8dHtNw;TFx}qTM
z;pmWLJ-_x<FzCm@C^^Ley7VoRs(zyS{NA3`^E2Ii-mvUro`)|*8(LWsh)zcXa6`;C
z3H@1^I#hLRuH}%&pI{Jw+v79)JF)x))NU3Bn?TPUZBv}RnVx@IWFm6T=yx)9x-5M$
zscN(0l<gi+tA}W4ixplR1BFvm9S^awWy|P#=a%`Cq$gP18S4+ixoC%WPU=OEm{LSD
zvYnt(*R6g2=Z%t?kFGn9%pdiPSha}NymppzsRRq36*~J7M!rgY5;Yl5(HM)9a3GTm
zE=93--UDLnT<cYYFyalhUtMBBl(R2e42(l%7~1PHI7+FAHiPW>QguNOHE4hDTC~I1
zr<xGwkJHUdn$v^GByPSEFdHQn);`qfBq`k>!UW&Nnz@{@-kqm^xOwY>XTtJ;K|Nlu
z3O90}SAS!sS+>&cK!dg7L|Jmc;v3rUqK0E`Q=cuA-fEV!>uIw>FR#*io=4c4?g&|l
zsHxCBfLN~Kjuk@lfPv~pV0PjNU*|N{M9%W7G`2iXHg=>LJwB{dA5Pzta1Y4IyuozA
z>s)8DMRdeQLZ~%lXNw!M>Yb@}9COwT+bb_h))sGP^?#^-jf1j8FH(=XzUWV{T#a&X
zK{?0n*`Vv5D5j2jvsGQ;_P5aub9}F|&oD<_BvpLzdpQ5F!oB!#bNj*Cm;@W%rSlc^
zuVSi5jN9&eODmNh(WJLBD7j>q*R=NUg*^&VAMZ45g(p(kp}EVdxz0KMW-S4DTqVx8
z6PYnp=uVdJS5f%OY&|e~gM2_Q_&EEj(74KT*sU)tq{1Q&F=^I+`G8G2@mAPfbwJa$
zOts}<X6G|AkQ8yjGS+L>Wcq2bOH4y;>pcLP5RC{XL-RiGd!jz!dKCi$_zZcdfBWgX
ztEcKtGt=lm6a1t1si%PM<AXRk`dYDB{gU5)<0mybcI%E^S~5w(XH=}b<z|{b04`ty
z9d)e-t+|Th)&SjrMZP{-*8z%BeEqfm0GlM)ox1dQZAT+azYW{x+n%^eC~IGkRqP}p
zD$82c1OKr!BwAqQPA3<{)pAl}U%BF5@N|kLseuToN*Sd}_PcZ7m57;+xWS?<O|=az
z`j_a-hpz3h<-Zt9jd;?cHWNQOGkv_v>Xc*mHqCgwANC^SkXK30u*v1XbE9C{IGYY6
zEzMAkHxa#Lylh@RIqKuoD*4+Am_$9&tpmsH@K>!<>u-6&El!y&I*}*Y@Cs;=#!t2I
znQlynHHWckA2OPP;Hss5w=)Teet+g&PHLaqeUudYgVW3Mv0m_j|26bYy<JOlJ=G~2
z^>X<^sBdZd#KpDc2R`j$wiAX~KKJbR9ff7V0lh0gMzFr?6Ru&Oz<Pxc)x;Dp^jobq
zraC6qZ;w1_1?00VTuEo;0znmYMvNFSCj9`fCN9Gz3{ozzp3ZtjIKMRH9`F&`v)in{
zH*=L-(vBI8rJs96j3IwMh5YkRWHYLo?hL<qd_{k-Uw602)c^9m&tI>Mlkz8jt+`e9
zK@Nhw3fF6;#|{>BsJgw$mo6dk##}A>w7CtH7w>u>m6iCnOxwDs=+K9b5WP@#NS3yz
z{cRI~yF@`<`U0r*@l94+dEKm$=#qC2{qX*236a0FxO0|M_PVm@RM@T+X^Y1_pipzT
z;O8^8l-Bin>yfm+{3Y%U>H!RWG2*7s=(L>5U%>6$rTWBEau>ECX06BGAD4a0%jj$-
zq7G$CmApcSJ<!e2N0MH0OR=AqBLqKw%un-K{!zf)69p=O-&{eNlkLF8-+1$jwQA$#
zo>g*P*6&!C7e{C?h_7ZO!2p{Xs9BDqpzLYrG{U6+_4NzKft#}o(v|XW7p4&E0N)%c
ze)Z#Xt_$BI3Fx8Uh(T$+U%B&nwvWX3<gM`buz~fz!o-R~H4e+`-SPk46Zb#X1Rn4^
zn&s;i;bX5HOnV<E{i%v)@ejdOUc%^upd+Nef-=->nFX_!nHWW;M7>=g(S9P}kCzJG
z{tdj*I3ka=r!ad?^Lgyexa11++K+Ht@WksC*bIH1y&1wih}@i2X7-3tZO@3_6zyhI
z={c5Ps)T+^GI&cQrjh-Z4Xb#Lv~JQw(LF%2W_}<0nDa90>#sDE;kRS2l^#tPm=OmA
zgK*);#qi9~!K+j?gTap`<9q`K2AXlM>rL91J34i7xq&A=N0@7q_&poB^%Xou`5BG0
zyWe7%LQ1iO*NYXs4#zq{%!#2|0luzJvRTzD^FE{Yd;0kwC=b>7X?$u+e@cZ|Z${9T
zqD!O<!Ccxcmep;f(d@aWdJpEykX$afjqg134K?^kt364<zn(Oi>e6^$HVBcHWMQe5
z&5j_+IX*u%a&6I6EvVVYwSoOtH(3c?<K*Z1tA&+C(@@kxW*Hr4iop~-@xaxJ=4$4Y
zzA0xOh1A+k7Wrs8ei)cx@b+2Fr;Wrkos3@TcLmP83iH%M`?+#iNzl2o@P~of1kofH
z`v9?TOPGFD1^EY9uBkR^RB3pZc}k^NS*bE-Q4l@A-_I_DguW5=eNnR%A>onvL$i`%
z$cw<=zese?GdkyY^7dzzSg<jZ<_27DukMgJ<|Wd!5{Dk)pC)*+;}tIlyjGh&shRTe
zS2Ju98)eg4TaLYoE#a>Z#+^5hn)k|!7z-!+Vihtwe#eI<Y+Co!Gt_@(r91WsyI7#0
z2*!jbTfBuwb<ut=bB$0re|P4<IH(YK>z#XXn+H2(V^XgufS9*u_}Jz~8Rf{MexY$Z
z8p_1Ei`J@CGV6n*a>RI{JpJ1<c{R(sC&V6gWl>5u1`S5m`8mC}_I3jm2-AjSVGMNx
zmKjBV!h(M4rBu6NaV4jnFE(*zCeLCvMC%Mqya&AgGkL*-F(W|Q;-+o*+<3b6I0_eM
z50<p1%1}}13XVFHwlZ!}iw^Zc(9E8d1)Ac|#$4px$rW@(-G0iu70_nh7rKRnUam*q
zC8H7f=y55C5+d2O=lk`!Ja*DOclJyk2Bqm6xir29IHP8OaS_V{%MD0_kh4*Z=8ppu
zbBL1i^2rpDhBUSuyAcihA<hy}cr6F%?la@cNGj)#D7oFmR@`)dp8Tx3gg<o%xKgpP
z=BRYydq&e_tP=C!b+qL-!)3^|v`V~c;I8#b+`)~E#J3Qwdg|_}#f7g>Hp<?j9%>wN
zJ9WlD?5@?oH%~UbqrxPeq>*zTX9m7ksTwW5t0@_;WU&~)Ah6648ohn4^V80r_Ihyd
zjy{m)q%Q#MEfo^RE8d%t7IhEUhkyC<@=exhb{>3wm)^nO;`IXpq%ukM&Co#@Moxa=
z@#DbSUnS~Ai3BQ25ubud#*dt8Z$FgFq+nByxn>!|Nv85S7%B7J#)3a@6)srz!l6gT
z;zC_^2&1pE4j;)UoR8{h?Jc^%XtMhC2iNO9oLR7I0i`P(vk`X<Ic>X$W*jjJxYT-{
zxdz7NPaB-m#0o>^rg|HcDTsN`Wy^RMe}I_u*<;0{A*?kIWWi?<8Pc6mS1RH8p?{i}
z*xMe{_M7m~3m7_#^{#2vhS%enyK}?NOHSWrs@vS*bsG$v*<vgIoe)=L?c?vUmPRCp
zH9_Y!jV{5Aq8q5cI9NrEmlnS2u*gmceR^HVje(=fGQI};r|*Y0A+tTg8vz5DQH|9w
zBa^8c+tTI0H$0pu+xN6Zi4Pt2jU(q0qxW@u_e78`iEqqi-BLU<Zbn09_p4pYI}e(I
zSjeloE7A^_eK^O~yEYS<duE!K`=Je3j*lzuh}dwx5@Bwqq=rm6)Gc^eUV5)^{*DRF
zne_LIi0+v1aSeH^JGxu&<Rb$bTb~E)NuN{JWLNL9PR@U61wKV23Fs_agbXcgjfF=N
z0=J)^7KOA&&noXc3@WEm+SBpM%K!fNhf$D$zP{m<fg+iO)f9<EY2S-cP|T$6nmtxN
zbrRwvvQwA>zvB%I-;2L<LX!76T&lvrt{y?(*PRP~2=OJOttKHnUj99{oj;3V(Mp}W
zD?Jd<1bKXc`;3B9NWzngoGmsxsag(GrcW<YPzDfJrWp0B62o<(ulIn0lB?O_djO(o
z|6GB>aM^SOIuqYe|A{^0Dwn&euv<GoHg(#v3<M=bX>u2*l5mR}XcK@i+~s(dwIBm^
I^85M!0Jy#cxBvhE

literal 0
HcmV?d00001


From 77cd2eeda3498fd344817373736f8b7883df909f Mon Sep 17 00:00:00 2001
From: Ulises Gascon <ulisesgascongonzalez@gmail.com>
Date: Wed, 27 Sep 2023 13:37:32 +0200
Subject: [PATCH 15/16] feat: transform John F. Kennedy reference into a quote
 component

---
 _articles/how-to-contribute.md | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/_articles/how-to-contribute.md b/_articles/how-to-contribute.md
index 17a04ad9821..f7536848f68 100644
--- a/_articles/how-to-contribute.md
+++ b/_articles/how-to-contribute.md
@@ -189,7 +189,15 @@ Finally, open source projects use the following tools to organize discussion. Re
 
 Now that you've figured out how open source projects work, it's time to find a project to contribute to!
 
-If you've never contributed to open source before, take some advice from U.S. President John F. Kennedy, who once said, _"Ask not what your country can do for you - ask what you can do for your country."_
+If you've never contributed to open source before, take some advice from U.S. President John F. Kennedy, who once said:, _"Ask not what your country can do for you - ask what you can do for your country."_
+
+<aside markdown="1" class="pquote">
+  <img src="/assets/images/how-to-contribute/johnfkennedy.jpg" class="pquote-avatar" alt="avatar">
+  Ask not what your country can do for you - ask what you can do for your country.
+  <p markdown="1" class="pquote-credit">
+— [_John f. Kennedy Library_](https://www.jfklibrary.org/learn/education/teachers/curricular-resources/ask-not-what-your-country-can-do-for-you)
+  </p>
+</aside>
 
 Contributing to open source happens at all levels, across projects. You don't need to overthink what exactly your first contribution will be, or how it will look.
 

From d8fcf5ca3b9ceeb5feee877f8c569959a0e8a9f3 Mon Sep 17 00:00:00 2001
From: Christine Belzie <105683440+CBID2@users.noreply.github.com>
Date: Thu, 28 Sep 2023 17:30:15 -0400
Subject: [PATCH 16/16] fix: revise typo

Co-authored-by: Zack Koppert <zkoppert@github.com>
---
 _articles/how-to-contribute.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_articles/how-to-contribute.md b/_articles/how-to-contribute.md
index f42d1d1c3e7..db837415d40 100644
--- a/_articles/how-to-contribute.md
+++ b/_articles/how-to-contribute.md
@@ -475,7 +475,7 @@ Tips for communicating on issues:
 
 You should usually open a pull request in the following situations:
 
-* Submit small fixes such a typo, a broken link or an obvious error.
+* Submit small fixes such as a typo, a broken link or an obvious error.
 * Start work on a contribution that was already asked for, or that you've already discussed, in an issue.
 
 A pull request doesn't have to represent finished work. It's usually better to open a pull request early on, so others can watch or give feedback on your progress. Just open it as a "draft" or mark as a "WIP" (Work in Progress) in the subject line or "Notes to Reviewers" sections if provided (or you can just create your own. Like this: `**## Notes to Reviewer**`). You can always add more commits later.