p5.js-website update workflow

.github/workflows/update-p5jswebsite.yml

@@ -0,0 +1,20 @@
+name: Trigger documentation update in p5.js-website
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  trigger:
+    runs-on: ubuntu-latest
+    name: Dispatch event to p5.js-website 
+    steps:
+      - name: Clone repository
+        uses: actions/checkout@v1
+      - name: Dispatch event to p5.js-website
+        uses: peter-evans/repository-dispatch@v1
+        with:
+          token: ${{ secrets.P5JS_TOKEN }}
+          repository: processing/p5.js-website
+          event-type: p5.js-release
+          client-payload: '{"ref": "${{ github.ref }}", "sha": "${{ github.sha }}"}'

tasks/release/release-p5.js

@@ -2,7 +2,6 @@
 // The release process includes:
 // 1. Creating the release archive (p5.js, p5.min.js, p5.sound.js, p5.sound.min.js, and p5.zip).
 // 2. Releasing to Bower via https://github.com/processing/p5.js-release (release-bower)
-// 3. Releasing the reference on the website via https://github.com/processing/p5.js-website (release-docs)
 
 const open = require('open');
 const spawn = require('child_process').spawnSync;
@@ -63,9 +62,6 @@ module.exports = function(grunt) {
       // 2. Push the new lib files to the dist repo (to be referred as bower-repo here)
       grunt.task.run('release-bower');
 
-      // 3. Push the docs out to the website
-      grunt.task.run('release-docs');
-
       done();
     }
   );