Fix code quality issues: add ESLint config to Cypress files, update documentation, improve HTML accessibility

.wiki/Playground-Testing.md

@@ -15,9 +15,9 @@ This document explains how to use WordPress Playground for testing our plugin.
 
 The easiest way to test our plugin with WordPress Playground is to use the online version:
 
-1. Single site testing: [Open in WordPress Playground](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/wpallstars/wp-plugin-starter-template-for-ai-coding/feature/testing-framework/playground/blueprint.json&_t=11)
+1. Single site testing: [Open in WordPress Playground](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/wpallstars/wp-plugin-starter-template-for-ai-coding/main/playground/blueprint.json&_t=1)
 
-2. Multisite testing: [Open in WordPress Playground](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/wpallstars/wp-plugin-starter-template-for-ai-coding/feature/testing-framework/playground/multisite-blueprint.json&_t=23)
+2. Multisite testing: [Open in WordPress Playground](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/wpallstars/wp-plugin-starter-template-for-ai-coding/main/playground/multisite-blueprint.json&_t=1)
 
 These links will automatically set up WordPress with multisite enabled, WP_DEBUG enabled, and both the Plugin Toggle and Kadence Blocks plugins activated.
 
@@ -111,8 +111,8 @@ We have two blueprints for testing:
 To run tests with WordPress Playground:
 
 1. Open the appropriate WordPress Playground link:
-   * [Single site](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/wpallstars/wp-plugin-starter-template-for-ai-coding/feature/testing-framework/playground/blueprint.json&_t=11)
+   * [Single site](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/wpallstars/wp-plugin-starter-template-for-ai-coding/main/playground/blueprint.json&_t=1)
-   * [Multisite](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/wpallstars/wp-plugin-starter-template-for-ai-coding/feature/testing-framework/playground/multisite-blueprint.json&_t=23)
+   * [Multisite](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/wpallstars/wp-plugin-starter-template-for-ai-coding/main/playground/multisite-blueprint.json&_t=1)
 
 2. Test the plugin manually in the browser
 
@@ -122,6 +122,7 @@ We've also included HTML files that embed WordPress Playground:
 
 1. Open `playground/index.html` in your browser for single site testing
 2. Open `playground/multisite.html` in your browser for multisite testing
+3. Open `playground/test.html` in your browser for a unified interface with buttons to switch between single site and multisite
 
 You can serve these files locally with a simple HTTP server:
 

.wiki/Testing.md

@@ -106,11 +106,11 @@ WordPress Playground runs WordPress entirely in the browser using WebAssembly. T
 
 The easiest way to test our plugin with WordPress Playground is to use the online version:
 
-1. Single site testing: [Open in WordPress Playground](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/wpallstars/wp-plugin-starter-template-for-ai-coding/feature/testing-framework/playground/blueprint.json&_t=9)
+1. Single site testing: [Open in WordPress Playground](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/wpallstars/wp-plugin-starter-template-for-ai-coding/main/playground/blueprint.json&_t=1)
 
-2. Multisite testing: [Open in WordPress Playground](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/wpallstars/wp-plugin-starter-template-for-ai-coding/feature/testing-framework/playground/multisite-blueprint.json&_t=23)
+2. Multisite testing: [Open in WordPress Playground](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/wpallstars/wp-plugin-starter-template-for-ai-coding/main/playground/multisite-blueprint.json&_t=1)
 
-These links will automatically set up WordPress with multisite enabled, WP_DEBUG enabled, and both the Plugin Toggle and Hello Dolly plugins activated.
+These links will automatically set up WordPress with multisite enabled, WP_DEBUG enabled, and both the Plugin Toggle and Kadence Blocks plugins activated.
 
 #### Local Testing with HTML Files
 
@@ -118,6 +118,7 @@ We've also included HTML files that embed WordPress Playground:
 
 1. Open `playground/index.html` in your browser for single site testing
 2. Open `playground/multisite.html` in your browser for multisite testing
+3. Open `playground/test.html` in your browser for a unified interface with buttons to switch between single site and multisite
 
 You can serve these files locally with a simple HTTP server:
 

cypress/e2e/playground-multisite.cy.js

@@ -1,3 +1,4 @@
+/* eslint-env mocha, jquery, cypress */
 describe('WordPress Playground Multisite Tests', () => {
   beforeEach(() => {
     // Visit the WordPress Playground page

cypress/e2e/playground-single-site.cy.js

@@ -1,3 +1,4 @@
+/* eslint-env mocha, jquery, cypress */
 describe('WordPress Playground Single Site Tests', () => {
   beforeEach(() => {
     // Visit the WordPress Playground page

playground/index.html

@@ -21,6 +21,6 @@
     </style>
 </head>
 <body>
-    <iframe src="https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/wpallstars/wp-plugin-starter-template-for-ai-coding/feature/testing-framework/playground/blueprint.json&_t=11" title="WordPress Playground Single Site Environment"></iframe>
+    <iframe src="https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/wpallstars/wp-plugin-starter-template-for-ai-coding/main/playground/blueprint.json&_t=1" title="WordPress Playground Single Site Environment"></iframe>
 </body>
 </html>

playground/multisite.html

@@ -21,6 +21,6 @@
     </style>
 </head>
 <body>
-    <iframe src="https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/wpallstars/wp-plugin-starter-template-for-ai-coding/feature/testing-framework/playground/multisite-blueprint.json&_t=24" title="WordPress Playground Multisite Environment"></iframe>
+    <iframe src="https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/wpallstars/wp-plugin-starter-template-for-ai-coding/main/playground/multisite-blueprint.json&_t=1" title="WordPress Playground Multisite Environment"></iframe>
 </body>
 </html>

playground/test.html

@@ -39,12 +39,18 @@
 </head>
 <body>
     <div class="buttons">
-        <button onclick="loadSingleSite()">Single Site</button>
+        <button type="button" id="singleSiteBtn">Single Site</button>
-        <button onclick="loadMultisite()">Multisite</button>
+        <button type="button" id="multisiteBtn">Multisite</button>
     </div>
     <iframe id="playground" src="about:blank" title="WordPress Playground Test Environment"></iframe>
 
     <script>
+        // Use unobtrusive event listeners instead of inline handlers
+        document.addEventListener('DOMContentLoaded', function() {
+            document.getElementById('singleSiteBtn').addEventListener('click', loadSingleSite);
+            document.getElementById('multisiteBtn').addEventListener('click', loadMultisite);
+        });
+
         function loadSingleSite() {
             document.getElementById('playground').src = "https://playground.wordpress.net/?blueprint=" + encodeURIComponent(JSON.stringify(singleSiteBlueprint));
         }