Switch websites so that v2.x deploys to p5js.org (the beta.p5js.org links continue to work via redirects) #1426

Please see the parent issue for timeline and context. lease feel free to raise questions, concerns, or overlooked tasks; however, the work will be done by the maintainers, so it is not open to implementation volunteers. However, additional non-blocking but very helpful tasks are at the bottom of the issue - volunteers are welcome to help!

When this task is done, on the p5.js-website repository, the main branch will include p5.js version 2 latest (currently 2.0), and a v1 branch will contain version 1 latest (currently main). Also, the p5js.org website will serve the main version 2.x reference, with beta.p5js.org redirecting to it to preserve existing URL usage. The version 1.x reference will remain accessible on v1.p5js.org. This task affects p5.js workflows but not the editor, please see parent issue for more info.

Steps maintainers will take

• Merge prerequisite PR that:
  • Update links in p5.js repo on FES (including internationalization/localization strings) to correct URLs used by p5.js#v1 to use v1.p5js.org for v1. No matching change is needed for v2.
  • Updates contributor docs to use correct website links - mostly, should not be needed, and most links should be relative
  • There should be no links that become dead/bad after switch. Even better if there are NO external links (only to *.p5js.org)
  • updates all release workflows to refer to the correct branch
  • Ensure there are no .todo mdx (tutorials that are skipped for beta site) in 2.0 branch (in progress)
• Rename main to “v1?” and deploy it to v1.p5js.org
• Rename 2.0 to main branch and deploy
• Set up redirect for beta.p5js.org → p5js.org to preserve old urls

Tasks open to volunteers

If a volunteer would like to audit FES links of external content (outside of p5js.org), this would be really helpful! Every time there is Content that is only in a blog or p5.js wiki (not maintained) or mdn, but is important, it should be added in the p5js.org website, and linked to correctly. However, this is not blocking for the switch, and even if a PR is made before the switch, it will likely not be merged until after.

We would also be grateful to volunteers for testing if existing community libraries listed on the website are working with 2.x. An audit was already done by maintainers when we released in April 2025, with proactive communication to the add-on library authors; and we are revisiting this audit again. However, more hands on deck is welcome 💟

Related

Shared for visibility / not blocking:

• Update VS Code tutorial section with p5.js 2.x Project Generator extension #1028