Merge branch 'main' into feat/libraries-directory

Author: davepagurek

.github/ISSUE_TEMPLATE/1.find-a-bug.yml

@@ -0,0 +1,77 @@
+name: "🐛 Found a Bug"
+description: Report p5.js website bugs (broken or incorrect behaviour).
+labels: [ Bug ]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        - Please make sure to [search for existing issues](https://github.com/processing/p5.js-website/issues) before filing a new one!
+
+  - type: dropdown
+    attributes:
+      label: Most appropriate sections of the p5.js website?
+      options:
+        - Home
+        - Reference
+        - Tutorials
+        - Examples
+        - Contribute
+        - Community (Sketches, Libraries, Events)
+        - About
+        - Other (specify if possible)
+    validations:
+      required: true
+
+  - type: dropdown
+    attributes:
+      label: What is your operating system?
+      options:
+        - Windows
+        - Mac OS
+        - Linux
+        - Android
+        - iOS
+        - Other (specify if possible)
+    validations:
+      required: false
+
+  - type: input
+    attributes:
+      label: Web browser and version
+      description: |
+        In the address bar, on Chrome enter `chrome://version`, on Firefox enter `about:support`. On Safari, use `About Safari`.
+    validations:
+      required: false
+
+  - type: textarea
+    attributes:
+      label: Actual Behavior
+      placeholder: What is currently happening.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Expected Behavior
+      description: |
+        If you want to include screenshots, paste them into the markdown editor below.
+      placeholder: What were you expecting?
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: |
+        - Add steps to reproduce bugs or add information on the place where the feature should be implemented.
+        - Add links to a sample deployment or code.
+    validations:
+      required: false
+
+  - type: input
+    attributes:
+      label: Would you like to work on the issue?
+      description: |
+        Please let us know if you can work on it or the issue should be assigned to someone else.
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/2.feature-request.yml

@@ -0,0 +1,31 @@
+name: 🌱 New Feature Request
+description: Request a new feature be added.
+labels: [ Feature Request ]
+body:
+  - type: textarea
+    attributes:
+      label: Increasing Access
+      description: How would this new feature help [increase access](https://github.com/processing/p5.js/blob/main/contributor_docs/access.md) to p5.js? (If you're not sure, you can type "Unsure" here and let others from the community offer their thoughts.)
+    validations:
+      required: true
+
+  - type: dropdown
+    attributes:
+      label: Most appropriate sub-area of p5.js?
+      options:
+        - Home
+        - Reference
+        - Tutorials
+        - Examples
+        - Contribute
+        - Community (Sketches, Libraries, Events)
+        - About
+        - Other (specify if possible)
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Feature request details
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/3.discussion.yml

@@ -0,0 +1,10 @@
+name: 💭 Discussion
+description: This template is for starting a discussion.
+labels: [ Discussion ]
+body:
+  - type: textarea
+    attributes:
+      label: Topic
+      description: What do you want to discuss with the group?
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,12 @@
+blank_issues_enabled: true
+
+contact_links:
+  - name: 🌸 p5.js Library Issues
+    url: https://github.com/processing/p5.js/issues
+    about: Report issues with the p5.js here.
+  - name: 🖥️ Web Editor Issues
+    url: https://github.com/processing/p5.js-web-editor/issues
+    about: Report issues with the p5.js web editor here.
+  - name: 💬 Forum
+    url: https://discourse.processing.org/c/p5js
+    about: Have other questions about using p5.js? Ask them here!

.github/ISSUE_TEMPLATE/default--select-this-.md

@@ -22,4 +22,8 @@ pnpm-debug.log*
 
 temp/*
 in/
-out/
+out/
+translator/
+
+# Don't commit custom dev builds
+public/p5.min.js

.gitignore

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2015-present p5.js contributors & The Processing Foundation
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

LICENSE

@@ -9,7 +9,7 @@ If you discover a bug or have an idea for a new feature you'd like to add, begin
 If you are here to edit or translate content, please do so inside [the `src/content/` folder](/src/content).
 
 ### Code Changes
-For making code changes, please check out the [technical overview](./docs/techical_overview.md) to get started.
+For making code changes, please check out the [technical overview](./docs/technical_overview.md) to get started.
 
 ### Adding Libraries
 Follow the steps in the <a href="./docs/contributing_libraries.md">Contributing Libraries</a> doc if you would like to add your libary to the collection!

README.md

@@ -17,6 +17,7 @@ if (shouldSkipCompress) {
 
 // https://astro.build/config
 export default defineConfig({
+  site: 'https://p5js.org',
   integrations: [
     preact({
       compat: true,
@@ -50,7 +51,7 @@ export default defineConfig({
     defaultStrategy: "viewport",
     prefetchAll: true,
   },
-  trailingSlash: "ignore",
+  trailingSlash: "always",
   build: {
     format: "directory",
   },

astro.config.mjs

@@ -4,6 +4,23 @@ This repo includes a few scripts to pull content from external sources, primaril
 
 They are all runnable via npm scripts.
 
+## Testing the docs of your fork
+
+If you are contributing a change to the main p5.js repo that affects documentation, you will want to preview how your changes will look on the website. To do so, make sure you have committed your changes to a branch of your fork of p5.js.
+
+Then, in the p5.js-website repo, run the following command, using the URL of your fork  of p5 before the `#`, and the name of your branch after the `#`:
+
+```sh
+npm run custom:dev https://github.com/yourUsername/p5.js.git#yourBranch
+```
+
+This will build the reference from your branch and start a development preview of the website. A URL will be logged in the console that you can go to in your browser to test out your changes.
+
+When you're done, you can run this command to reset your changes:
+```sh
+npm run custom:cleanup
+```
+
 ## After a p5.js release
 
 To update the content on the p5.js website following a new release of p5.js, you should run all of these commands to pull in the latest content. **Be sure to run the search indices script last as it depends on the results of the other scripts to be accurate.**