Pull updates from p5.js repo contributor_docs folder

Author: Qianqianye

src/content/contributor-docs/en/contributing_to_the_p5.js_reference.mdx renamed to src/content/contributor-docs/en/contributing_to_the_p5js_reference.mdx

@@ -37,7 +37,6 @@ This is a relatively long and comprehensive document but we will try to signpost
     * [Source code](#source-code)
     * [Unit tests](#unit-tests)
     * [Inline documentation](#inline-documentation)
-    * [Internationalization](https://github.com/processing/p5.js/blob/main/contributor_docs/contributor_guidelines.md#internationalization)
     * [Accessibility](#accessibility)
   * [Code standard](#code-standard)
   * [Software Design principles](#software-design-principles)
@@ -154,7 +153,7 @@ For feature enhancement proposals to be accepted they must be approved by at lea
 
 This template should be used if you wish to propose a new feature to be added to p5.js. For example to add support for drawing native HTML `<table>` elements with a new `createTable` function. Some proposals may overlap with existing feature enhancement proposals, in these cases you should just choose whichever template you feel is most appropriate.
 
-Accordingly, the template form fields are nearly identical to the field of the "Existing Feature Enhancement." As such please see the [previous section](#existing-feature-enchancement) for details about how to fill in each field.
+Accordingly, the template form fields are nearly identical to the field of the "Existing Feature Enhancement." As such please see the [previous section](#existing-feature-enhancement) for details about how to fill in each field.
 
 For new feature request proposals to be accepted, they must be approved by at least 2 [area stewards or maintainers](https://github.com/processing/p5.js#stewards) before work can begin on a pull request. 
 
@@ -190,7 +189,7 @@ Similarly, you should work at your own pace and be confident that there is no ha
 
 ## Quick Get Started For Developers
 
-If you want to work/contribute to p5.js'🌸 codebase as a developer, either directly for improving p5.js or for improving its sub-projects like [Friendly Error Systems](.https://github.com/processing/p5.js/blob/main/contributor_docs/friendly_error_system/), you can follow the following steps:
+If you want to work/contribute to p5.js'🌸 codebase as a developer, either directly for improving p5.js or for improving its sub-projects like [Friendly Error Systems](../friendly_error_system/), you can follow the following steps:
 
 1. [Create a fork of p5.js.](https://docs.github.com/en/get-started/quickstart/fork-a-repo)
 2. [Clone your created fork to your computer.](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository)
@@ -373,7 +372,7 @@ If you are going to work on unit tests, please see [here](../unit_testing/). Not
 
 ### Inline documentation
 
-If you are going to work on the inline documentation, as known as p5.js reference, please see [here](../contributing_to_the_p5.js_reference/).
+If you are going to work on the inline documentation, as known as p5.js reference, please see [here](../contributing_to_the_p5js_reference/).
 
 ### Accessibility
 

src/content/contributor-docs/en/contributor_guidelines.mdx

@@ -306,4 +306,4 @@ p5.prototype.myMethod = function(){
 
 **Examples are great, too!** They show people what your library can do. Because this is all JavaScript, people can see them running online before they download anything.[ ](http://jsfiddle.net/) You can create a collection of examples on the p5.js web editor to showcase how your library works.
 
-**Let us know!** Once your library is ready for distribution, send an email to [[email protected]](mailto:[email protected]) with a link and some info. We'll include it on the [libraries page](http://p5js.org/libraries/)! If you have created a library and would like to have it included on the [p5js.org/libraries](https://p5js.org/libraries) page, please fill in [this form](https://docs.google.com/forms/d/e/1FAIpQLSdWWb95cfvosaIFI7msA7XC5zOEVsNruaA5klN1jH95ESJVcw/viewform).
+**Submit your library!** Once your library is ready for distribution and you’d like it included on the [p5js.org/libraries](https://p5js.org/libraries) page, please submit a pull request on the p5.js website GitHub repository following [this intruction](.https://github.com/processing/p5.js-website/blob/main/docs/contributing_libraries/)!

src/content/contributor-docs/en/creating_libraries.mdx

@@ -58,7 +58,7 @@ We use YUIDoc to generate the p5.js API documentation. To generate the docs, nav
 $ npm run grunt yui:dev
 ```
 
-The output will appear in docs/reference. Refer to the [inline documentation guide](.https://github.com/processing/p5.js/blob/main/contributor_docs/contributing_to_the_p5.js_reference/) for more information.
+The output will appear in docs/reference. Refer to the [inline documentation guide](../contributing_to_the_p5js_reference/) for more information.
 
 **[⬆ back to top](#table-of-contents)**
 

src/content/contributor-docs/en/documentation_style_guide.mdx

@@ -39,7 +39,7 @@ The FES is a part of the p5.js' [internationalization] effort. We generate all F
 
 We welcome contributions from all around the world! 🌐
 
-[internationalization]: https://github.com/processing/p5.js/blob/main/contributor_docs/internationalization.md
+[internationalization]: https://github.com/processing/p5.js/blob/main/contributor_docs/archive/internationalization.md
 
 [i18next]: https://www.i18next.com/
 
@@ -132,7 +132,7 @@ translator('fes.fileLoadError.image', { suggestion });
 
 The [internationalization doc] has a step-by-step guide on adding and modifying translation files.
 
-[internationalization doc]: https://github.com/processing/p5.js/blob/main/contributor_docs/internationalization.md
+[internationalization doc]: https://github.com/processing/p5.js/blob/main/contributor_docs/archive/internationalization.md
 
 ## Understanding How FES Works
 
@@ -165,13 +165,13 @@ These functions are mainly responsible for catching errors and generating FES me
 
 For full reference, please see our [Dev Notes].
 
-[`_friendlyFileLoadError()`]: https://github.com/processing/p5.js/blob/main/contributor_docs/fes_contribution_guide.md#_friendlyerror
+[`_friendlyFileLoadError()`]: ./fes_contribution_guide.md#_friendlyerror
 
-[`_validateParameters()`]: https://github.com/processing/p5.js/blob/main/contributor_docs/fes_contribution_guide.md#_validateparameters
+[`_validateParameters()`]: ./fes_contribution_guide.md#_validateparameters
 
-[`_fesErrorMontitor()`]: https://github.com/processing/p5.js/blob/main/contributor_docs/fes_contribution_guide.md#feserrormonitor
+[`_fesErrorMontitor()`]: ./fes_contribution_guide.md#feserrormonitor
 
-[Dev Notes]: https://github.com/processing/p5.js/blob/main/contributor_docs/fes_contribution_guide.md#-development-notes
+[Dev Notes]: ./fes_contribution_guide.md#-development-notes
 
 #### FES Message Displayer
 

src/content/contributor-docs/en/friendly_error_system.mdx

@@ -31,7 +31,7 @@ Before we begin, identify which one of the following cases describes your case b
 
 ### Step 1 – Double-check your inline documentation
 
-First, ensure your method has [inline documentation](.https://github.com/processing/p5.js/blob/main/contributor_docs/contributing_to_the_p5.js_reference/) with the full list of your parameters.
+First, ensure your method has [inline documentation](../contributing_to_the_p5js_reference/) with the full list of your parameters.
 
 For example, the `circle()` method has the following inline documentation that starts with a description of the method, followed by a parameter list, and then code for an example:
 
@@ -274,7 +274,7 @@ The above parameter validation message will be shown in Korean if the browser is
 Please consider adding unit tests for your new FE messages to detect bugs early and to ensure your code is delivering intended messages to our users. Also, unit tests are a good way to make sure other contributor’s new code does not accidentally break or interfere with the functionality of your code. Here are a few good guides on unit testing:
 
 * [Unit Testing and Test Driven Development](https://docs.google.com/document/d/1iw60L1abRJZDn1zUViO9A0j6Fco4yFoQ9LXIlEEroN8/edit?usp=sharing) by Andy Timmons
-* [Contributors Doc: Unit Testing](.https://github.com/processing/p5.js/blob/main/contributor_docs/unit_testing/)
+* [Contributors Doc: Unit Testing](../unit_testing/)
 
 Example:
 
@@ -301,4 +301,4 @@ Additionally, we are excited to share insights from our community through the FE
 * [21-22 FES Survey Report Comic](https://almchung.github.io/p5jsFESsurvey/)
 * [21-22 FES Survey Full Report](https://observablehq.com/@almchung/p5-fes-21-survey)
 
-For more in-depth information about the design and technical aspects of FES, please refer to the [FES README document](.https://github.com/processing/p5.js/blob/main/contributor_docs/friendly_error_system/). This document provides detailed explanations and development notes, which are beneficial for those seeking a deeper understanding of FES.
+For more in-depth information about the design and technical aspects of FES, please refer to the [FES README document](../friendly_error_system/). This document provides detailed explanations and development notes, which are beneficial for those seeking a deeper understanding of FES.

src/content/contributor-docs/en/how-to-add-friendly-error-messages.mdx

@@ -12,24 +12,24 @@ Whether you have just joined us as a steward, are a seasoned maintainer of p5.js
 
 ## Table of Contents
 
-* [Issues](steward_guidelines.md#issues)
-  * [Bug report](steward_guidelines.md#bug-report)
-  * [Feature request](steward_guidelines.md#feature-request)
-  * [Feature enhancement](steward_guidelines.md#feature-enhancement)
-  * [Discussion](steward_guidelines.md#discussion)
-* [Pull Requests](steward_guidelines.md#pull-requests)
-  * [Simple fix](steward_guidelines.md#simple-fix)
-  * [Bug fix](steward_guidelines.md#bug-fix)
-  * [New feature/feature enhancement](steward_guidelines.md#new-feature-feature-enhancement)
-  * [Dependabot](steward_guidelines.md#dependabot)
-* [Build Process](steward_guidelines.md#build-process)
-  * [Main build task](steward_guidelines.md#main-build-task)
-  * [Miscellaneous tasks](steward_guidelines.md#miscellaneous-tasks)
-* [Release Process](steward_guidelines.md#release-process)
-* [Tips & Tricks](steward_guidelines.md#tips--tricks)
-  * [Reply templates](steward_guidelines.md#reply-templates)
-  * [GitHub CLI](steward_guidelines.md#github-cli)
-  * [Managing notifications](steward_guidelines.md#managing-notifications)
+* [Issues](#issues)
+  * [Bug report](#bug-report)
+  * [Feature request](#feature-request)
+  * [Feature enhancement](#feature-enhancement)
+  * [Discussion](#discussion)
+* [Pull Requests](#pull-requests)
+  * [Simple fix](#simple-fix)
+  * [Bug fix](#bug-fix)
+  * [New feature/feature enhancement](#new-feature-feature-enhancement)
+  * [Dependabot](#dependabot)
+* [Build Process](#build-process)
+  * [Main build task](#main-build-task)
+  * [Miscellaneous tasks](#miscellaneous-tasks)
+* [Release Process](#release-process)
+* [Tips & Tricks](#tips--tricks)
+  * [Reply templates](#reply-templates)
+  * [GitHub CLI](#github-cli)
+  * [Managing notifications](#managing-notifications)
 
 ***
 
@@ -90,7 +90,7 @@ Feature request issues should use the "New Feature Request" issue template. The
 
 Feature enhancement issues should use the "Existing Feature Enhancement" issue template. The process is very similar to new feature requests. The difference between a new feature request and feature enhancement can be blurry sometimes. Feature enhancement mainly deals with existing functions of p5.js while a new feature request could be requesting entirely new functions to be added.
 
-1. Similar to new feature requests, feature enhancement should only be accepted if they increase access to p5.js. Please see point 1 of [section above](steward_guidelines.md#feature-request).
+1. Similar to new feature requests, feature enhancement should only be accepted if they increase access to p5.js. Please see point 1 of [section above](#feature-request).
 2. Inclusion criteria for feature enhancements are similar to those for feature requests, but particular attention should be paid to potential breaking changes.
    * If modifying existing functions, all previous valid and documented function signatures must behave in the same way.
 3. Feature enhancements must be approved by at least one steward or maintainer before work should begin toward a PR. The PR review process for feature enhancement is documented below.
@@ -110,7 +110,7 @@ This type of issue has a minimal template ("Discussion") and should be used to g
 Almost all code contributions to the p5.js repositories happen through pull requests. Stewards and maintainers may have push access to the repositories but are still encouraged to follow the same issue > PR > review process when contributing code. Here are the steps to review a PR:
 
 * Pull request template can be found [here](.https://github.com/processing/p5.js/blob/main/.github/PULL_REQUEST_TEMPLATE/).
-* Almost all pull requests must have associated issues opened and discussed first, meaning the relevant [issue workflow](steward_guidelines.md#issues) must have been followed first before a PR should be reviewed by any steward or maintainer.
+* Almost all pull requests must have associated issues opened and discussed first, meaning the relevant [issue workflow](#issues) must have been followed first before a PR should be reviewed by any steward or maintainer.
   * The only instances where this does not apply are very minor typo fixes, which do not require an open issue and can be merged by anyone with merge access to the repo, even if they are not stewards of a particular area.
   * While this exception exists, we will apply it in practice only while contributors are still encouraged to open new issues first. In other words, if in doubt about whether this exception applies, just open an issue anyway.
 * If a pull request does not fully solve the referenced issue, you can edit the original post and change "Resolves #OOOO" to "Addresses #OOOO" so that it does not automatically close the original issue when the PR is merged.
@@ -129,7 +129,7 @@ Simple fixes, such as a small typo fix, can be merged directly by anyone with me
 
 2. The PR "Files Changed" tab can be used to initially review whether the fix is implemented as described in the issue discussion.
 
-3. The PR should be tested locally whenever possible and relevant. The GitHub CLI can help streamline some of the process. (See more below in [Tips & Tricks](steward_guidelines.md#tips-tricks)).
+3. The PR should be tested locally whenever possible and relevant. The GitHub CLI can help streamline some of the process. (See more below in [Tips & Tricks](#tips-tricks)).
    * [ ] The fix should address the original issue sufficiently.
    * [ ] The fix should not change any existing behaviors unless agreed upon in the original issue.
    * [ ] The fix should not have a significant performance impact on p5.js.
@@ -322,13 +322,13 @@ Below are some of the Saved Replies that are being used by p5.js maintainers. Yo
 
 ##### Closing: Access
 
-> I'm not seeing a lot of interest in this feature, and we don't have a clear explanation of how it [expands access](.access/), so I will close this for now. If an access statement can be added to the issue request, please feel welcome to reopen.
+> I'm not seeing a lot of interest in this feature, and we don't have a clear explanation of how it [expands access](../access/), so I will close this for now. If an access statement can be added to the issue request, please feel welcome to reopen.
 
-> We do not see a further explanation of how this issue [expands access](.access/), so I will close this issue for now. If a more detailed access statement can be added to the feature request, please feel welcome to reopen it. Thank you!
+> We do not see a further explanation of how this issue [expands access](../access/), so I will close this issue for now. If a more detailed access statement can be added to the feature request, please feel welcome to reopen it. Thank you!
 
 ##### Closing: Addon
 
-> I think this function is beyond the scope of the p5.js API (we try to keep it as minimal as possible), but it could be a great starting point for an addon library. See the docs here for how to create an addon: [https://github.com/processing/p5.js/blob/main/contributor\_docs/creating\_libraries.md](.creating_libraries/)
+> I think this function is beyond the scope of the p5.js API (we try to keep it as minimal as possible), but it could be a great starting point for an addon library. See the docs here for how to create an addon: [Creating an Addon Library](../creating_libraries/)
 
 ##### Closing PR: Need Issue First