Remove block mu-plugin, add block.json checking workflow

.github/workflows/block-json-check.yml

@@ -0,0 +1,29 @@
+name: Test for block.json files.
+
+on: 
+  pull_request:
+    branches: [ trunk, develop ]
+
+jobs:
+  block-file-check:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Get all files
+      id: changed-block-json-files
+      uses: tj-actions/changed-files@v44
+
+    - name: Leave a comment and reject PR if block.json file is present
+      if: contains(steps.changed-block-json-files.outputs.all_changed_files, 'block.json')
+      uses: actions/github-script@v7
+      with:
+        script: |
+          github.rest.issues.createComment({
+            issue_number: context.issue.number,
+            owner: context.repo.owner,
+            repo: context.repo.repo,
+            body: '> [!CAUTION]\n> This PR includes a `block.json` file. If you are adding a new block, please ensure this goes into [the WPCOM Special Projects Monorepo](https://github.com/a8cteam51/special-projects-blocks-monorepo) instead. You will find[ full documentation on the process here](https://github.com/a8cteam51/special-projects-blocks-monorepo/wiki). Please discuss with WPComSP Engineering Leads if you believe  your block should be exempt from the monorepo.'
+          })
+          core.setFailed('This PR included a block.json file and so was rejected.')

.github/workflows/fill-in-scaffold.yml

@@ -30,7 +30,6 @@ jobs:
           git submodule update
           git mv --force README.scaffold.md README.md
           git mv themes/build-processes-demo themes/${{ github.event.repository.name }}
-          git mv mu-plugins/build-processes-demo-blocks mu-plugins/${{ github.event.repository.name }}-blocks
           git mv mu-plugins/build-processes-demo-features mu-plugins/${{ github.event.repository.name }}-features
 
       - name: Commit the changed files.

.gitignore

@@ -15,7 +15,6 @@ mu-plugins/*
 !mu-plugins/mu-loader.php
 !mu-plugins/colophon
 !mu-plugins/team51-tracking
-!mu-plugins/build-processes-demo-blocks
 !mu-plugins/build-processes-demo-features
 
 themes/*

README.md

@@ -80,11 +80,7 @@ FSE template parts are included in this to show desired folder structure only. Y
 
 ### Gutenberg blocks
 
-All custom-built blocks must be placed in a mu-plugin. The demo project contains a mu-plugin called `build-processes-demo-blocks` which exemplifies building two blocks called `build-processes-demo/foobar` and `build-processes-demo/spamham`, respectively.
-
-By separating the blocks from the theme into a mu-plugin, we can ensure that the blocks are always available on the site, even if the theme is changed (e.g., because of a future redesign or as part of the debugging process). Moreover, it forces us, as developers, to think about the blocks as a separate entity from the theme and to design the code as such thus making it easier to reuse them in other projects.
-
-The mu-plugin must contain enough CSS for the block to be functional and not appear broken. All other styling can be held in the mu-plugin or the theme. [Seedlet is an example](https://github.com/Automattic/themes/tree/trunk/seedlet/assets/sass/blocks) of a theme providing its own styling for the blocks.
+Custom blocks should now use the [WPCom Special Projects Blocks Monorepo](https://github.com/a8cteam51/special-projects-blocks-monorepo). You'll find full written documentation for how to use this system [in the Wiki of the repo](https://github.com/a8cteam51/special-projects-blocks-monorepo/wiki).
 
 ### Features plugin
 

composer.json

@@ -47,30 +47,22 @@
   "scripts": {
     "format:php": [
       "@format:php:theme",
-      "@format:php:blocks",
       "@format:php:features"
     ],
     "format:php:theme": "phpcbf --standard=./themes/build-processes-demo/.phpcs.xml.dist --basepath=. ./themes/build-processes-demo -v",
-    "format:php:blocks": "phpcbf --standard=./mu-plugins/build-processes-demo-blocks/.phpcs.xml.dist --basepath=. ./mu-plugins/build-processes-demo-blocks -v",
     "format:php:features": "phpcbf --standard=./mu-plugins/build-processes-demo-features/.phpcs.xml.dist --basepath=. ./mu-plugins/build-processes-demo-features -v",
 
     "lint:php": [
       "@lint:php:theme",
-      "@lint:php:blocks",
       "@lint:php:features"
     ],
     "lint:php:theme": "phpcs --standard=./themes/build-processes-demo/.phpcs.xml.dist --basepath=. ./themes/build-processes-demo -v",
-    "lint:php:blocks": "phpcs --standard=./mu-plugins/build-processes-demo-blocks/.phpcs.xml.dist --basepath=. ./mu-plugins/build-processes-demo-blocks -v",
     "lint:php:features": "phpcs --standard=./mu-plugins/build-processes-demo-features/.phpcs.xml.dist --basepath=. ./mu-plugins/build-processes-demo-features -v",
 
     "internationalize": [
       "@makepot:theme",
       "@updatepo:theme",
 
-      "@makepot:blocks",
-      "@updatepo:blocks",
-      "@makejson:blocks",
-
       "@makepot:features",
       "@updatepo:features"
     ],
@@ -79,11 +71,6 @@
     "updatepo:theme": "wp i18n update-po themes/build-processes-demo/languages/build-processes-demo.pot",
     "makemo:theme": "wp i18n make-mo themes/build-processes-demo/languages",
 
-    "makepot:blocks": "wp i18n make-pot mu-plugins/build-processes-demo-blocks",
-    "updatepo:blocks": "wp i18n update-po mu-plugins/build-processes-demo-blocks/languages/build-processes-demo-blocks.pot",
-    "makejson:blocks": "wp i18n make-json mu-plugins/build-processes-demo-blocks/languages --pretty-print --no-purge",
-    "makemo:blocks": "wp i18n make-mo mu-plugins/build-processes-demo-blocks/languages",
-
     "makepot:features": "wp i18n make-pot mu-plugins/build-processes-demo-features",
     "updatepo:features": "wp i18n update-po mu-plugins/build-processes-demo-features/languages/build-processes-demo-features.pot",
     "makemo:features": "wp i18n make-mo mu-plugins/build-processes-demo-features/languages",