@ideasonpurpose/build-tools-wordpress 2.6.6 → 2.7.0

package/AGENTS.md

@@ -0,0 +1,68 @@
+## AI Coding Assistant Guidelines
+
+**Mantra:** Minimal. Surgical. Collaborative. Verifiable.
+
+### 0. Communicate like a senior engineer
+
+- Start with the answer, no preamble.
+- Match response length to task complexity.
+- Begin with a brief plan: what you understand, assumptions, approach.
+- Call out trade-offs explicitly (simplicity vs future-proofing, readability vs performance).
+- When ambiguous, present 2-3 concrete options with pros/cons instead of guessing.
+- Ask for confirmation on anything unclear.
+
+## 1. Think Before Coding
+
+Optimize for simplicity, maintainability, readability.
+
+**Don't assume. Don't hide confusion. Offer alternatives.**
+
+Before implementing:
+
+- State assumptions explicitly. If uncertain, ask.
+- If multiple interpretations exist, offer choices — don't pick silently.
+- If a simpler approach exists, say so and push back.
+- If unclear, stop and name what's confusing.
+
+## 2. Simplicity First
+
+**Minimum code that solves the problem. Nothing speculative.**
+
+- Delete more than you add.
+- Prefer boring, obvious code over clever code.
+- No features beyond what was asked.
+- No abstractions for single-use code.
+- No "flexibility" or "configurability" that wasn't requested.
+- Only add error handling for realistically possible cases given current scope and style.
+- Never introduce new dependencies unless explicitly asked.
+- If you write 200 lines and it could be 50, rewrite it.
+
+Ask yourself: "Would a senior engineer call this overcomplicated?" If yes, simplify.
+
+## 3. Surgical Changes
+
+**Touch only what you must. Clean up only your own mess.**
+
+When editing existing code:
+
+- Preserve the spirit and conventions of the codebase.
+- Don't "improve" adjacent code, comments, or formatting.
+- Don't remove comments or commented-out code.
+- Don't refactor things that aren't broken.
+- Match existing style, even if you'd do it differently.
+- If you notice unrelated dead code, mention it - don't delete it.
+
+When your changes create orphans:
+
+- Remove imports/variables/functions that _your_ changes made unused.
+- Do not remove pre-existing dead code unless asked.
+
+Every changed line should trace directly to the user's request.
+
+## 4. Documentation and Comments
+
+- Prefer self-documenting code and descriptive names over comments.
+- Add comments only where the _why_ is not obvious from the code.
+- Update or delete comments that your changes invalidate.
+- Follow the existing codebase's conventions for types, docstrings, and documentation style.
+

package/CHANGELOG.md

@@ -4,6 +4,14 @@ All notable changes to this project will be documented in this file. Dates are d
 
 Generated by [`auto-changelog`](https://github.com/CookPete/auto-changelog).
 
+#### v2.6.6
+
+> 27 April 2026
+
+- bump deps
+- feat: add nested list structure and formatting for WordPress block patterns
+- feat: add experimental formatting helpers for HTML/PHP and WordPress block patterns
+
 #### v2.6.5
 
 > 5 April 2026

package/README.md

@@ -1,6 +1,6 @@
 # @ideasonpurpose/build-tools-wordpress
 
-#### Version 2.6.6
+#### Version 2.7.0
 
 [![NPM Version](https://img.shields.io/npm/v/%40ideasonpurpose%2Fbuild-tools-wordpress?logo=npm)](https://www.npmjs.com/package/@ideasonpurpose/build-tools-wordpress)
 [![GitHub Actions Workflow Status](https://img.shields.io/github/actions/workflow/status/ideasonpurpose/build-tools-wordpress/npm-publish.yml?logo=github&logoColor=white)](https://github.com/ideasonpurpose/build-tools-wordpress#readme)

package/boilerplate/.env.sample

@@ -0,0 +1,77 @@
+# Configuration for the Ideas On Purpose WordPress Docker environment,
+# more info here: https://github.com/ideasonpurpose/docker-wordpress-dev
+
+
+SSH_KEY_PATH=
+#   SSH_KEY_PATH should be set to the local path to your private key. For example,
+#   if you have public key named `id_ed25519_deploy.pub` associated with your managed
+#   WordPress account, SSH_KEY_PATH should point to the pair's matching private
+#   key like this:  SSH_KEY_PATH="~/.ssh/id_ed25519_deploy"
+
+
+SSH_LOGIN=
+#   SSH_LOGIN should be set to the SSH Login string from WP Engine's or Kinsta's
+#   admin backend. They should look something like this:
+#   - wpengine:   "iop001@iop001.ssh.wpengine.net"
+#   - kinsta:     "ssh iop001@11.22.33.44 -p 54321"
+#   In the above examples the elements map like this:
+#        `${SSH_USER}@${SSH_HOST}`
+#   Each item can also be entered individually, and individual entries will take
+#   precedence over components extracted from SSH_LOGIN.
+#   Values should be quoted for compatibility with Docker Compose v2.x
+
+
+SSH_USER=
+#   The user account which connects to the server. For WP Engine, this matches the
+#   environment name.
+
+
+SSH_HOST=
+#   The server address to connect to.
+
+
+SSH_PORT=
+#   The server port listening for SSH connections
+
+
+SSH_WP_CONTENT_DIR=
+#   default:  sites/${SSH_USER}/wp-content
+#   SSH_WP_CONTENT_DIR is the path to the wordpress wp-content directory. This will
+#   most likely match the `WP_CONTENT_DIR` WordPress constant and does not include
+#   a trailing slash.
+#   Path can be relative to the SSH user home folder or an absolute path.
+#   Examples:
+#    - wpengine:  sites/${SSH_USER}/wp-content
+#    - kinsta:    public/wp-content
+
+
+IOP_DEV_PLUGIN_1=
+IOP_DEV_PLUGIN_2=
+IOP_DEV_PLUGIN_3=
+IOP_DEV_PLUGIN_4=
+IOP_DEV_PLUGIN_5=
+IOP_DEV_PLUGIN_6=
+IOP_DEV_PLUGIN_7=
+IOP_DEV_PLUGIN_8=
+#   Additional development plugins can be mounted into the WordPress environment as
+#   individual volumes. The local relative path to the working plugin directory should
+#   be pointed to the absolute path inside the container. In the following example,
+#   an example-plugin project is being developed in a sibling directory to the theme:
+#
+#     IOP_DEV_PLUGIN_1="../example-plugin:/var/www/html/wp-content/plugins/example-plugin"
+
+
+WORDPRESS_DEBUG=1
+#   This is used to set the WP_DEBUG constant to toggle WordPress debugging.
+#   .env vars are imported as strings, so true/false will not work correctly.
+#   PHP does correctly coerce the integers 0 and 1 to their corresponding boolean values.
+#   PHP interprets the number 0 as a string to boolean false
+#   Leave this value blank or set it to 0 to disable WP_DEBUG
+#   Setting this to 1, true or any other non-empty string enables WP_DEBUG
+
+
+WP_ENVIRONMENT_TYPE=
+#   Blank or one of 'production', 'staging' or 'development'. For IOP's development
+#   environments, this value defaults to 'development'. Otherwise WordPress defaults
+#   to 'production'. Documentation:
+#   https://developer.wordpress.org/reference/functions/wp_get_environment_type/

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ideasonpurpose/build-tools-wordpress",
-  "version": "2.6.6",
+  "version": "2.7.0",
   "description": "Build scripts and dependencies for IOP's WordPress development environments.",
   "homepage": "https://github.com/ideasonpurpose/build-tools-wordpress#readme",
   "bugs": {
@@ -41,27 +41,25 @@
     "@rollup/plugin-json": "^6.1.0",
     "@rollup/plugin-node-resolve": "^16.0.3",
     "@svgr/webpack": "^8.1.0",
-    "@wordpress/dependency-extraction-webpack-plugin": "^6.44.0",
+    "@wordpress/dependency-extraction-webpack-plugin": "^6.45.0",
     "ansi-html": "^0.0.9",
     "archiver": "^7.0.1",
-    "auto-changelog": "^2.5.0",
     "autoprefixer": "^10.5.0",
     "babel-loader": "^10.1.1",
-    "caniuse-lite": "^1.0.30001791",
+    "caniuse-lite": "^1.0.30001792",
     "chalk": "^5.6.2",
     "chalk-cli": "^6.0.0",
     "classnames": "^2.5.1",
     "cli-truncate": "^6.0.0",
     "copy-webpack-plugin": "^14.0.0",
     "cosmiconfig": "^9.0.1",
-    "cross-env": "^10.1.0",
     "css-loader": "^7.1.4",
-    "cssnano": "^7.1.7",
+    "cssnano": "^8.0.0",
     "dotenv": "^17.4.2",
     "esbuild-loader": "^4.4.3",
-    "eslint": "^10.2.1",
+    "eslint": "^10.3.0",
     "filesize": "^11.0.17",
-    "fs-extra": "^11.3.4",
+    "fs-extra": "^11.3.5",
     "globby": "^16.2.0",
     "html-webpack-plugin": "^5.6.7",
     "http-proxy": "^1.18.1",
@@ -71,7 +69,7 @@
     "lodash": "^4.18.1",
     "mini-css-extract-plugin": "^2.10.2",
     "ora": "^9.4.0",
-    "postcss": "^8.5.12",
+    "postcss": "^8.5.14",
     "postcss-loader": "^8.2.1",
     "postcss-scss": "^4.0.9",
     "prettier": "^3.8.3",

package/{example → tooling}/docker-compose.yml

@@ -15,6 +15,20 @@ services:
       MYSQL_PASSWORD: wordpress
     # command: >
     #   --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
+    # Command update from https://x.com/i/grok?conversation=2009819808595165421
+    command: >
+      --disable-log-bin
+      --innodb_flush_log_at_trx_commit=2
+      --sync_binlog=0              
+      --innodb_doublewrite=0       
+      --slow-query-log=0
+      --general-log=0
+      --performance_schema=OFF
+    logging: # Prevent container logs from bloating on disk
+      driver: "json-file"
+      options:
+        max-size: "10m"
+        max-file: "3"
 
   # Ideas On Purpose's local WordPress development environment.
   # Update image version with `docker run ideasonpurpose/wordpress init`
@@ -23,7 +37,7 @@ services:
     depends_on:
       - db
     # image: &wp_img ideasonpurpose/wordpress:dev
-    image: &wp_img ideasonpurpose/wordpress:6.7.2
+    image: &wp_img ideasonpurpose/wordpress:6.9.4
     restart: always
     volumes:
       - wp_data:/var/www/html
@@ -49,8 +63,6 @@ services:
       - 9003
 
     # Link external plugin projects by defining host:container path pairs in .env
-    # An example .env entry looks like this:
-    #  IOP_DEV_PLUGIN_1="../iop-data-model/:/var/www/html/wp-content/plugins/iop-data-model"
     environment:
       IOP_DEV_PLUGIN_1:
       IOP_DEV_PLUGIN_2:
@@ -60,15 +72,6 @@ services:
       IOP_DEV_PLUGIN_6:
       IOP_DEV_PLUGIN_7:
       IOP_DEV_PLUGIN_8:
-      WP_ENVIRONMENT_TYPE:
-      WP_MULTISITE:
-
-    # Apache will throw errors for any ulimit value below 8192
-    # NOTE THAT THIS MIGHT BE MORE THAN THE SYSTEM OFFERS
-    # TODO: Still true?
-    # TODO: Testing removal. 2025-03-18
-    # ulimits:
-    #   nofile: 8192
 
     # Required for iptables port-mapping to work inside the Docker image
     # This is used to fix a PHP/WordPress issue where internal requests
@@ -76,28 +79,10 @@ services:
     cap_add:
       - NET_ADMIN
 
-  # # TODO: Deprecated and likely ready to remove 2025-03-18
-  # # Ideas On Purpose's development toolchain
-  # # Image from: https://hub.docker.com/r/ideasonpurpose/docker-build
-  # tools:
-  #   # image: ideasonpurpose/docker-build:dev
-  #   image: ideasonpurpose/docker-build:0.17.2
-  #   user: "${UID:-1000}:${GID:-1000}"
-  #   depends_on:
-  #     - wordpress
-  #   volumes:
-  #     - .:/usr/src/site/
-  #   ports:
-  #     - "${npm_config_port:-8080}:8080"
-  #   environment:
-  #     PORT: ${npm_config_port:-8080}
-  #   entrypoint: npm run
-  #   command: start
-
   # Utility service for running composer commands
   # Image from: https://hub.docker.com/_/composer
   composer:
-    image: composer:2.8
+    image: composer:2.9
     profiles: ["utility"]
     user: "${UID:-1000}:${GID:-1000}"
     environment:
@@ -281,17 +266,6 @@ services:
     secrets:
       - SSH_KEY
 
-  # Run the init script from ideasonpurpose/wordpress:latest (intentionally "latest")
-  # to refresh tooling and bring the project inline with our boilerplate
-  # Project info: https://github.com/ideasonpurpose/docker-wordpress-dev
-  refresh:
-    # image: ideasonpurpose/wordpress:dev
-    image: ideasonpurpose/wordpress:latest
-    profiles: ["utility"]
-    volumes:
-      - .:/usr/src/site
-    command: init
-
 secrets:
   SSH_KEY:
     file: ${SSH_KEY_PATH:-~/.ssh/your_ssh_private_key}