Open
Conversation
…lf-hosted Playground documentation
…led explanations on browser behavior, performance expectations, and persistence options. Added a new image for the refresh button and improved section headings for clarity.
fellyph
requested review from
adamziel and
Copilot
and removed request for
Copilot
brandonpayton
approved these changes
Feb 4, 2026
Member
brandonpayton
left a comment
brandonpayton
left a comment
There was a problem hiding this comment.
@fellyph I left some suggestions but this looks great overall. Thank you!
Comment on lines
15
to
19
| ### What to expect | ||
|
|
||
| - **Initial setup complexity**: Building and deploying Playground involves multiple steps. Allow time for troubleshooting during your first deployment. | ||
| - **Static file hosting**: Playground is primarily static files (HTML, JS, WASM) with minimal server-side requirements. | ||
| - **Browser-based execution**: All WordPress processing happens in the user's browser via WebAssembly—your server only delivers files. |
packages/docs/site/docs/developers/23-architecture/18-host-your-own-playground.md
Outdated
Show resolved
Hide resolved
packages/docs/site/docs/developers/23-architecture/18-host-your-own-playground.md
Outdated
Show resolved
Hide resolved
packages/docs/site/docs/developers/23-architecture/18-host-your-own-playground.md
Outdated
Show resolved
Hide resolved
| | Fresh WordPress (no plugins) | 5-10 seconds | | ||
| | With small plugins | 10-20 seconds | | ||
| | With large plugins (e.g., WooCommerce) | 30-60 seconds | | ||
| | On mobile devices | 1.5-2x slower than desktop | |
Member
There was a problem hiding this comment.
I'm sure some folks will complain that their experience varies from these estimates, but it seems so good to have these to set expectations.
Collaborator
Author
There was a problem hiding this comment.
can we set 5+ seconds, 10+ seconds and 30+ ?
Collaborator
Author
There was a problem hiding this comment.
@brandonpayton I will include this image:
…r-own-playground.md Co-authored-by: Brandon Payton <brandon@happycode.net>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR enhances documentation for self-hosting WordPress Playground and clarifies its limitations, focusing on setup expectations, performance characteristics, and troubleshooting guidance.
Changes:
- Added comprehensive pre-deployment guidance covering complexity, performance factors, and browser compatibility
- Expanded limitations documentation with clearer explanations of temporary instances, persistence options, and performance expectations
- Introduced production deployment checklist and troubleshooting section for common self-hosting issues
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| packages/docs/site/docs/developers/24-limitations/01-index.md | Added anchor links, expanded temporary instance explanation with persistence instructions, added performance expectations table, and improved browser support details |
| packages/docs/site/docs/developers/23-architecture/18-host-your-own-playground.md | Added "Before you start" section with setup expectations and browser compatibility matrix, production deployment checklist, and troubleshooting guide |
Comments suppressed due to low confidence (1)
packages/docs/site/docs/developers/24-limitations/01-index.md:1
- Corrected spacing in 'blueprints,for' to 'blueprints, for'.
---
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…m/WordPress/wordpress-playground into updating-host-own-playground-page
…g load time tables with a performance graph image. Updated the refresh button image across multiple language versions.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request significantly improves the documentation for self-hosting and using WordPress Playground by clarifying setup expectations, adding troubleshooting guidance, and expanding details on browser compatibility and performance. The updates also enhance the limitations documentation with clearer explanations, practical tips, and improved formatting for easier navigation.
Improvements to self-hosting documentation:
Enhancements to limitations and usage documentation: