{"id":1126,"date":"2026-05-13T21:34:49","date_gmt":"2026-05-13T21:34:49","guid":{"rendered":"https:\/\/make.wordpress.org\/ai\/?p=1126"},"modified":"2026-05-13T21:34:49","modified_gmt":"2026-05-13T21:34:49","slug":"ai-contributor-weekly-summary-13-may-2026","status":"publish","type":"post","link":"https:\/\/make.wordpress.org\/ai\/2026\/05\/13\/ai-contributor-weekly-summary-13-may-2026\/","title":{"rendered":"AI Contributor Weekly Summary \u2013 13 May 2026"},"content":{"rendered":"<p class=\"wp-block-paragraph\"><em>This week\u2019s AI contributor meeting focused on the final coordination for the WordPress 7.0 release, the roadmap for the AI <span tabindex='0' class='glossary-item-container'>Plugin<span class='glossary-item-hidden-content'><span class='glossary-item-header'>Plugin<\/span> <span class='glossary-item-description'>A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory <a href=\"https:\/\/wordpress.org\/plugins\/\">https:\/\/wordpress.org\/plugins\/<\/a> or can be cost-based plugin from a third-party.<\/span><\/span><\/span> 1.0.0, and a deep dive into security experiments regarding Connector Approvals and Request Logging.<\/em><\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\">\n\n\n\n<h2 class=\"wp-block-heading\">Announcements &amp; Timeline<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Reviewed the <a href=\"https:\/\/make.wordpress.org\/core\/7-0\/\">current WP 7.0 timeline<\/a> and where the <span tabindex='0' class='glossary-item-container'>core<span class='glossary-item-hidden-content'><span class='glossary-item-header'>Core<\/span> <span class='glossary-item-description'>Core is the set of software required to run WordPress. The Core Development Team builds WordPress.<\/span><\/span><\/span>-ai teams work fits in<\/li>\n\n\n\n<li><strong>Field Guide:<\/strong> The comprehensive developer field guide is expected to be published alongside RC4. <a href=\"https:\/\/profiles.wordpress.org\/jeffpaul\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>jeffpaul<\/a> noted that the content regarding Connectors <span tabindex='0' class='glossary-item-container'>API<span class='glossary-item-hidden-content'><span class='glossary-item-header'>API<\/span> <span class='glossary-item-description'>An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.<\/span><\/span><\/span>, Abilities, and the AI Client is being finessed for accuracy. Draft, with current edits <a href=\"https:\/\/docs.google.com\/document\/d\/1k6i4lPrIdibSmP1v1LJfR2_QD7Wwnb6fraLw01V3KwE\/edit?tab=t.8943tt6gy1u2\">available here<\/a>; <strong><em>any and all feedback in the guide ASAP is greatly appreciated!<\/em><\/strong><\/li>\n\n\n\n<li><strong>AI Plugin 0.9.0:<\/strong> Has officially shipped: <a href=\"https:\/\/make.wordpress.org\/ai\/2026\/05\/11\/whats-new-in-ai-0-9-0\/\">Announcement post<\/a><\/li>\n\n\n\n<li><strong>AI Plugin 1.0.0:<\/strong> The team is targeting <strong>Tuesday, May 19<\/strong> for the <a href=\"https:\/\/github.com\/WordPress\/ai\/milestone\/7\">V1<\/a> release, strategically launching one day before WordPress 7.0 to provide a stable companion for early adopters.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\">\n\n\n\n<h2 class=\"wp-block-heading\">WordPress 7.0 Field Guide<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The team reviewed the draft status of the 7.0 Field Guide.<\/li>\n\n\n\n<li><strong>Action Item:<\/strong> Contributors are asked to review the <a href=\"https:\/\/docs.google.com\/document\/d\/1k6i4lPrIdibSmP1v1LJfR2_QD7Wwnb6fraLw01V3KwE\/edit?tab=t.8943tt6gy1u2\">draft<\/a> and lacking that then the published version immediately upon release. If any technical errors are spotted regarding AI implementations, they must be called out quickly for immediate adjustment.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\">\n\n\n\n<h2 class=\"wp-block-heading\">WCEU &amp; <span tabindex='0' class='glossary-item-container'>Contributor Day<span class='glossary-item-hidden-content'><span class='glossary-item-header'>Contributor Day<\/span> <span class='glossary-item-description'>Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of <a href=\"https:\/\/make.wordpress.org\/\">https:\/\/make.wordpress.org\/<\/a> There are many teams that people can participate in, each with a different focus. <a href=\"https:\/\/make.wordpress.org\/support\/handbook\/getting-started\/getting-started-at-a-contributor-day\/\">https:\/\/make.wordpress.org\/support\/handbook\/getting-started\/getting-started-at-a-contributor-day\/<\/a><\/span><\/span><\/span> Planning<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Table Leads:<\/strong> The team is seeking a <strong>Table Lead for Core AI<\/strong> for <span tabindex='0' class='glossary-item-container'>WordCamp<span class='glossary-item-hidden-content'><span class='glossary-item-header'>WordCamp<\/span> <span class='glossary-item-description'>WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they\u2019ve learned throughout the year and share the joy. <a href=\"https:\/\/central.wordcamp.org\/about\/\">Learn more<\/a>.<\/span><\/span><\/span> Europe \u2013 Please <span tabindex='0' class='glossary-item-container'>ping<span class='glossary-item-hidden-content'><span class='glossary-item-header'>Ping<\/span> <span class='glossary-item-description'>The act of sending a very small amount of data to an end point.  Ping is used in computer science to illicit a response from a target server to test it\u2019s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of \u201cPing me when the meeting starts.\u201d<\/span><\/span><\/span> in the <a href=\"https:\/\/make.wordpress.org\/ai\/tag\/core-ai\/\" class=\"tag\"><span class=\"tag-prefix\">#<\/span>core-ai<\/a> <span tabindex='0' class='glossary-item-container'>Slack<span class='glossary-item-hidden-content'><span class='glossary-item-header'>Slack<\/span> <span class='glossary-item-description'>Slack is a Collaborative Group Chat Platform <a href=\"https:\/\/slack.com\/\">https:\/\/slack.com\/<\/a>. The WordPress community has its own Slack Channel at <a href=\"https:\/\/make.wordpress.org\/chat\/\">https:\/\/make.wordpress.org\/chat\/<\/a><\/span><\/span><\/span> channel if you would like to know more.<\/li>\n\n\n\n<li><strong>Leadership Strategy:<\/strong> <a href=\"https:\/\/profiles.wordpress.org\/karmatosed\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>karmatosed<\/a> and <a href=\"https:\/\/profiles.wordpress.org\/justlevine\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>justlevine<\/a> emphasized the importance of \u201cempowering new blood,\u201d suggesting that experienced contributors like <a href=\"https:\/\/profiles.wordpress.org\/justlevine\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>justlevine<\/a> (remote) and <a href=\"https:\/\/profiles.wordpress.org\/swissspidy\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>swissspidy<\/a> (local) could pair with and support newer leads rather than just leading the table themselves. <a href=\"https:\/\/profiles.wordpress.org\/swissspidy\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>swissspidy<\/a> confirmed after the meeting, <a href=\"https:\/\/wordpress.slack.com\/archives\/C08TJ8BPULS\/p1778696532829269\">in slack <\/a>that, he has not yet confirmed if he will be attending.<\/li>\n\n\n\n<li><strong>Digital Participation:<\/strong> <a href=\"https:\/\/profiles.wordpress.org\/justlevine\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>justlevine<\/a> confirmed he will provide digital support for contributors working remotely during the event.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\">\n\n\n\n<h2 class=\"wp-block-heading\">AI Plugin 1.0.0<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A significant portion of the meeting was dedicated to the specific features intended to ship in the V1 release:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Connector Approval Experiment<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>The Problem:<\/strong> Right now, any installed plugin can potentially use the Connectors API and reuse stored AI credentials, which means site owners may not have clear control over which plugins are actually using those keys. The concern is not only general plugin access, but also the newer AI-specific risk: once an LLM can access sensitive data, that data may be sent upstream into model history with little practical privacy boundary.<\/li>\n\n\n\n<li><strong>The Proposed Solution:<\/strong> <a href=\"https:\/\/profiles.wordpress.org\/dkotter\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>dkotter<\/a> adds <a href=\"https:\/\/github.com\/WordPress\/ai\/pull\/467\">a Connectors Approval flow<\/a> that blocks plugin access by default and requires admin approval before a plugin can use a connector. The goal is to create a practical first layer of interference around access to sensitive connector data now, without waiting to solve the entire long-term secrets architecture.<\/li>\n\n\n\n<li><strong><a href=\"https:\/\/profiles.wordpress.org\/justlevine\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>justlevine<\/a>,<\/strong> <strong>commentary:<\/strong> David helped reframe the value of the experiment by distinguishing LLMs from traditional plugin risk. He argued that the immediate problem is not just secret storage, but that LLMs can absorb and pass along context in a non-deterministic way, which makes access control especially important. His view was that the first step does not need to fully solve encryption or the deeper secrets-management layer; it can instead focus on preventing access to the sensitive data that LLM-powered features might otherwise consume. He also reinforced the value of \u201cemergency breaks,\u201d such as the existing constant-based kill switch and approval controls, because they give site owners a way to limit or stop unsafe behavior while the platform matures. Finally, he suggested that Connectors could be positioned as a more robust and safer pattern for registering credentials and related options than traditional settings, which could help drive adoption of this more managed model over time.<\/li>\n\n\n\n<li><strong>Security Concerns:<\/strong> <a href=\"https:\/\/profiles.wordpress.org\/jason_the_adams\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>jason_the_adams<\/a> pushed on the idea of \u201cfalse security,\u201d pointing out that this does not stop a bad plugin from pulling API credentials directly from the database or otherwise bypassing the approval flow. Others agreed that secret management or encryption on its own would not fully solve that, because WordPress does not yet have a true per-plugin sandbox or permissions layer around secrets. The group aligned that this experiment should be documented carefully so users understand it improves control and creates friction, but does not eliminate the broader platform-level gap.<\/li>\n\n\n\n<li><strong>Decision:<\/strong> The group landed on moving forward with the PR as an experiment for 1.0, not as a complete security solution. The reasoning from <a href=\"https:\/\/profiles.wordpress.org\/jeffpaul\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>jeffpaul<\/a> was that it is better to start with a clear, limited control mechanism now than to wait for a perfect model, and that this gives the team something concrete to build on for 7.1 work around secrets management, permissions, and safer connector access.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">AI Request Logging<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Database Strategy:<\/strong> The team reached a consensus on using a custom database table for logging rather than post <span tabindex='0' class='glossary-item-container'>meta<span class='glossary-item-hidden-content'><span class='glossary-item-header'>Meta<\/span> <span class='glossary-item-description'>Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.<\/span><\/span><\/span>, primarily due to enterprise-level performance concerns. This was based on <a href=\"https:\/\/github.com\/WordPress\/ai\/pull\/437\">this PR<\/a>.<\/li>\n\n\n\n<li><strong>Data Structure:<\/strong> To prevent bloat, the log will use truncated context. <a href=\"https:\/\/profiles.wordpress.org\/mikeyarce\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>mikeyarce<\/a> suggested adding tracking for cached vs. non-cached tokens to assist with cost analysis for providers like Anthropic and OpenAI.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Version Management &amp; Philosophy<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Versioning:<\/strong> The question was asked if 1.0.0 is meant to imply semver-style stability, or if we are following WordPress-style versioning, where experiments can still change in breaking ways. The group leaned toward dropping strict SemVer expectations and following WordPress-style versioning, with experiments explicitly not guaranteed future compatibility.<\/li>\n\n\n\n<li><strong>Compatibility:<\/strong> The group reiterated that features marked as Experiments do not guarantee future compatibility. Users opting into these features should expect potential breaking changes as the team iterates.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\">\n\n\n\n<h2 class=\"wp-block-heading\">Next Steps<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Review and finalize the <strong>WordPress 7.0 Field Guide<\/strong> content tomorrow.<\/li>\n\n\n\n<li>Perform final testing on the <strong>Connector Approval<\/strong> and <strong>Request Logging<\/strong> PRs.<\/li>\n\n\n\n<li>Finalize the <strong>AI Plugin 1.0.0<\/strong> release for Tuesday.<\/li>\n\n\n\n<li><a href=\"https:\/\/profiles.wordpress.org\/justlevine\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>justlevine<\/a> to finalize <strong><span tabindex='0' class='glossary-item-container'>MCP Adapter<span class='glossary-item-hidden-content'><span class='glossary-item-header'>MCP Adapter<\/span> <span class='glossary-item-description'>Translates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts.<\/span><\/span><\/span><\/strong> documentation and plugin scaffolding over the weekend.<\/li>\n\n\n\n<li>Formalize the call for <strong>WCEU Table Leads<\/strong> in the Slack channel.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\">\n\n\n\n<h2 class=\"wp-block-heading\">Upcoming Meetings<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>AI Team Office Hours (Slack):<\/strong> 14 May 2026. <a href=\"https:\/\/profiles.wordpress.org\/jeffpaul\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>jeffpaul<\/a> and <a href=\"https:\/\/profiles.wordpress.org\/justlevine\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>justlevine<\/a> will facilitate.<\/li>\n\n\n\n<li><strong>Weekly AI Contributor Call (Google Meet):<\/strong> 20 May 2026 (WordPress 7.0 Release Day).<\/li>\n<\/ul>\n\n\n\n<p class=\"has-text-align-right wp-block-paragraph\"><em>Props to\u00a0<a href=\"https:\/\/profiles.wordpress.org\/jeffpaul\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>jeffpaul<\/a> for pre-publish review.<\/em><\/p>\n<p class=\"o2-appended-tags\"><a href=\"https:\/\/make.wordpress.org\/ai\/tag\/summary\/\" class=\"tag\"><span class=\"tag-prefix\">#<\/span>summary<\/a><\/p><nav class='o2-post-footer-actions'><ul class='o2-post-footer-action-row'><li class='o2-post-footer-action'><a href=\"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fai%2F2026%2F05%2F13%2Fai-contributor-weekly-summary-13-may-2026%2F%23respond&#038;locale=en_US\" title=\"Login to Reply\"  class=\"genericon  genericon-reply\"  data-action=\"login-to-reply\"  data-actionstate=\"default\" >Login to Reply<\/a><\/li><\/ul><div class='o2-post-footer-action-likes'><\/div><ul class='o2-post-footer-action-row'><\/ul><\/nav>","protected":false},"excerpt":{"rendered":"<p>This week\u2019s AI contributor meeting focused on final preparations for the WordPress 7.0 release, the roadmap toward AI Plugin 1.0.0, and key discussions around Connector Approvals and AI Request Logging experiments. Contributors also reviewed field guide progress, discussed WordCamp Europe contributor planning, and aligned on how experimental AI features should evolve within WordPress-style versioning.<\/p>\n","protected":false},"author":5988227,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"advanced_seo_description":"","jetpack_seo_html_title":"","jetpack_seo_noindex":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[23],"tags":[3,16],"class_list":["post-1126","post","type-post","status-publish","format-standard","hentry","category-summaries","tag-core-ai","tag-summary","mentions-dkotter","mentions-jason_the_adams","mentions-jeffpaul","mentions-justlevine","mentions-karmatosed","mentions-mikeyarce","mentions-swissspidy","author-neel33"],"revision_note":"","jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"jetpack-related-posts":[{"id":1088,"url":"https:\/\/make.wordpress.org\/ai\/2026\/05\/08\/ai-contributor-weekly-summary-6-may-2026\/","url_meta":{"origin":1126,"position":0},"title":"AI Contributor Weekly Summary &#8211; 6 May 2026","author":"Jeffrey Paul","date":"8 May 2026","format":false,"excerpt":"This week\u2019s AI contributors meeting focused on the future direction of the Core AI team, WordPress 7.0 preparation work, and ongoing discussions around connector approval and API key security. Contributors also reviewed provider plugin releases, WPBench maintainership, and plans for the upcoming AI 1.0.0 release.","rel":"","context":"In &quot;Summaries&quot;","block_context":{"text":"Summaries","link":"https:\/\/make.wordpress.org\/ai\/category\/summaries\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1086,"url":"https:\/\/make.wordpress.org\/ai\/2026\/05\/08\/ai-contributor-weekly-summary-29-april-2026\/","url_meta":{"origin":1126,"position":1},"title":"AI Contributor Weekly Summary &#8211; 29 April 2026","author":"Jeffrey Paul","date":"8 May 2026","format":false,"excerpt":"This week\u2019s AI contributors meeting focused on MCP adapter progress, release planning ahead of WordPress 7.0, and increasing testing efforts across the AI plugin ecosystem. Contributors also discussed connector security experiments, provider\/model selection improvements, and ongoing ownership discussions around WordPress Agent Skills.","rel":"","context":"In &quot;Summaries&quot;","block_context":{"text":"Summaries","link":"https:\/\/make.wordpress.org\/ai\/category\/summaries\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1072,"url":"https:\/\/make.wordpress.org\/ai\/2026\/04\/27\/ai-contributor-weekly-summary-22-april-2026\/","url_meta":{"origin":1126,"position":2},"title":"AI Contributor Weekly Summary &#8211; 22 April 2026","author":"Jeffrey Paul","date":"27 April 2026","format":false,"excerpt":"This week\u2019s AI team meeting focused on keeping momentum during a period of reduced contributor availability, making key decisions to unblock WordPress 7.0 work. Highlights include agreement to ship the MCP adapter as a standalone WordPress.org plugin, continue connector flow improvements, and move forward with reversible decisions while leadership availability\u2026","rel":"","context":"In &quot;Summaries&quot;","block_context":{"text":"Summaries","link":"https:\/\/make.wordpress.org\/ai\/category\/summaries\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":863,"url":"https:\/\/make.wordpress.org\/ai\/2026\/03\/11\/ai-contributor-weekly-summary-11-march-2026\/","url_meta":{"origin":1126,"position":3},"title":"AI Contributor Weekly Summary \u2013 11 March 2026","author":"neillmcshea","date":"11 March 2026","format":false,"excerpt":"This week\u2019s AI contributor meeting focused on final preparations for WordPress 7.0, specifically addressing critical compatibility issues between the AI Experiments plugin and core. The group also discussed a potential rebrand of the experiments plugin, the introduction of \"Capital F\" features, and initial coordination for the upcoming WordCamp Asia Contributor\u2026","rel":"","context":"In &quot;General&quot;","block_context":{"text":"General","link":"https:\/\/make.wordpress.org\/ai\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":829,"url":"https:\/\/make.wordpress.org\/ai\/2026\/03\/06\/ai-contributor-weekly-summary-4-march-2026\/","url_meta":{"origin":1126,"position":4},"title":"AI Contributor Weekly Summary &#8211; 4 March 2026","author":"Jeffrey Paul","date":"6 March 2026","format":false,"excerpt":"This week\u2019s AI contributor meeting reviewed progress across the AI Experiments plugin, provider plugins for the WordPress AI Client ecosystem, and the MCP adapter project as WordPress 7.0 Beta 3 approaches. Contributors also discussed upcoming testing needs for the connectors interface and early feedback on \u201cTry AI\u201d onboarding flows.","rel":"","context":"In &quot;Summaries&quot;","block_context":{"text":"Summaries","link":"https:\/\/make.wordpress.org\/ai\/category\/summaries\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1146,"url":"https:\/\/make.wordpress.org\/ai\/2026\/05\/21\/ai-contributor-weekly-summary-20-may-2026\/","url_meta":{"origin":1126,"position":5},"title":"AI Contributor Weekly Summary \u2013 20 May 2026","author":"neillmcshea","date":"21 May 2026","format":false,"excerpt":"This week\u2019s AI contributor meeting coincided directly with the landmark launch day of WordPress 7.0. The team focused on tracking the core release timeline, stabilizing the freshly debuted version 1.0.0 of the AI plugin, resolving high-priority architectural questions for the Abilities API, and restructuring technical and operational frameworks for the\u2026","rel":"","context":"In &quot;General&quot;","block_context":{"text":"General","link":"https:\/\/make.wordpress.org\/ai\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"jetpack_shortlink":"https:\/\/wp.me\/pgARFV-ia","_links":{"self":[{"href":"https:\/\/make.wordpress.org\/ai\/wp-json\/wp\/v2\/posts\/1126","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/make.wordpress.org\/ai\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/make.wordpress.org\/ai\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/make.wordpress.org\/ai\/wp-json\/wp\/v2\/users\/5988227"}],"replies":[{"embeddable":true,"href":"https:\/\/make.wordpress.org\/ai\/wp-json\/wp\/v2\/comments?post=1126"}],"version-history":[{"count":3,"href":"https:\/\/make.wordpress.org\/ai\/wp-json\/wp\/v2\/posts\/1126\/revisions"}],"predecessor-version":[{"id":1131,"href":"https:\/\/make.wordpress.org\/ai\/wp-json\/wp\/v2\/posts\/1126\/revisions\/1131"}],"wp:attachment":[{"href":"https:\/\/make.wordpress.org\/ai\/wp-json\/wp\/v2\/media?parent=1126"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/make.wordpress.org\/ai\/wp-json\/wp\/v2\/categories?post=1126"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/make.wordpress.org\/ai\/wp-json\/wp\/v2\/tags?post=1126"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}