[Docs] Document Symfony apps in Playground without WordPress

packages/docs/site/docs/main/guides/index.md

@@ -13,6 +13,10 @@ In this section we present a selection of guides that will help you to both work
 
 Embed editable, runnable PHP and WordPress examples in any web page with the `<php-snippet>` web component. The guide covers custom Blueprints, expected output, pure-PHP snippets, runtime sharing, and the standalone PHP Playground.
 
+## [Run PHP frameworks in Playground](/guides/php-frameworks)
+
+Use Playground as a generic browser-based PHP runtime. This guide shows how to skip the WordPress download, load a bundled Symfony app with a Blueprint, and run it from a `<php-snippet>`.
+
 ## [WordPress Playground for Everyone](/guides/playground-for-everyone)
 
 Think Playground is only for developers? Think again. This guide shows how WordPress Playground helps beginners, site owners, and everyday users experiment safely — no technical expertise required.

packages/docs/site/docs/main/guides/php-frameworks.md

@@ -0,0 +1,185 @@
+---
+title: Run PHP frameworks in Playground
+slug: /guides/php-frameworks
+description: Use WordPress Playground as a browser-based PHP runtime for frameworks and apps that are not WordPress.
+sidebar_class_name: navbar-build-item
+---
+
+import { PhpCodeSnippetExample } from '@site/src/components/PhpCodeSnippetLiveExample';
+
+# Run PHP frameworks in Playground
+
+WordPress Playground is also a browser-based PHP runtime. WordPress is the
+most common app it boots, but a Blueprint can skip the WordPress download,
+write any PHP files into the virtual filesystem, and run a framework such as
+Symfony.
+
+This guide shows the shape of that setup. Use it when you want a shareable demo,
+a docs example, or a quick compatibility check for a PHP app that does not need
+a server, database, Node.js, Sass, or a local Composer install.
+
+## What changes when you skip WordPress
+
+Set `preferredVersions.wp` to `false` in a Blueprint, or `wp="none"` on a
+`<php-snippet>`. Playground still downloads PHP, mounts a writable filesystem,
+runs Blueprint steps, and supports networking when `features.networking` is
+`true`. It just does not download or boot WordPress.
+
+That makes Playground useful for generic PHP examples:
+
+- PHP libraries that need a real filesystem.
+- Framework demos that can run behind `public/index.php`.
+- Documentation snippets that should execute in the browser.
+- Reproducible bug reports for PHP code that is not WordPress-specific.
+
+## Try a Symfony app
+
+The example below uses a Blueprint to download and unzip a bundled Symfony app
+into `/app`. Then a `<php-snippet>` boots the Symfony kernel and renders the
+dashboard route. The app's Composer dependencies include the WordPress HTML API,
+so the snippet can read the `<h1>` with `WP_HTML_Processor` without installing or
+booting WordPress.
+
+<PhpCodeSnippetExample name="symfonyBlueprint" />
+
+Here is the complete embed:
+
+<!-- prettier-ignore-start -->
+
+```html
+<script type="module" src="https://playground.wordpress.net/php-code-snippet.js"></script>
+
+<script id="symfony-blueprint" type="application/json">
+{
+  "features": {
+    "networking": true
+  },
+  "steps": [
+    {
+      "step": "unzip",
+      "zipFile": {
+        "resource": "url",
+        "url": "https://wordpress.github.io/blueprints/blueprints/symfony-package-radar/symfony-package-radar.zip?v=html-api-2026-06-08"
+      },
+      "extractToPath": "/app"
+    }
+  ]
+}
+</script>
+
+<php-snippet name="run-symfony.php" wp="none" blueprint="symfony-blueprint">
+  <script type="application/x-php">
+<?php
+require '/app/symfony-package-radar/vendor/autoload.php';
+
+use App\Kernel;
+use Symfony\Component\HttpFoundation\Request;
+
+$kernel = new Kernel( 'prod', false );
+$request = Request::create( '/' );
+$response = $kernel->handle( $request );
+
+$page_title = get_first_h1_text( $response->getContent() );
+
+echo 'HTTP ' . $response->getStatusCode() . PHP_EOL;
+echo 'Symfony page: ' . $page_title . PHP_EOL;
+echo 'WordPress installed: ';
+echo file_exists( '/wordpress/wp-load.php' ) ? 'yes' : 'no';
+
+$kernel->terminate( $request, $response );
+
+/**
+ * The app's Composer dependencies include the WordPress HTML API, so the
+ * snippet can read the <h1> with WP_HTML_Processor without installing or
+ * booting WordPress.
+ */
+function get_first_h1_text( string $html ): string {
+	$processor = WP_HTML_Processor::create_fragment( $html );
+	if ( ! $processor->next_tag( 'H1' ) ) {
+		return 'unknown';
+	}
+
+	$text = '';
+	while ( $processor->next_token() ) {
+		if ( 'H1' === $processor->get_tag() && $processor->is_tag_closer() ) {
+			break;
+		}
+		if ( '#text' === $processor->get_token_type() ) {
+			$text .= $processor->get_modifiable_text();
+		}
+	}
+
+	return trim( $text );
+}
+  </script>
+  <script type="text/expected-output">
+HTTP 200
+Symfony page: Symfony Playground
+WordPress installed: no
+  </script>
+</php-snippet>
+```
+
+<!-- prettier-ignore-end -->
+
+The same app is also available as a full Playground page:
+
+[Open the Symfony Package Radar demo](https://playground.wordpress.net/?blueprint-url=https%3A%2F%2Fwordpress.github.io%2Fblueprints%2Fblueprints%2Fsymfony-package-radar%2Fblueprint.json)
+
+## Package the app as a ZIP
+
+For framework demos, prefer a ZIP that already contains `vendor/`. That keeps
+the Playground startup path short and avoids asking every visitor to wait for
+Composer, Git, and package registry downloads. The Symfony demo uses that path to
+bundle both Symfony and a Composer-installed copy of the WordPress HTML API; it
+still does not include a WordPress install.
+
+For snippets or CLI runs, a small Blueprint can install the app into `/app` with
+one step:
+
+```json
+{
+	"$schema": "https://playground.wordpress.net/blueprint-schema.json",
+	"landingPage": "/symfony-package-radar/public/index.php",
+	"preferredVersions": {
+		"php": "8.4",
+		"wp": false
+	},
+	"features": {
+		"networking": true
+	},
+	"steps": [
+		{
+			"step": "unzip",
+			"zipFile": {
+				"resource": "bundled",
+				"path": "./symfony-package-radar.zip"
+			},
+			"extractToPath": "/app"
+		}
+	]
+}
+```
+
+Use `bundled` resources when the ZIP ships next to `blueprint.json`, or use a
+`url` resource when the ZIP is hosted separately. See [Blueprint bundles](/blueprints/bundles)
+for packaging details.
+
+For a full-page Playground website, use a Blueprint like the gallery demo. It
+adds a tiny router at the Playground document root so the Symfony `public/`
+directory can respond to browser requests.
+
+## Keep the demo browser-friendly
+
+A Playground-hosted framework demo works best when it:
+
+- Does not require a long-running background process.
+- Stores generated files under the virtual filesystem.
+- Avoids native extensions that are not compiled into PHP.wasm.
+- Avoids frontend build steps at runtime.
+- Keeps network calls optional or resilient, because browsers may require CORS
+  proxying for third-party services.
+
+Those constraints still leave plenty of room for real framework behavior:
+controllers, routing, dependency injection, templates, forms, HTTP clients, and
+plain PHP libraries all work when their PHP dependencies are available.

packages/docs/site/sidebars.js

@@ -46,6 +46,7 @@ const sidebars = {
 					},
 					items: [
 						'main/guides/php-code-snippets',
+						'main/guides/php-frameworks',
 						'main/guides/agent-skill-wp-playground',
 						'main/guides/wordpress-native-ios-app',
 						'main/guides/for-plugin-developers',

packages/docs/site/src/components/PhpCodeSnippetLiveExample.examples.ts

@@ -187,6 +187,76 @@ echo get_bloginfo( 'version' );
   <script type="text/expected-output">
 6.8
   </script>
+</php-snippet>`,
+	symfonyBlueprint: String.raw`<script id="symfony-blueprint-preview" type="application/json">
+{
+  "features": {
+    "networking": true
+  },
+  "steps": [
+    {
+      "step": "unzip",
+      "zipFile": {
+        "resource": "url",
+        "url": "https://wordpress.github.io/blueprints/blueprints/symfony-package-radar/symfony-package-radar.zip?v=html-api-2026-06-08"
+      },
+      "extractToPath": "/app"
+    }
+  ]
+}
+</script>
+
+<php-snippet name="run-symfony.php" wp="none" blueprint="symfony-blueprint-preview">
+  <script type="application/x-php">
+<?php
+require '/app/symfony-package-radar/vendor/autoload.php';
+
+use App\Kernel;
+use Symfony\Component\HttpFoundation\Request;
+
+$kernel = new Kernel('prod', false);
+$request = Request::create('/');
+$response = $kernel->handle($request);
+
+$pageTitle = get_first_h1_text($response->getContent());
+
+echo 'HTTP ' . $response->getStatusCode() . PHP_EOL;
+echo 'Symfony page: ' . $pageTitle . PHP_EOL;
+echo 'WordPress installed: ';
+echo file_exists('/wordpress/wp-load.php') ? 'yes' : 'no';
+
+$kernel->terminate($request, $response);
+
+/**
+ * The app's Composer dependencies include the WordPress HTML API, so the
+ * snippet can read the <h1> with WP_HTML_Processor without installing or
+ * booting WordPress.
+ */
+function get_first_h1_text(string $html): string
+{
+    $processor = WP_HTML_Processor::create_fragment($html);
+    if (!$processor->next_tag('H1')) {
+        return 'unknown';
+    }
+
+    $text = '';
+    while ($processor->next_token()) {
+        if ('H1' === $processor->get_tag() && $processor->is_tag_closer()) {
+            break;
+        }
+        if ('#text' === $processor->get_token_type()) {
+            $text .= $processor->get_modifiable_text();
+        }
+    }
+
+    return trim($text);
+}
+  </script>
+  <script type="text/expected-output">
+HTTP 200
+Symfony page: Symfony Playground
+WordPress installed: no
+  </script>
 </php-snippet>`,
 	illustration: String.raw`<php-snippet name="illustration.php" runnable="false">
   <script type="application/x-php">

packages/docs/site/src/components/PhpCodeSnippetLiveExample.tsx

@@ -1,10 +1,13 @@
 import React, { useEffect, useState } from 'react';
 import type { ExampleName } from './PhpCodeSnippetLiveExample.examples';
 
-// php-code-snippet.js used to be served with a one-year browser cache.
-// Keep this query so docs previews don't reuse stale pre-editable-default copies.
+// In dev, load the local Playground website script so docs previews exercise
+// uncommitted php-code-snippet.js changes. Production docs still use the hosted
+// script and keep a query string to avoid stale one-year browser caches.
 const SCRIPT_URL =
-	'https://playground.wordpress.net/php-code-snippet.js?v=editable-by-default';
+	process.env.NODE_ENV === 'development'
+		? 'http://127.0.0.1:5400/website-server/php-code-snippet.js'
+		: 'https://playground.wordpress.net/php-code-snippet.js?v=selected-text-visible';
 
 function usePhpSnippetScript() {
 	useEffect(() => {

packages/playground/website/public/php-code-snippet.js

@@ -671,7 +671,7 @@ pre {
 	caret-color: #24292f;
 	overflow: hidden;
 }
-.editor textarea::selection { background: #cfe7ff; color: transparent; }
+.editor textarea::selection { background: #cfe7ff; color: #24292f; }
 .output {
 	display: none;
 	border-top: 1px solid #e1e4e8;