Symfony Playground Blueprint

[adamziel]

What it does

Adds a Symfony Package Radar Blueprint to the community gallery.

The demo runs a bundled Symfony app in Playground with preferredVersions.wp set to false, so it does not download WordPress. It shows attribute routes, autowired controller arguments, Twig rendering, a JSON route, and Symfony HttpClient running through Playground networking.

Rationale

Blueprints can demonstrate PHP applications beyond WordPress. This example gives the gallery a small, framework-specific app that starts quickly because the Symfony app and Composer dependencies are bundled in symfony-package-radar.zip.

Implementation

• Adds blueprints/symfony-package-radar/blueprint.json.
• Bundles the Symfony app and its vendor/ directory in symfony-package-radar.zip.
• Uses a bundled ZIP resource plus an unzip step instead of downloading Composer packages at runtime.
• Falls back to cached package metadata if Packagist networking or TLS is unavailable.
• Simplifies the demo UI while keeping the story: PHP-only Symfony, package metadata, editable controller source, and a JSON route.
• Styles the highlighted controller source with the Dracula dark syntax palette and keeps the JSON route link short.
• Includes a gallery screenshot.

Testing instructions

npm install
CHANGED_FILES=$'blueprints/symfony-package-radar/blueprint.json\nblueprints/symfony-package-radar/screenshot.jpg\nblueprints/symfony-package-radar/symfony-package-radar.zip' \
GITHUB_BRANCH=add-symfony-package-radar-demo \
npm run validate:pr-blueprints

npx @wp-playground/cli@latest server \
  --port=9400 \
  --blueprint=blueprints/symfony-package-radar/blueprint.json \
  --blueprint-may-read-adjacent-files

Then open http://127.0.0.1:9400/symfony-package-radar/public/index.php.

[github-actions]

Test using WordPress Playground

The changes in this pull request can be previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time one of the links below is clicked.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Blueprint previews

• Open symfony-package-radar in WordPress Playground