Automatically enabled plugin using the mu-plugins folder

[carstingaxion]

Hello 👋🏻

I’d like to suggest adding a playground, that skips the plugin activation step because a plugin can also directly placed in the mu-plugins folder.

We could for sure load hello-dolly here for demo-purposes, but we could also use a small plugin with a different purpose for that.

—-

Maybe this little block-variation of a core/paragraph block, that makes use of the new Block Bindings API to provide data about the current post type.

The block can show all post type labels including its slug and/or the post_type_supports for the current post type.

https://gist.github.com/carstingaxion/f98c213aad40d6413fe50eac1cc92228

[github-actions]

Test using WordPress Playground

The changes in this pull request can 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

• The Plugin and Theme Directories cannot be accessed within Playground.
• 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 the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

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

Test this pull request with WordPress Playground.

[bgrgicak]

One of our existing blueprints uses a mu-plugin. Would this be a good example? If yes, should we update the description?