{"id":4412,"date":"2026-05-23T12:20:24","date_gmt":"2026-05-23T10:20:24","guid":{"rendered":"https:\/\/davidperezgar.com\/en\/?p=4412"},"modified":"2026-05-23T12:38:33","modified_gmt":"2026-05-23T10:38:33","slug":"preview-of-plugins-in-wordpress-playground-directly-from-the-pull-request","status":"publish","type":"post","link":"https:\/\/davidperezgar.com\/en\/blog\/preview-of-plugins-in-wordpress-playground-directly-from-the-pull-request\/","title":{"rendered":"Preview plugins in WordPress Playground directly from the Pull Request"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">When someone opens a PR in a WordPress plugin, the usual process for reviewing it involves downloading the branch, installing it locally, activating the plugin, and testing the changes by hand. That has frictions: you have to have a prepared local environment and dedicate time to install something that is perhaps half broken. If the reviewer is not a developer, they can&#8217;t do it directly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">With this setup, the PR itself generates a link that opens the plugin running in the browser. One click, and you&#8217;re already trying.<\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_83 counter-hierarchy ez-toc-counter ez-toc-white ez-toc-container-direction\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Tabla de contenidos<\/p>\n<label for=\"ez-toc-cssicon-toggle-item-6a11d784e7cdc\" class=\"ez-toc-cssicon-toggle-label\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/label><input type=\"checkbox\"  id=\"ez-toc-cssicon-toggle-item-6a11d784e7cdc\"  aria-label=\"Toggle\" \/><nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/davidperezgar.com\/en\/blog\/preview-of-plugins-in-wordpress-playground-directly-from-the-pull-request\/#What_is_WordPress_Playground\" >What is WordPress Playground?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/davidperezgar.com\/en\/blog\/preview-of-plugins-in-wordpress-playground-directly-from-the-pull-request\/#How_the_complete_system_works\" >How the complete system works<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/davidperezgar.com\/en\/blog\/preview-of-plugins-in-wordpress-playground-directly-from-the-pull-request\/#Step-by-step_guide\" >Step-by-step guide<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/davidperezgar.com\/en\/blog\/preview-of-plugins-in-wordpress-playground-directly-from-the-pull-request\/#1_Create_the_folder_structure\" >1. Create the folder structure<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/davidperezgar.com\/en\/blog\/preview-of-plugins-in-wordpress-playground-directly-from-the-pull-request\/#2_Add_build-distyml\" >2. Add build-dist.yml<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/davidperezgar.com\/en\/blog\/preview-of-plugins-in-wordpress-playground-directly-from-the-pull-request\/#3_Add_playground-previewyml\" >3. Add playground-preview.yml<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/davidperezgar.com\/en\/blog\/preview-of-plugins-in-wordpress-playground-directly-from-the-pull-request\/#4_Check_workflow_permissions\" >4. Check workflow permissions<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/davidperezgar.com\/en\/blog\/preview-of-plugins-in-wordpress-playground-directly-from-the-pull-request\/#5_Make_the_first_push_and_check\" >5. Make the first push and check<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/davidperezgar.com\/en\/blog\/preview-of-plugins-in-wordpress-playground-directly-from-the-pull-request\/#6_Open_a_PR_and_wait_for_the_automatic_comment\" >6. Open a PR and wait for the automatic comment<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/davidperezgar.com\/en\/blog\/preview-of-plugins-in-wordpress-playground-directly-from-the-pull-request\/#Customize_the_blueprint\" >Customize the blueprint<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/davidperezgar.com\/en\/blog\/preview-of-plugins-in-wordpress-playground-directly-from-the-pull-request\/#Install_a_dependency_plugin\" >Install a dependency plugin<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/davidperezgar.com\/en\/blog\/preview-of-plugins-in-wordpress-playground-directly-from-the-pull-request\/#Create_Test_Data_with_WP-CLI\" >Create Test Data with WP-CLI<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/davidperezgar.com\/en\/blog\/preview-of-plugins-in-wordpress-playground-directly-from-the-pull-request\/#Fix_WordPress_or_PHP_version\" >Fix WordPress or PHP version<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/davidperezgar.com\/en\/blog\/preview-of-plugins-in-wordpress-playground-directly-from-the-pull-request\/#Important_Notes\" >Important Notes<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_is_WordPress_Playground\"><\/span>What is WordPress Playground?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress Playground is a WordPress environment that runs entirely in-browser, serverless. Use WebAssembly (WASM) to run PHP directly on the client. You don&#8217;t need Docker, XAMPP, or anything installed locally.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Anyone can open a URL and have a functional WordPress in seconds, with the plugin installed and activated. When you close the tab, everything disappears. No trace, no facilities, no conflicts.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This makes it perfect for code reviews, quick demos, and plugin testing without compromising any real environment.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_the_complete_system_works\"><\/span>How the complete system works<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">There are three pieces that fit together:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\"><strong>build-dist.yml<\/strong> \u2014 runs on every push. It installs the Composer dependencies without <code>--dev<\/code>, generates a <code>blueprint.json<\/code> pointing to that particular branch, and forces a push to a branch <code>dist\/nombre-rama<\/code>. It also deletes the dist branch when the original is deleted.<\/li>\n\n\n\n<li class=\"\"><strong>playground-preview.yml<\/strong> \u2014 Runs when a PR is opened, reopened, or updated. Build the Playground URL with the dist branch blueprint and post or update a comment in the PR. Use HTML marker so you don&#8217;t duplicate comments.<\/li>\n\n\n\n<li class=\"\"><strong>pr-blueprint.json<\/strong> \u2014 blueprint template to check the trunk manually, without opening a PR. Define the landing page within wp-admin, automatically log in as admin, install the plugin from the zip URL and activate it.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Step-by-step_guide\"><\/span>Step-by-step guide<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"1_Create_the_folder_structure\"><\/span>1. Create the folder structure<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You need two folders at the root of the repository: <code>.github\/workflows\/<\/code> for workflows and <code>.github\/<\/code> for the blueprint.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"2_Add_build-distyml\"><\/span>2. Add build-dist.yml<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">This workflow does three things: it installs dependencies, generates the blueprint with the correct branch, and pushes the dist branch. Adjust the <code>landingPage<\/code> plugin and plugin name in the blueprint generation section.<\/p>\n\n\n\n<div class=\"cbc-code-wrapper\"><div class=\"cbc-code-bar\"><button class=\"cbc-copy-button\">Copy<\/button><\/div><pre class=\"wp-block-code\"><code class=\"\">name: Build dist branch\n\non:\n  push:\n    branches:\n      - '**'\n  delete:\n\npermissions:\n  contents: write\n\njobs:\n  build:\n    if: github.event_name == 'push' &amp;&amp; !startsWith(github.ref_name, 'dist\/')\n    runs-on: ubuntu-latest\n    steps:\n      - name: Checkout\n        uses: actions\/checkout@v4\n\n      - name: Setup PHP\n        uses: shivammathur\/setup-php@v2\n        with:\n          php-version: '8.2'\n          tools: composer\n\n      - name: Install production dependencies\n        run: composer install --no-dev --optimize-autoloader\n\n      - name: Generate Playground blueprint\n        env:\n          BRANCH_NAME: ${{ github.ref_name }}\n        run: |\n          mkdir -p .wordpress-playground\n          cat > .github\/pr-blueprint.json &lt;&lt; EOF\n          {\n            \"\\$schema\": \"https:\/\/playground.wordpress.net\/blueprint-schema.json\",\n            \"landingPage\": \"\/wp-admin\/options-general.php?page=your-plugin\",\n            \"steps\": [\n              {\n                \"step\": \"login\",\n                \"username\": \"admin\",\n                \"password\": \"password\"\n              },\n              {\n                \"step\": \"installPlugin\",\n                \"pluginZipFile\": {\n                  \"resource\": \"url\",\n                  \"url\": \"https:\/\/github.com\/your-org\/your-plugin\/archive\/refs\/heads\/dist\/${BRANCH_NAME}.zip\"\n                },\n                \"options\": { \"activate\": true }\n              }\n            ]\n          }\n          EOF\n\n      - name: Push to dist branch\n        env:\n          BRANCH_NAME: ${{ github.ref_name }}\n        run: |\n          git config user.name \"github-actions[bot]\"\n          git config user.email \"github-actions[bot]@users.noreply.github.com\"\n          git add -f vendor\/ .wordpress-playground\/\n          git diff --cached --quiet || git commit -m \"Build: add vendor and playground blueprint\"\n          git push origin HEAD:dist\/${BRANCH_NAME} --force\n\n  delete-dist:\n    if: github.event_name == 'delete' &amp;&amp; github.event.ref_type == 'branch' &amp;&amp; !startsWith(github.event.ref, 'dist\/')\n    runs-on: ubuntu-latest\n    steps:\n      - name: Checkout\n        uses: actions\/checkout@v4\n\n      - name: Delete dist branch\n        env:\n          BRANCH_NAME: ${{ github.event.ref }}\n        run: |\n          git push origin \":refs\/heads\/dist\/${BRANCH_NAME}\" || true<\/code><\/pre><\/div>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"3_Add_playground-previewyml\"><\/span>3. Add playground-preview.yml<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">This workflow publishes the comment to the PR. HTML markup prevents duplicate comments from being created on each push. Change it to the name of your plugin.<\/p>\n\n\n\n<div class=\"cbc-code-wrapper\"><div class=\"cbc-code-bar\"><button class=\"cbc-copy-button\">Copy<\/button><\/div><pre class=\"wp-block-code\"><code class=\"\">name: Playground PR Preview\n\non:\n  pull_request:\n    types: [opened, reopened, synchronize]\n\npermissions:\n  issues: write\n  pull-requests: write\n\njobs:\n  playground-preview:\n    name: Comment with Playground preview link\n    runs-on: ubuntu-latest\n    steps:\n      - name: Post Playground preview comment\n        uses: actions\/github-script@v7\n        with:\n          github-token: ${{ secrets.GITHUB_TOKEN }}\n          script: |\n            const marker = '&lt;!-- your-plugin-playground-preview -->';\n            const issue_number = context.payload.pull_request.number;\n            const branchName = context.payload.pull_request.head.ref;\n            const owner = context.repo.owner;\n            const repo = context.repo.repo;\n\n            const blueprintUrl = `https:\/\/raw.githubusercontent.com\/${owner}\/${repo}\/dist\/${branchName}\/.wordpress-playground\/blueprint.json`;\n            const playgroundUrl = `https:\/\/playground.wordpress.net\/?blueprint-url=${encodeURIComponent(blueprintUrl)}`;\n\n            const body = [\n              marker,\n              '## Test in WordPress Playground',\n              `[**Open PR #${issue_number} in Playground \u2197**](${playgroundUrl})`,\n              '> The link becomes active once the **Build dist branch** workflow finishes.',\n              '- Login: `admin` \/ `password`',\n              '- The plugin is installed and activated automatically.',\n            ].join('\\n');\n\n            const comments = await github.paginate(\n              github.rest.issues.listComments,\n              { owner, repo, issue_number, per_page: 100 }\n            );\n            const existing = comments.find(c => c.body?.includes(marker));\n\n            if (existing) {\n              await github.rest.issues.updateComment({ owner, repo, comment_id: existing.id, body });\n            } else {\n              await github.rest.issues.createComment({ owner, repo, issue_number, body });\n            }<\/code><\/pre><\/div>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"4_Check_workflow_permissions\"><\/span>4. Check workflow permissions<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">In <code>build-dist.yml<\/code> Coming <code>permissions: contents: write<\/code>. In <code>playground-preview.yml<\/code> you need <code>issues: write<\/code> and <code>pull-requests: write<\/code>. If your repo has the Actions with restricted permissions by default, review it in <em>Settings \u2192 Actions \u2192 General \u2192 Workflow permissions<\/em>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"5_Make_the_first_push_and_check\"><\/span>5. Make the first push and check<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Push any branch, go to <em>Actions<\/em> , and check that the <em>Build dist branch<\/em> workflow ends in green. On the repo branches it should appear <code>dist\/nombre-de-tu-rama<\/code> with the vendor and blueprint inside.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"6_Open_a_PR_and_wait_for_the_automatic_comment\"><\/span>6. Open a PR and wait for the automatic comment<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Opening the PR executes the <em>Playground PR Preview<\/em> workflow. In a few seconds you will see a comment with the direct link to Playground with the plugin installed, login made as admin and the settings page open.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Customize_the_blueprint\"><\/span>Customize the blueprint<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The blueprint is a JSON that Playground interprets. You can add more steps depending on what your plugin needs.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" src=\"https:\/\/davidperezgar.com\/wp-content\/uploads\/github-comment-playground.png\" alt=\"Github Comment Playground\" class=\"wp-image-4604\" title=\"\"><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Install_a_dependency_plugin\"><\/span>Install a dependency plugin<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<div class=\"cbc-code-wrapper\"><div class=\"cbc-code-bar\"><button class=\"cbc-copy-button\">Copy<\/button><\/div><pre class=\"wp-block-code\"><code class=\"\">{\n  \"step\": \"installPlugin\",\n  \"pluginZipFile\": {\n    \"resource\": \"wordpress.org\/plugins\",\n    \"slug\": \"woocommerce\"\n  },\n  \"options\": { \"activate\": true }\n}<\/code><\/pre><\/div>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Create_Test_Data_with_WP-CLI\"><\/span>Create Test Data with WP-CLI<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<div class=\"cbc-code-wrapper\"><div class=\"cbc-code-bar\"><button class=\"cbc-copy-button\">Copy<\/button><\/div><pre class=\"wp-block-code\"><code class=\"\">{\n  \"step\": \"wp-cli\",\n  \"command\": \"wp post create --post_title='Test product' --post_status=publish\"\n}<\/code><\/pre><\/div>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Fix_WordPress_or_PHP_version\"><\/span>Fix WordPress or PHP version<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<div class=\"cbc-code-wrapper\"><div class=\"cbc-code-bar\"><button class=\"cbc-copy-button\">Copy<\/button><\/div><pre class=\"wp-block-code\"><code class=\"\">{\n  \"$schema\": \"https:\/\/playground.wordpress.net\/blueprint-schema.json\",\n  \"preferredVersions\": {\n    \"php\": \"8.1\",\n    \"wp\": \"6.4\"\n  }\n}<\/code><\/pre><\/div>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Important_Notes\"><\/span>Important Notes<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The Composer vendor registers in the dist branch with <code>git add -f vendor\/<\/code>. It&#8217;s intentional: Playground downloads the zip from that branch and needs all the dependencies included. It doesn&#8217;t conflict with you <code>.gitignore<\/code> because it only happens in the dist branch.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The build is forced (<code>--force<\/code>), so the dist branch always reflects the current state. There is no accumulated history.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If a PR receives several pushes in a row, the workflow updates the same comment instead of creating a new one. That is controlled by the HTML marker. Change it to something unique to your plugin to avoid collisions if you have multiple repos with the same setup.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Full documentation: <a href=\"https:\/\/wordpress.github.io\/wordpress-playground\/guides\/github-action-pr-preview\/\" target=\"_blank\" rel=\"noopener\">WordPress Playground Guide<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>When someone opens a PR in a WordPress plugin, the usual process for reviewing it involves downloading the branch, installing it locally, activating the plugin, and testing the changes by hand. That has frictions: you have to have a prepared local environment and dedicate time to install something that is perhaps half broken. If the reviewer is not a developer, they can&#8217;t do it directly. With this setup, the PR itself generates a link that opens the plugin running in the browser. One click, and you&#8217;re already trying. What is WordPress Playground? WordPress Playground is a WordPress environment that runs entirely on the&#8230; <a title=\"Preview WordPress Playground plugins directly from the Pull Request\" class=\"read-more\" href=\"https:\/\/davidperezgar.com\/blog\/desarrollo-web\/preview-de-plugins-en-wordpress-playground-directamente-desde-el-pull-request\/\" aria-label=\"Read more about WordPress Playground Plugin Preview directly from the Pull Request\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":4414,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"_ayudawp_aiss_exclude":false,"webmentions_disabled_pings":false,"webmentions_disabled":false,"editor_notices":[],"footnotes":""},"categories":[1],"tags":[],"class_list":["post-4412","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","generate-columns","tablet-grid-50","mobile-grid-100","grid-parent","grid-50"],"_links":{"self":[{"href":"https:\/\/davidperezgar.com\/en\/wp-json\/wp\/v2\/posts\/4412","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/davidperezgar.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/davidperezgar.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/davidperezgar.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/davidperezgar.com\/en\/wp-json\/wp\/v2\/comments?post=4412"}],"version-history":[{"count":4,"href":"https:\/\/davidperezgar.com\/en\/wp-json\/wp\/v2\/posts\/4412\/revisions"}],"predecessor-version":[{"id":4420,"href":"https:\/\/davidperezgar.com\/en\/wp-json\/wp\/v2\/posts\/4412\/revisions\/4420"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/davidperezgar.com\/en\/wp-json\/wp\/v2\/media\/4414"}],"wp:attachment":[{"href":"https:\/\/davidperezgar.com\/en\/wp-json\/wp\/v2\/media?parent=4412"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/davidperezgar.com\/en\/wp-json\/wp\/v2\/categories?post=4412"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/davidperezgar.com\/en\/wp-json\/wp\/v2\/tags?post=4412"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}