You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The embed used an <iframe>, and iframes are typically difficult to embed in posts because of security issues, KSES filtering, and user permissions. However, with Playground, we get a sandboxed environment that can run WordPress blocks, plugins, and even clone the current site.
Playground could, therefore, power the following features:
Use X block without installing it
Create a page with a feature from Y plugin without installing it
Build a custom block directly on the website
Easily embed external content
A "Playground editor role" who can fork the site, make changes, and propose them back – similar to pull requests but native to WordPress and without git.
The text was updated successfully, but these errors were encountered:
I recently managed to embed this live Playground Mindmap in a blog post using the Playground block:
https://whimsical.com/wordpress-playground-mindmap-3hVkrfvWsDvQXSPEDnUGcN
The embed used an
<iframe>
, and iframes are typically difficult to embed in posts because of security issues, KSES filtering, and user permissions. However, with Playground, we get a sandboxed environment that can run WordPress blocks, plugins, and even clone the current site.Playground could, therefore, power the following features:
The text was updated successfully, but these errors were encountered: