├── .gitattributes ├── .github └── workflows │ └── markdown-link-check.yml ├── LICENSE ├── README.md ├── code-of-conduct.md ├── contributing.md └── mlc_config.json /.gitattributes: -------------------------------------------------------------------------------- 1 | * text=auto 2 | readme.md merge=union 3 | -------------------------------------------------------------------------------- /.github/workflows/markdown-link-check.yml: -------------------------------------------------------------------------------- 1 | name: Check Markdown links 2 | 3 | on: 4 | push: 5 | schedule: 6 | - cron: '0 9 * * *' # 9am every day 7 | 8 | jobs: 9 | markdown-link-check: 10 | runs-on: ubuntu-latest 11 | steps: 12 | - uses: actions/checkout@master 13 | - uses: gaurav-nelson/github-action-markdown-link-check@v1 14 | with: 15 | config-file: 'mlc_config.json' 16 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Creative Commons Legal Code 2 | 3 | CC0 1.0 Universal 4 | 5 | CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE 6 | LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN 7 | ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS 8 | INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES 9 | REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS 10 | PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM 11 | THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED 12 | HEREUNDER. 13 | 14 | Statement of Purpose 15 | 16 | The laws of most jurisdictions throughout the world automatically confer 17 | exclusive Copyright and Related Rights (defined below) upon the creator 18 | and subsequent owner(s) (each and all, an "owner") of an original work of 19 | authorship and/or a database (each, a "Work"). 20 | 21 | Certain owners wish to permanently relinquish those rights to a Work for 22 | the purpose of contributing to a commons of creative, cultural and 23 | scientific works ("Commons") that the public can reliably and without fear 24 | of later claims of infringement build upon, modify, incorporate in other 25 | works, reuse and redistribute as freely as possible in any form whatsoever 26 | and for any purposes, including without limitation commercial purposes. 27 | These owners may contribute to the Commons to promote the ideal of a free 28 | culture and the further production of creative, cultural and scientific 29 | works, or to gain reputation or greater distribution for their Work in 30 | part through the use and efforts of others. 31 | 32 | For these and/or other purposes and motivations, and without any 33 | expectation of additional consideration or compensation, the person 34 | associating CC0 with a Work (the "Affirmer"), to the extent that he or she 35 | is an owner of Copyright and Related Rights in the Work, voluntarily 36 | elects to apply CC0 to the Work and publicly distribute the Work under its 37 | terms, with knowledge of his or her Copyright and Related Rights in the 38 | Work and the meaning and intended legal effect of CC0 on those rights. 39 | 40 | 1. Copyright and Related Rights. A Work made available under CC0 may be 41 | protected by copyright and related or neighboring rights ("Copyright and 42 | Related Rights"). Copyright and Related Rights include, but are not 43 | limited to, the following: 44 | 45 | i. the right to reproduce, adapt, distribute, perform, display, 46 | communicate, and translate a Work; 47 | ii. moral rights retained by the original author(s) and/or performer(s); 48 | iii. publicity and privacy rights pertaining to a person's image or 49 | likeness depicted in a Work; 50 | iv. rights protecting against unfair competition in regards to a Work, 51 | subject to the limitations in paragraph 4(a), below; 52 | v. rights protecting the extraction, dissemination, use and reuse of data 53 | in a Work; 54 | vi. database rights (such as those arising under Directive 96/9/EC of the 55 | European Parliament and of the Council of 11 March 1996 on the legal 56 | protection of databases, and under any national implementation 57 | thereof, including any amended or successor version of such 58 | directive); and 59 | vii. other similar, equivalent or corresponding rights throughout the 60 | world based on applicable law or treaty, and any national 61 | implementations thereof. 62 | 63 | 2. Waiver. To the greatest extent permitted by, but not in contravention 64 | of, applicable law, Affirmer hereby overtly, fully, permanently, 65 | irrevocably and unconditionally waives, abandons, and surrenders all of 66 | Affirmer's Copyright and Related Rights and associated claims and causes 67 | of action, whether now known or unknown (including existing as well as 68 | future claims and causes of action), in the Work (i) in all territories 69 | worldwide, (ii) for the maximum duration provided by applicable law or 70 | treaty (including future time extensions), (iii) in any current or future 71 | medium and for any number of copies, and (iv) for any purpose whatsoever, 72 | including without limitation commercial, advertising or promotional 73 | purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each 74 | member of the public at large and to the detriment of Affirmer's heirs and 75 | successors, fully intending that such Waiver shall not be subject to 76 | revocation, rescission, cancellation, termination, or any other legal or 77 | equitable action to disrupt the quiet enjoyment of the Work by the public 78 | as contemplated by Affirmer's express Statement of Purpose. 79 | 80 | 3. Public License Fallback. Should any part of the Waiver for any reason 81 | be judged legally invalid or ineffective under applicable law, then the 82 | Waiver shall be preserved to the maximum extent permitted taking into 83 | account Affirmer's express Statement of Purpose. In addition, to the 84 | extent the Waiver is so judged Affirmer hereby grants to each affected 85 | person a royalty-free, non transferable, non sublicensable, non exclusive, 86 | irrevocable and unconditional license to exercise Affirmer's Copyright and 87 | Related Rights in the Work (i) in all territories worldwide, (ii) for the 88 | maximum duration provided by applicable law or treaty (including future 89 | time extensions), (iii) in any current or future medium and for any number 90 | of copies, and (iv) for any purpose whatsoever, including without 91 | limitation commercial, advertising or promotional purposes (the 92 | "License"). The License shall be deemed effective as of the date CC0 was 93 | applied by Affirmer to the Work. Should any part of the License for any 94 | reason be judged legally invalid or ineffective under applicable law, such 95 | partial invalidity or ineffectiveness shall not invalidate the remainder 96 | of the License, and in such case Affirmer hereby affirms that he or she 97 | will not (i) exercise any of his or her remaining Copyright and Related 98 | Rights in the Work or (ii) assert any associated claims and causes of 99 | action with respect to the Work, in either case contrary to Affirmer's 100 | express Statement of Purpose. 101 | 102 | 4. Limitations and Disclaimers. 103 | 104 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 105 | surrendered, licensed or otherwise affected by this document. 106 | b. Affirmer offers the Work as-is and makes no representations or 107 | warranties of any kind concerning the Work, express, implied, 108 | statutory or otherwise, including without limitation warranties of 109 | title, merchantability, fitness for a particular purpose, non 110 | infringement, or the absence of latent or other defects, accuracy, or 111 | the present or absence of errors, whether or not discoverable, all to 112 | the greatest extent permissible under applicable law. 113 | c. Affirmer disclaims responsibility for clearing rights of other persons 114 | that may apply to the Work or any use thereof, including without 115 | limitation any person's Copyright and Related Rights in the Work. 116 | Further, Affirmer disclaims responsibility for obtaining any necessary 117 | consents, permissions or other rights required for any use of the 118 | Work. 119 | d. Affirmer understands and acknowledges that Creative Commons is not a 120 | party to this document and has no duty or obligation with respect to 121 | this CC0 or use of the Work. 122 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Awesome WordPress Playground [![Awesome](https://awesome.re/badge.svg)](https://awesome.re) 2 | 3 | [WordPress Playground](https://wordpress.org/playground/) is [WordPress](https://wordpress.org/) in one click. It's a platform that lets you run WordPress instantly on any device without a host. It’s your place to build, experiment, test, and grow. 4 | 5 | This list collects awesome uses of playground and awesome tools to build with it. 6 | 7 | ## Contents 8 | 9 | - [Official Links](#official-links) 10 | - [Applications](#applications) 11 | - [Building Blueprints](#building-blueprints) 12 | - [Tools](#tools) 13 | - [Tutorials & Guides](#tutorials--guides) 14 | - [Contribute](#contribute) 15 | 16 | 17 | ## Official Links 18 | 19 | - [WordPress Playground](https://playground.wordpress.net/) - Try WordPress Playground here. 20 | - [WordPress.org/Playground](https://wordpress.org/playground/) - WordPress Playground explained on WordPress.org. 21 | - [WordPress Playground on GitHub](https://github.com/WordPress/wordpress-playground) - The source code for the playground. 22 | - [Playground Tools on GitHub](https://github.com/WordPress/playground-tools) - Tools and applications built using WordPress Playground. 23 | 24 | ## Applications 25 | 26 | This is where WordPress Playground powers applications that were not possible or much harder without it. 27 | 28 | - [Gutenberg Pull Request Previewer](https://playground.wordpress.net/wordpress.html) - Run a [Gutenberg](https://github.com/WordPress/gutenberg/) Pull Request in a playground to test it. 29 | - [Playground inside Playground](https://playground.wordpress.net/#{%22landingPage%22:%22/wp-admin/post.php?post=1&action=edit%22,%22steps%22:[{%22step%22:%22login%22},{%22step%22:%22installPlugin%22,%22pluginZipFile%22:{%22resource%22:%22wordpress.org/plugins%22,%22slug%22:%22interactive-code-block%22}},{%22step%22:%22writeFile%22,%22path%22:%22/wordpress/post.txt%22,%22data%22:%22%3C!--%20wp:wordpress-playground/playground%20{\%22codeEditor\%22:true,\%22files\%22:[{\%22name\%22:\%22index.php\%22,\%22contents\%22:\%22%3C?php\\\\n/**\\\\n%20*%20Plugin%20Name:%20A%20WordPress%20plugin\\\\n%20*/\\\\nadd_action('init',%20function()%20{\\\\n%20%20update_option('blogname',%20'This%20is%20a%20Playground%20demo!');\\\\n});\%22}]}%20/--%3E%22},{%22step%22:%22runPHP%22,%22code%22:%22%3C?php%20require%20'/wordpress/wp-load.php';%20kses_remove_filters();%20wp_update_post(['ID'=%3E1,'post_title'%20=%3E%20'Playground%20Plugin%20Editor',%20'post_content'=%3Efile_get_contents('/wordpress/post.txt')]);%22}]}) - Uses the interactive code block to do a live preview of the code. 30 | - [Playground Synchronization](https://playground.wordpress.net/demos/time-traveling.html) - Record changes made in one playground and play them back in a second playground. 31 | - [Time Traveling](https://playground.wordpress.net/demos/time-traveling.html) - Record changes made in one playground and play them back in a second playground. 32 | - [Translate Live](https://translate.wordpress.org/projects/wp-plugins/friends/dev/de/default/playground/) - Inline Translation for WordPress plugins and themes, here is an example of the WordPress Plugin [Friends](https://wordpress.org/plugins/friends/) and the language German. 33 | - [WordPress Block Development Examples](https://wordpress.github.io/block-development-examples) – Learn about Block Development through code examples and live demos. 34 | - [WordPress Core Pull Request Previewer](https://playground.wordpress.net/wordpress.html) - Run a [WordPress Core](https://github.com/WordPress/wordpress-develop/) Pull Request in a playground to test it. 35 | - [WP-CLI in the browser](https://playground.wordpress.net/demos/wp-cli.html) - Puts a wp-cli commandline above a playground to manipulate it. 36 | 37 | ## Building Blueprints 38 | 39 | - [Blueprint Builder](https://playground.wordpress.net/builder/builder.html) - A codepen-like environment for building blueprints with autocomplete. 40 | - [Blueprints Gallery](https://github.com/WordPress/blueprints/blob/trunk/GALLERY.md) - A directory of blueprints that demonstrate different ways to use them. 41 | - [Step Library](https://akirk.github.io/playground-step-library/) - Easily build blueprints by joining more complex steps together. 42 | 43 | ## Tools 44 | 45 | - [Edit Visually Browser Extension](https://github.com/WordPress/playground-tools/tree/trunk/packages/edit-visually-browser-extension) - Edit GitHub issue descriptions and other text formats using WordPress blocks in Playground. 46 | - [Museum of Block Art](https://block-museum.com/) - In this museum, the blocks are demo'ed using WordPress Playground. 47 | - [Playground Block for Gutenberg](https://wordpress.org/plugins/interactive-code-block/) - A block that embeds a playground in your post. 48 | - [WordPress Playground for VS Code](https://marketplace.visualstudio.com/items?itemName=WordPressPlayground.wordpress-playground) - Run a WordPress development server without any dependencies. 49 | - [wp-now](https://www.npmjs.com/package/@wp-now/wp-now) - A CLI tool to streamline the process of setting up a local WordPress environment. 50 | 51 | ## Tutorials & Guides 52 | 53 | - [WordPress Playground Documentation](https://wordpress.github.io/wordpress-playground/) - An introduction to WordPress Playground. 54 | - [WordPress Playground README](https://github.com/WordPress/wordpress-playground?#wordpress-playground-and-php-wasm-webassembly) - An explanation of WordPress Playground and how to get started. 55 | - [Blueprints 101](https://github.com/WordPress/blueprints/blob/blueprints-crash-course/docs/index.md) - A Blueprints crash course. 56 | - [Query API](https://wordpress.github.io/wordpress-playground/developers/apis/query-api) - How to configure playground.wordpress.net via query parameters. 57 | - [Blueprint API](https://wordpress.github.io/wordpress-playground/blueprints/data-format) - How to create and use blueprints. 58 | - [Playground on WordPress.tv](https://wordpress.tv/tag/wordpress-playground/) - Talks from WordCamps on WordPress Playground. 59 | 60 | ## Contribute 61 | 62 | Contributions welcome! Read the [contribution guidelines](contributing.md) first. 63 | -------------------------------------------------------------------------------- /code-of-conduct.md: -------------------------------------------------------------------------------- 1 | # WordPress's Community Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation. 6 | 7 | We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. 8 | 9 | ### Our Expectations 10 | 11 | Examples of behavior that contributes to a positive environment for our community include: 12 | 13 | Demonstrating empathy and kindness toward other people 14 | Being respectful of differing opinions, viewpoints, and experiences 15 | Giving and gracefully accepting constructive feedback 16 | Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience 17 | Focusing on what is best not just for us as individuals, but for the overall community 18 | 19 | Examples of unacceptable behavior include: 20 | 21 | The use of sexualized language or imagery, and sexual attention or advances of any kind 22 | Insulting or derogatory comments, taunting or baiting, and personal or political attacks 23 | Public or private harassment 24 | Publishing others’ private information, such as a physical or email address, without their explicit permission 25 | Other conduct which could reasonably be considered inappropriate in a professional setting 26 | 27 | **Influencing Unacceptable Behavior** 28 | 29 | Influencing or inciting unacceptable behavior and activities will be viewed as the behavior and activities themselves, and result in the same consequences. 30 | 31 | **Retaliation** 32 | 33 | Retaliation against those who raise concerns or make reports in good faith will not be tolerated. 34 | 35 | ### Interpretation 36 | 37 | These expectations are not exhaustive or complete. Rather, they serve to distill our common understanding of a collaborative, shared environment and goals. We expect it to be followed in spirit as much as in letter. 38 | 39 | ### Enforcement Responsibilities 40 | 41 | Community leaders (such as team reps, component maintainers, organizers, and project leads) are responsible for clarifying and enforcing our standards of acceptable behavior; they will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. 42 | 43 | Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, documentation edits, issues, videos, presentations, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate. 44 | 45 | ### Scope 46 | 47 | This Code of Conduct applies within all community spaces (virtual and in-person) and applies when an individual officially represents the community in public spaces. Examples of representing our community include using an official email address, posting via an official social media account, or representing WordPress as an organizer, speaker, or volunteer at an online or offline event. 48 | 49 | ### Enforcement 50 | 51 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the WordPress Incident Response Team at reports@wordpress.org. All complaints will be reviewed and investigated promptly and fairly. 52 | 53 | All community leaders are obligated to respect the privacy and security of the reporter of any incident. 54 | 55 | ### Enforcement Guidelines 56 | 57 | Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct: 58 | 59 | ### 1. Correction 60 | 61 | **Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community. 62 | 63 | **Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation, explaining why the behavior was inappropriate. A public apology may be requested. 64 | 65 | ### 2. Warning 66 | 67 | **Community Impact**: A violation through a single incident or series of actions. 68 | 69 | **Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban. 70 | 71 | ### 3. Temporary Ban 72 | 73 | **Community Impact**: A serious violation of community standards, including sustained inappropriate behavior. 74 | 75 | **Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban. 76 | 77 | ### 4. Permanent Ban 78 | 79 | **Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. 80 | 81 | **Consequence**: A permanent ban from any sort of public interaction within the community. 82 | 83 | ### Modifications to the Community CoC 84 | 85 | This Code of Conduct may be amended from time to time, as may the procedures it sets out where appropriate in a particular case. Your agreement to comply with the Code of Conduct will be deemed agreement to any changes to it. If you would like to suggest updates to this document, you can do so by emailing support@wordcamp.org. 86 | 87 | ### Attribution 88 | 89 | This is a copy of the [WordPress Community Code of Conduct](https://make.wordpress.org/handbook/community-code-of-conduct/). It is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html. 90 | 91 | Community Impact Guidelines were inspired by [Mozilla’s code of conduct enforcement ladder](https://github.com/mozilla/diversity). 92 | 93 | For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations. 94 | -------------------------------------------------------------------------------- /contributing.md: -------------------------------------------------------------------------------- 1 | # Contribution Guidelines 2 | 3 | Please note that this project is released with a 4 | [Contributor Code of Conduct](code-of-conduct.md). By participating in this 5 | project you agree to abide by its terms. 6 | 7 | --- 8 | 9 | Ensure your pull request adheres to the following guidelines: 10 | 11 | - Make sure you take care of this 12 | - And this as well 13 | - And don't forget to check this 14 | 15 | Thank you for your suggestions! 16 | 17 | 18 | ## Updating your PR 19 | 20 | A lot of times, making a PR adhere to the standards above can be difficult. 21 | If the maintainers notice anything that we'd like changed, we'll ask you to 22 | edit your PR before we merge it. There's no need to open a new PR, just edit 23 | the existing one. If you're not sure how to do that, 24 | [here is a guide](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md) 25 | on the different ways you can update your PR so that we can merge it. 26 | -------------------------------------------------------------------------------- /mlc_config.json: -------------------------------------------------------------------------------- 1 | { 2 | "ignorePatterns": [ 3 | ], 4 | "timeout": "20s", 5 | "retryOn429": true, 6 | "retryCount": 5, 7 | "fallbackRetryDelay": "30s", 8 | "aliveStatusCodes": [200, 20, 403] 9 | } 10 | --------------------------------------------------------------------------------