From 3df17eb59acac580c09bcff0a920aa55cf80ef2f Mon Sep 17 00:00:00 2001 From: sambensim Date: Sun, 7 Jul 2024 19:39:40 -0700 Subject: [PATCH 1/4] Fix broken links on contributor page readme - Fixed 6 links as outlined in Issue #444. - Additionally fixed a typo in the second to last paragraph (changed from "there are many more ways to contribute to p5.js through non-source code contribution than can be exhaustively listed here" to "there are many more ways to contribute to p5.js through non-source code contribution than ***cannot*** be exhaustively listed here") --- src/content/contributor-docs/en/README.mdx | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/src/content/contributor-docs/en/README.mdx b/src/content/contributor-docs/en/README.mdx index 56533c93d5..afec59d79d 100644 --- a/src/content/contributor-docs/en/README.mdx +++ b/src/content/contributor-docs/en/README.mdx @@ -18,7 +18,7 @@ This project follows the [all-contributors](https://github.com/kentcdodds/all-co @all-contributors please add @[your GitHub handle] for [your contribution type] ``` -You can find relevant contribution type [here](https://allcontributors.org/docs/en/emoji-key). Although we will usually automatically add you to the contributor list using the bot after merging your PR. The contributor docs are published on p5.js [website](https://p5js.org/contributor-docs/#/), and hosted on p5.js [GitHub repository](https://github.com/processing/p5.js/tree/main/contributor_docs). +You can find relevant contribution type [here](https://allcontributors.org/docs/en/emoji-key). Although we will usually automatically add you to the contributor list using the bot after merging your PR. The contributor docs are published on p5.js [website](https://p5js.org/contribute/#/), and hosted on p5.js [GitHub repository](https://github.com/processing/p5.js/tree/main/contributor_docs). # Before Contributing @@ -26,7 +26,7 @@ Contributing to p5.js should be a stress free experience and we welcome contribu First, please have a read through our [community statement](https://p5js.org/community/). -Next, we are currently prioritizing work that expands access (inclusion and accessibility) to p5.js! See [our access statement](./access/) for more details. +Next, we are currently prioritizing work that expands access (inclusion and accessibility) to p5.js! See [our access statement](https://p5js.org/contribute/access/) for more details. # Get Started @@ -37,7 +37,7 @@ Now you are ready to start contributing to p5.js! There are many ways to get sta Depending on what kind of contribution you are making to p5.js, please read on to the relevant section of this documentation. -## [Source code contribution](./contributor_guidelines/) +## [Source code contribution](https://p5js.org/contribute/contributor_guidelines/) For a typical contribution to the p5.js or p5.js-website repository, we will follow the following steps: @@ -49,7 +49,7 @@ For a typical contribution to the p5.js or p5.js-website repository, we will fol 6. Discuss 7. Approved and merged -Head over to [this link](./contributor_guidelines/) where you will be guided one step at a time on how to navigate the steps above, or you can also use the table of contents on the same page to skip to a relevant part you need a refresher on. +Head over to [this link](https://p5js.org/contribute/contributor_guidelines/) where you will be guided one step at a time on how to navigate the steps above, or you can also use the table of contents on the same page to skip to a relevant part you need a refresher on. Most of the time we will stick with this workflow quite strictly and, especially if you have contributed to other projects before, it may feel like there are too many hoops to jump through for what may be a simple contribution. However, the steps above are aimed to make it easy for you as a contributor and for stewards/maintainers to contribute meaningfully, while also making sure that you won't be spending time working on things that may not be accepted for various reasons. The steps above will help ensure that any proposals or fixes are adequately discussed and considered before any work begin, and often this will actually save you (and the steward/maintainer) time because the PR that would need additional fixing after review, or outright not accepted, would happen less often as a result. @@ -57,8 +57,8 @@ Most of the time we will stick with this workflow quite strictly and, especially ## Non-source code contribution -There are many more ways to contribute to p5.js through non-source code contribution than can be exhaustively listed here, some of the ways may also involve working with some of the p5.js repositories (such as adding examples, writing tutorials for the website, etc.). Depending on what the planned contribution is, we may be able to support you in different ways so do reach out to us via any channel available to you (email, social media, [Discourse forum](https://discourse.processing.org/c/p5js/10), Discord, etc). +There are many more ways to contribute to p5.js through non-source code contribution than cannot be exhaustively listed here, some of the ways may also involve working with some of the p5.js repositories (such as adding examples, writing tutorials for the website, etc.). Depending on what the planned contribution is, we may be able to support you in different ways so do reach out to us via any channel available to you (email, social media, [Discourse forum](https://discourse.processing.org/c/p5js/10), Discord, etc). -## [Stewards and maintainers](./steward_guidelines/) +## [Stewards and maintainers](https://p5js.org/contribute/steward_guidelines/) -For information related to area stewards or general maintenance of p5.js GitHub repository, please check out the [steward guidelines](./steward_guidelines/). +For information related to area stewards or general maintenance of p5.js GitHub repository, please check out the [steward guidelines](https://p5js.org/contribute/steward_guidelines/). From 9f7ea1556d48a0135c88c5bbf83927812741cf90 Mon Sep 17 00:00:00 2001 From: Qianqian Ye Date: Tue, 23 Jul 2024 17:50:55 -0700 Subject: [PATCH 2/4] Update src/content/contributor-docs/en/README.mdx Co-authored-by: Kenneth Lim --- src/content/contributor-docs/en/README.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/contributor-docs/en/README.mdx b/src/content/contributor-docs/en/README.mdx index afec59d79d..b949c1e4ee 100644 --- a/src/content/contributor-docs/en/README.mdx +++ b/src/content/contributor-docs/en/README.mdx @@ -18,7 +18,7 @@ This project follows the [all-contributors](https://github.com/kentcdodds/all-co @all-contributors please add @[your GitHub handle] for [your contribution type] ``` -You can find relevant contribution type [here](https://allcontributors.org/docs/en/emoji-key). Although we will usually automatically add you to the contributor list using the bot after merging your PR. The contributor docs are published on p5.js [website](https://p5js.org/contribute/#/), and hosted on p5.js [GitHub repository](https://github.com/processing/p5.js/tree/main/contributor_docs). +You can find relevant contribution type [here](https://allcontributors.org/docs/en/emoji-key). Although we will usually automatically add you to the contributor list using the bot after merging your PR. The contributor docs are published on p5.js [website](https://p5js.org/contribute/), and hosted on p5.js [GitHub repository](https://github.com/processing/p5.js/tree/main/contributor_docs). # Before Contributing From 8b9644d64a603f1f24d0b880bc388596da1e68e2 Mon Sep 17 00:00:00 2001 From: sambensim Date: Mon, 26 Aug 2024 10:38:14 -0700 Subject: [PATCH 3/4] Update README.mdx Removed mistaken typo --- src/content/contributor-docs/en/README.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/contributor-docs/en/README.mdx b/src/content/contributor-docs/en/README.mdx index b949c1e4ee..7c6e99778b 100644 --- a/src/content/contributor-docs/en/README.mdx +++ b/src/content/contributor-docs/en/README.mdx @@ -57,7 +57,7 @@ Most of the time we will stick with this workflow quite strictly and, especially ## Non-source code contribution -There are many more ways to contribute to p5.js through non-source code contribution than cannot be exhaustively listed here, some of the ways may also involve working with some of the p5.js repositories (such as adding examples, writing tutorials for the website, etc.). Depending on what the planned contribution is, we may be able to support you in different ways so do reach out to us via any channel available to you (email, social media, [Discourse forum](https://discourse.processing.org/c/p5js/10), Discord, etc). +There are many more ways to contribute to p5.js through non-source code contribution than can be exhaustively listed here, some of the ways may also involve working with some of the p5.js repositories (such as adding examples, writing tutorials for the website, etc.). Depending on what the planned contribution is, we may be able to support you in different ways so do reach out to us via any channel available to you (email, social media, [Discourse forum](https://discourse.processing.org/c/p5js/10), Discord, etc). ## [Stewards and maintainers](https://p5js.org/contribute/steward_guidelines/) From d7af43035c510d224b9d265c640bea19c64ade72 Mon Sep 17 00:00:00 2001 From: sambensim Date: Mon, 26 Aug 2024 10:41:46 -0700 Subject: [PATCH 4/4] Change README.mdx Phrasing Implemented @SableRaf 's rephrasing suggestion --- src/content/contributor-docs/en/README.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/contributor-docs/en/README.mdx b/src/content/contributor-docs/en/README.mdx index 7c6e99778b..3191281703 100644 --- a/src/content/contributor-docs/en/README.mdx +++ b/src/content/contributor-docs/en/README.mdx @@ -57,7 +57,7 @@ Most of the time we will stick with this workflow quite strictly and, especially ## Non-source code contribution -There are many more ways to contribute to p5.js through non-source code contribution than can be exhaustively listed here, some of the ways may also involve working with some of the p5.js repositories (such as adding examples, writing tutorials for the website, etc.). Depending on what the planned contribution is, we may be able to support you in different ways so do reach out to us via any channel available to you (email, social media, [Discourse forum](https://discourse.processing.org/c/p5js/10), Discord, etc). +There are many ways to contribute to p5.js beyond coding, such as adding examples, writing tutorials for the website and more. If you need help getting involved, contact us through the official [p5.js Discord](https://discord.gg/SHQ8dH25r9) or the [Processing Foundation forum](https://discourse.processing.org/c/p5js/10). ## [Stewards and maintainers](https://p5js.org/contribute/steward_guidelines/)