docs(Vector): clarify 3-component nature of vectors in 2D usage

.github/ISSUE_TEMPLATE/1-p5.js-2.0-bug-report.yml

@@ -1,18 +1,16 @@
-name: 📃 p5.js 2.0 Beta Bug Report
+name: 📃 p5.js 2.0 Bug Report
 description: This template is for submitting a bug report for bugs found in the p5.js 2.0 beta releases.
-title: "[p5.js 2.0 Beta Bug Report]: "
+title: "[p5.js 2.0 Bug Report]: "
 labels: [p5.js 2.0]
 body:
   - type: markdown
     attributes:
       value: |
         ### What falls under this category?
-        There has been many changes to p5.js in 2.0 that is currently released as beta versions. If you suspect there may be a bug, please follow the below steps before opening a bug report using this template:
-
-        1. There are some differences in behavior between p5.js 1.x and 2.0 beta, please check the changelog and/or [proposal list](https://github.com/orgs/processing/projects/21) to see if the difference in behavior is intended. If in doubt, feel free to open the issue anyway and ask.
-        2. Breaking changes may still happen between beta versions, please make sure to include the full beta version number and use the latest beta release where possible.
-        3. We are not considering any new proposal for p5.js 2.0 at this stage and if you would like to request new features, please use the "New feature request" issue template.
-        4. The documentation and examples may be outdated at this stage while we work on updating them.
+        There has been many changes to p5.js in 2.0! You can try it in p5.js Editor by updating the version in "Settings," and reference is available [on the beta version of the site](https://beta.p5js.org/). If you suspect there may be a bug, please follow the below steps before opening a bug report using this template:
+        1. There are some differences in behavior between p5.js 1.x and 2.0 beta, please check the changelog and/or [2.0 status board](https://github.com/orgs/processing/projects/21) to see if the difference in behavior is intended. If in doubt, feel free to open the issue anyway and ask.
+        2. New proposals for future p5.js 2.x minor releases may be considered! Please use the "New feature request" issue template, or check the [2.0 status board](https://github.com/orgs/processing/projects/21) is there is already discussion abotu this proposal.
+        3. Reports of errors or potential improvements in documentation and examples is expecially helpful, since many things have been updated from 1.x to 2.0!
   - type: checkboxes
     id: sub-area
     attributes:
@@ -78,4 +76,4 @@ body:
 
         ```"
     validations:
-      required: true
+      required: true

.github/ISSUE_TEMPLATE/2-found-a-bug.yml

@@ -19,11 +19,11 @@ body:
         - label: Math
         - label: Typography
         - label: Utilities
+        - label: p5.strands
         - label: WebGL
-        - label: Build process
-        - label: Unit testing
-        - label: Internationalization
-        - label: Friendly errors
+        - label: DevOps, Build process, Unit testing
+        - label: Internationalization (i18n)
+        - label: Friendly Errors
         - label: Other (specify if possible)
 - type: input
   attributes:

.github/config.yml

@@ -4,12 +4,26 @@
 
 # Comment to be posted to on first time issues
 newIssueWelcomeComment: >
-  Welcome! 👋 Thanks for opening your first issue here! And to ensure the community is able to respond to your issue, please make sure to fill out the inputs in the issue forms. Thank you!
-# Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
+   Welcome! 👋 Thanks for opening your first issue here! And to ensure the community is able to respond to your issue, please make sure to fill out the inputs in the issue forms.
+
+   For guidance on contributing, check out our [contributing guidelines](https://github.com/processing/p5.js/blob/main/CONTRIBUTING.md) and other [resources for contributors](https://p5js.org/contribute/).
+
+   💬 If you have questions or need support,  feel free to join the [Processing Foundation Forum](https://discourse.processing.org/) or visit our [Community page](https://p5js.org/community/).
 
+   📜 Please also review our [Code of Conduct](https://p5js.org/code-of-conduct/) to understand our community standards.
+
+   Thank You!
+# Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
 # Comment to be posted to on PRs from first time contributors in your repository
 newPRWelcomeComment: >
-  🎉 Thanks for opening this pull request! Please check out our [contributing guidelines](https://github.com/processing/p5.js/blob/main/CONTRIBUTING.md) if you haven't already. And be sure to add yourself to the [list of contributors on the readme page](https://github.com/processing/p5.js#contributors)!
+   🎉 Thanks for opening this pull request! For guidance on contributing, check out our [contributor guidelines](https://p5js.org/contribute/contributor_guidelines/) and other [resources for contributors](https://p5js.org/contribute)!
+
+   🤔 Please ensure that your PR links to an issue, which has been approved for work by a maintainer; otherwise, there might already be someone working on it, or still ongoing discussion about implementation. You are welcome to join the discussion in an Issue if you're not sure!
+
+   🌸  Once your PR is merged, be sure to [add yourself](https://github.com/processing/p5.js/issues/2309) to the [list of contributors on the readme page](https://github.com/processing/p5.js#contributors) !
+
+
+   Thank You!
 
 # Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge
 

.github/first-timers.yml

@@ -1,4 +1,4 @@
-# You can create the issue in a different repo than where the problem is. Just make sure you installed the bot on the configured repository.
+# You can create the issue in a different repo than where the problem is. Just make sure you have installed the bot on the configured repository.
 # The issue will link back to the original repository where the contribution will be made.
 repository: p5.js
 
@@ -11,4 +11,4 @@ labels:
   - hacktoberfest
 
 # If you would like to add your own template for the issue, add an .md file to your .github folder
-# template: .github/first-timers-issue-template.md 
+# template: .github/first-timers-issue-template.md 

.github/labeler.yml

@@ -22,11 +22,16 @@
   - '\[[xX]\]\s*Utilities'
 "Area:WebGL":
   - '\[[xX]\]\s*WebGL'
+"Internationalization":
+  - '\[[xX]\]\s*Internationalization'
+"DevOps":
+  - '\[[xX]\]\s*Build Process'
+  - '\[[xX]\]\s*Unit Testing'
 "Build Process":
   - '\[[xX]\]\s*Build Process'
 "Unit Testing":
   - '\[[xX]\]\s*Unit Testing'
-"Internationalization":
-  - '\[[xX]\]\s*Internationalization'
 "Friendly Errors":
   - '\[[xX]\]\s*Friendly Errors'
+"p5.strands":
+  - '\[[xX]\]\s*p5.strands'

.github/workflows/auto-close-issues.yml

@@ -0,0 +1,20 @@
+name: Close Linked Issues on PR Merge
+
+on:
+  pull_request:
+    types: [closed]
+    branches:
+      - 2.0
+      - dev-2.0
+
+jobs:
+  close_issues:
+    if: github.event.pull_request.merged == true
+    runs-on: ubuntu-latest
+    steps:
+      - name: Close linked issues on non-default branches
+        uses: processing/branch-pr-close-issue@v1
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          branch: dev-2.0
+

.github/workflows/release-workflow-v2.yml

@@ -0,0 +1,113 @@
+name: New p5.js 2.x release
+# Requires secrets `NPM_TOKEN` and `ACCESS_TOKEN` to be set
+
+permissions:
+  contents: write
+
+on:
+  push:
+    tags:
+      - 'v2.*.*' # Push events to matching v*.*.*, i.e. v20.15.10
+      - 'v2.*.*-*' # Push events to matching v*.*.*-*, i.e. v20.15.10-0
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    name: Release
+    env:
+      INPUT_TOKEN: ${{ secrets.NPM_TOKEN }}
+    steps:
+      # 1. Setup
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: 20
+      - name: Get semver info
+        id: semver
+        uses: akshens/semver-tag@v4
+        with:
+          version: ${{ github.ref_name }}
+
+      - name: Get version number
+        id: version-number
+        run: |
+          version=$(echo ${{ github.ref_name }} | cut -c 2-)
+          echo "version=$version" >> $GITHUB_OUTPUT
+
+      - name: Get current date
+        id: date
+        run: echo "date=$(date +"%B %Oe, %Y")" >> $GITHUB_OUTPUT
+      - name: Install dependencies
+        run: npm ci
+        env:
+          CI: true
+      - name: Run test
+        run: npm test
+        env:
+          CI: true
+      - name: Run build
+        run: npm run build
+
+      # 2. Prepare release files
+      - run: mkdir release && mkdir p5 && cp -r ./lib/* p5/
+      - name: Create release zip file
+        uses: TheDoctor0/zip-release@0.6.2
+        with:
+          type: zip
+          filename: release/p5.zip
+          path: ./p5/*
+
+      - name: Copy release files
+        run: cp lib/p5.js lib/p5.min.js lib/p5.esm.js release/
+
+      # 3. Release p5.js
+      - name: Create GitHub release
+        uses: softprops/action-gh-release@v0.1.15
+        with:
+          draft: true
+          prerelease: ${{ steps.semver.outputs.is-prerelease == 'true' }}
+          files: release/*
+          generate_release_notes: true
+          token: ${{ secrets.ACCESS_TOKEN }}
+      - name: Publish to NPM
+        uses: JS-DevTools/npm-publish@v1
+        with:
+          token: ${{ secrets.NPM_TOKEN }}
+          tag: ${{ steps.semver.outputs.is-prerelease != 'true' && 'latest' || 'beta' }}
+
+      # 4. Update p5.js website
+      - name: Clone p5.js website
+        if: ${{ steps.semver.outputs.is-prerelease != 'true' }}
+        uses: actions/checkout@v3
+        with:
+          repository: processing/p5.js-website
+          ref: '2.0'
+          path: website
+          fetch-depth: 0
+          token: ${{ secrets.ACCESS_TOKEN }}
+      - name: Updated website files
+        if: ${{ steps.semver.outputs.is-prerelease != 'true' }}
+        run: |
+          cd website
+          npm install
+          npm run build:p5-version
+          npm run build:contributor-docs
+          npm run build:contributors
+          npm run build:reference
+          npm run build:search
+      - name: Commit updated website files
+        if: ${{ steps.semver.outputs.is-prerelease != 'true' }}
+        run: |
+          cd website
+          git config --local user.email "41898282+github-actions[bot]@users.noreply.github.com"
+          git config --local user.name "github-actions[bot]"
+          git add .
+          git commit -m "Update p5.js to ${{ github.ref_name }}"
+      - name: Push updated website repo
+        if: ${{ steps.semver.outputs.is-prerelease != 'true' }}
+        uses: ad-m/github-push-action@v0.6.0
+        with:
+          github_token: ${{ secrets.ACCESS_TOKEN }}
+          branch: '2.0'
+          directory: website/
+          repository: processing/p5.js-website

.github/workflows/release-workflow.yml

@@ -7,8 +7,8 @@ permissions:
 on:
   push:
     tags:
-      - 'v*.*.*' # Push events to matching v*.*.*, i.e. v20.15.10
-      - 'v*.*.*-*' # Push events to matching v*.*.*-*, i.e. v20.15.10-0
+      - 'v1.*.*' # Push events to matching v*.*.*, i.e. v20.15.10
+      - 'v1.*.*-*' # Push events to matching v*.*.*-*, i.e. v20.15.10-0
 
 jobs:
   release:
@@ -73,6 +73,7 @@ jobs:
         uses: JS-DevTools/npm-publish@v1
         with:
           token: ${{ secrets.NPM_TOKEN }}
+          tag: r1
 
       # 4. Update p5.js website
       - name: Clone p5.js website
@@ -88,11 +89,11 @@ jobs:
         run: |
           cd website
           npm install
+          npm run build:p5-version
           npm run build:contributor-docs
           npm run build:contributors
           npm run build:reference
           npm run build:search
-          npm run build:p5-version
       - name: Commit updated website files
         if: ${{ steps.semver.outputs.is-prerelease != 'true' }}
         run: |

.github/workflows/stewards-update.yml

@@ -0,0 +1,42 @@
+name: Update Steward Table in README
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - stewards.yml
+  workflow_dispatch:
+
+jobs:
+  build:
+    if: github.ref == 'refs/heads/main' && github.repository == 'processing/p5.js'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: "20"
+
+      - name: Install dependencies
+        run: npm install js-yaml
+
+      - name: Run table generator
+        run: node utils/stewards-table.js
+
+      - name: Reset all changes except README.md
+        run: |
+          git restore --staged .
+          git add README.md
+          git checkout -- .
+
+      - name: Create Pull Request
+        uses: peter-evans/create-pull-request@v7
+        with:
+          commit-message: "Update README table from stewards.yml"
+          branch: update-readme-table
+          title: "chore: update README table from stewards.yml"
+          body: "This PR updates the README.md table to reflect changes in stewards.yml."
+          add-paths: README.md
+          token: ${{ secrets.ACCESS_TOKEN }}