{"id":205,"date":"2026-02-05T06:56:24","date_gmt":"2026-02-05T05:56:24","guid":{"rendered":"https:\/\/helloblog.io\/ro\/wordpress-revine-la-trei-release-uri-majore-in-2026-planificare-7-0-ai-client-redesign-admin-php-7-4\/"},"modified":"2026-02-05T06:56:24","modified_gmt":"2026-02-05T05:56:24","slug":"wordpress-revine-la-trei-release-uri-majore-in-2026-planificare-7-0-ai-client-redesign-admin-php-7-4","status":"publish","type":"post","link":"https:\/\/helloblog.io\/ro\/wordpress-revine-la-trei-release-uri-majore-in-2026-planificare-7-0-ai-client-redesign-admin-php-7-4\/","title":{"rendered":"WordPress revine la trei release-uri majore \u00een 2026: primele discu\u021bii pentru 7.0, AI Client, redesign de admin \u0219i PHP minim 7.4"},"content":{"rendered":"\n<p>\u00cen ultimele luni, discu\u021biile despre ritmul de livrare (release cadence) \u00een WordPress au fost mai tensionate dec\u00e2t de obicei: \u00eentre planificare tehnic\u0103, capacitate de contribu\u021bie \u0219i contextul juridic care a influen\u021bat direct resursele proiectului. \u00centr-un check-in trimestrial cu core committers \u0219i leadership, proiectul a conturat acum o direc\u021bie diferit\u0103 pentru 2026: revenirea la trei release-uri majore \u0219i startul planific\u0103rii pentru WordPress 7.0.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"2000\" height=\"1333\" src=\"https:\/\/helloblog.io\/app\/uploads\/sites\/10\/2026\/02\/core-committers-check-in-feature-img.jpg\" alt=\"Captur\u0103 de ecran cu un articol intitulat \u201eCore Committers Check-in \u2013 November 2025\u201d\" class=\"wp-image-204\" srcset=\"https:\/\/helloblog.io\/app\/uploads\/sites\/10\/2026\/02\/core-committers-check-in-feature-img.jpg 2000w, https:\/\/helloblog.io\/app\/uploads\/sites\/10\/2026\/02\/core-committers-check-in-feature-img-300x200.jpg 300w, https:\/\/helloblog.io\/app\/uploads\/sites\/10\/2026\/02\/core-committers-check-in-feature-img-1024x682.jpg 1024w, https:\/\/helloblog.io\/app\/uploads\/sites\/10\/2026\/02\/core-committers-check-in-feature-img-768x512.jpg 768w, https:\/\/helloblog.io\/app\/uploads\/sites\/10\/2026\/02\/core-committers-check-in-feature-img-1536x1024.jpg 1536w, https:\/\/helloblog.io\/app\/uploads\/sites\/10\/2026\/02\/core-committers-check-in-feature-img-400x267.jpg 400w\" sizes=\"auto, (max-width: 2000px) 100vw, 2000px\" \/><figcaption class=\"wp-element-caption\"><em>Forr\u00e1s: The Repository \/ Make WordPress Core<\/em><\/figcaption><\/figure>\n\n\n\n<p>\u00cent\u00e2lnirea a fost desf\u0103\u0219urat\u0103 sub <a href=\"https:\/\/www.chathamhouse.org\/about-us\/chatham-house-rule\">Chatham House Rule<\/a>, ceea ce explic\u0103 de ce concluziile apar mai degrab\u0103 ca direc\u021bii \u0219i inten\u021bii dec\u00e2t ca decizii finale nominalizate. Pe agend\u0103 au intrat: calendarul de release pentru 2026, fereastra probabil\u0103 pentru WordPress 7.0, func\u021bionalit\u0103\u021bi candidate (inclusiv WordPress AI Client), stadiul redesign-ului de admin \u0219i posibilitatea ridic\u0103rii versiunii minime de PHP.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">De ce conteaz\u0103 schimbarea: de la \u201eun singur major release\u201d la trei \u00een 2026<\/h2>\n\n\n\n<p>Concluzia principal\u0103 a \u00eent\u00e2lnirii: WordPress este setat s\u0103 revin\u0103 la trei versiuni majore \u00een 2026. E o schimbare notabil\u0103 fa\u021b\u0103 de \u00eenceputul anului, c\u00e2nd Executive Director Mary Hubbard anun\u021base c\u0103 \u00een 2026 va exista un singur major release, invoc\u00e2nd \u201eongoing legal matters\u201d &#8211; o trimitere la disputa juridic\u0103 din jurul WP Engine &#8211; \u0219i \u00een paralel reducerea contribu\u021biilor Automattic la WordPress.<\/p>\n\n\n\n<p>Practic, discu\u021bia despre cadence nu mai e doar o preferin\u021b\u0103 de product management; e o problem\u0103 de capacitate real\u0103 (c\u00e2\u021bi oameni pot livra), coordonare \u00eentre echipe \u0219i predictibilitate pentru ecosistem (pluginuri, teme, hosting, agen\u021bii).<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Trei release-uri majore \u00een 2026 \u0219i \u021binta pentru WordPress 7.0<\/h2>\n\n\n\n<p>Potrivit noti\u021belor publicate pe Make WordPress Core de core committer-ul Jonathan Desrosiers, inten\u021bia este reluarea ritmului de trei release-uri majore anul viitor, cu WordPress 7.0 vizat pentru martie sau aprilie.<\/p>\n\n\n\n<p>O lansare \u00een februarie a fost exclus\u0103, pentru c\u0103 ar \u00eempinge Beta 1 la \u00eenceput de ianuarie &#8211; exact perioada \u00een care mul\u021bi contributori sunt \u00eenc\u0103 \u00een concediu &#8211; iar mai multe func\u021bionalit\u0103\u021bi aflate \u00een lucru nu ar fi gata la timp.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Lans\u0103ri aliniate cu evenimente \u201eflagship\u201d: idee, nu plan<\/h3>\n\n\n\n<p>\u00cen \u00eent\u00e2lnire s-a discutat \u0219i posibilitatea alinierii release-urilor majore cu evenimente importante (flagship events), pe modelul lans\u0103rii WordPress 6.9 care a coincis cu State of the Word. Totu\u0219i, grupul a subliniat c\u0103 o astfel de sincronizare adaug\u0103 complexitate: c\u0103l\u0103torii, fusuri orare, disponibilitatea release squad-ului \u0219i a contributorilor.<\/p>\n\n\n\n<p>\u00cen acest moment, ideea r\u0103m\u00e2ne o posibilitate, nu un plan. A fost marcat\u0103 pentru discu\u021bii ulterioare, tocmai pentru a evalua dac\u0103 beneficiile de comunicare \u0219i coordonare dep\u0103\u0219esc costul opera\u021bional.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Ce ar putea intra \u00een WordPress 7.0: de la Tabs block la WordPress AI Client<\/h2>\n\n\n\n<p>O parte din func\u021bionalit\u0103\u021bile care fuseser\u0103 ini\u021bial luate \u00een calcul pentru WordPress 6.9 au revenit pe mas\u0103 ca posibili candida\u021bi pentru 7.0. \u00cen discu\u021bii au ap\u0103rut:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>template activation<\/li>\n\n\n<li>Tabs block<\/li>\n\n\n<li>client-side abilities pentru Abilities API (un API care descrie \u201ecapabilit\u0103\u021bi\u201d utilizabile de diverse componente)<\/li>\n\n\n<li>client-side media editing (editare media \u00een browser)<\/li>\n\n<\/ul>\n\n\n\n<p>Cea mai ampl\u0103 dezbatere s-a concentrat \u00eens\u0103 pe WordPress AI Client.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">WordPress AI Client: SDK nativ, agnostic de provider, posibil candidat pentru Core<\/h3>\n\n\n\n<p>WordPress AI Client este unul dintre cele patru \u201eBuilding Blocks\u201d din roadmap-ul AI Team \u0219i, \u00een acest moment, este luat \u00een calcul pentru includere \u00een WordPress Core. Versiunea 0.1.0 a WordPress AI Client a fost livrat\u0103 recent, iar ideea de baz\u0103 este s\u0103 ofere o cale nativ\u0103 (WordPress-native), agnostic de provider, prin care pluginurile \u0219i temele pot interac\u021biona cu servicii AI.<\/p>\n\n\n\n<p>Clientul adapteaz\u0103 <a href=\"https:\/\/github.com\/WordPress\/php-ai-client\">PHP AI Client<\/a> la conven\u021biile WordPress \u0219i mizeaz\u0103 pe infrastructura pe care o avem deja \u00een ecosistem. Concret, conform descrierilor din noti\u021bele \u00eent\u00e2lnirii \u0219i anun\u021bului de lansare, WordPress AI Client:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>folose\u0219te WordPress HTTP API pentru request-uri c\u0103tre servicii AI<\/li>\n\n\n<li>centralizeaz\u0103 cheile API \u00eentr-un ecran dedicat, numit \u201eAI Credentials\u201d<\/li>\n\n\n<li>gestioneaz\u0103 selec\u021bia modelului f\u0103r\u0103 s\u0103 for\u021beze pluginurile s\u0103 \u201ehard-codeze\u201d provideri specifici (de ex. un singur vendor)<\/li>\n\n<\/ul>\n\n\n\n<p>Planurile pentru release-uri viitoare ale AI Client includ, de asemenea:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>suport pentru Abilities API<\/li>\n\n\n<li>REST endpoints<\/li>\n\n\n<li>un Prompt Builder pe client-side (un builder \u00een browser pentru compunerea prompturilor)<\/li>\n\n<\/ul>\n\n\n\n<p>Motivul pentru care core committers \u00eel v\u0103d ca un candidat puternic pentru core \u021bine de \u201efunda\u021bie\u201d: dac\u0103 vrei un ecosistem s\u0103n\u0103tos, ai nevoie de interfe\u021be \u0219i conven\u021bii stabile, pe care pluginurile s\u0103 construiasc\u0103 \u00eentr-un mod compatibil. \u00cen noti\u021bele \u00eent\u00e2lnirii, argumentul este formulat explicit: includerea AI Client \u00een Core ar \u00eencuraja ecosistemul s\u0103 construiasc\u0103 pe baze solide (precum Abilities API), iar combinarea acestor API-uri poate deschide multe posibilit\u0103\u021bi at\u00e2t pentru dezvoltatori, c\u00e2t \u0219i pentru ownerii de site-uri.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Constr\u00e2ngeri: WordPress trebuie s\u0103 r\u0103m\u00e2n\u0103 agnostic (\u0219i AI-ul nu poate fi \u201eun singur provider\u201d)<\/h3>\n\n\n\n<p>\u00cen acela\u0219i timp, discu\u021biile au subliniat limitele: WordPress \u201eva r\u0103m\u00e2ne mereu agnostic\u201d. Asta \u00eenseamn\u0103 c\u0103 includerea unui model AI specific sau integrarea doar cu anumite servicii third-party nu este sustenabil\u0103 pe termen lung.<\/p>\n\n\n\n<p>A fost men\u021bionat\u0103 \u0219i perspectiva c\u0103, pe termen mai lung, oportunit\u0103\u021bi interesante ar putea veni din modele emergente bazate pe machine sau direct la nivel de browser. Nu s-a ales \u00eens\u0103 o direc\u021bie concret\u0103 \u00een aceast\u0103 \u00eent\u00e2lnire.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">\u00cenainte de o decizie: use case-uri clare pentru \u201edefault WordPress\u201d<\/h3>\n\n\n\n<p>\u00cenainte ca AI Client s\u0103 fie acceptat \u00een core, contributorii vor s\u0103 vad\u0103 use case-uri clare \u00een WordPress \u201eout of the box\u201d. Exemplele vehiculate au fost foarte concrete:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>c\u0103utare \u00een Media Library dup\u0103 subiect (de exemplu, s\u0103 g\u0103se\u0219ti imagini cu un anumit tip de con\u021binut)<\/li>\n\n\n<li>generarea de newslettere pe baza con\u021binutului recent publicat<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Redesign-ul de admin: nu o revolu\u021bie, ci o \u201e\u00eemprosp\u0103tare\u201d<\/h2>\n\n\n\n<p>Redesign-ul zonei de administrare a ap\u0103rut din nou \u00een discu\u021bie, cu o clarificare important\u0103: obiectivul nu este un overhaul complet, ci mai degrab\u0103 o aplicare a unui \u201efresh coat of paint\u201d &#8211; adic\u0103 o \u00eemprosp\u0103tare a ceea ce exist\u0103 deja.<\/p>\n\n\n\n<p>Aceast\u0103 nuan\u021b\u0103 vine \u00een contextul discu\u021biilor din \u00eent\u00e2lnirea trimestrial\u0103 din iulie, c\u00e2nd se analizase ideea de a testa redesign-ul ca experiment fie \u00een pluginul Gutenberg, fie ca un plugin separat de tip \u201eMP7\u201d. Referin\u021ba la MP7 este inten\u021bionat un nod c\u0103tre MP6, modelul \u201efeature as a plugin\u201d folosit \u00een 2013, care a influen\u021bat redesign-ul de admin din WordPress 3.8.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Unde se \u00eencadreaz\u0103 \u00een roadmap: Gutenberg Phase 3 (Collaboration)<\/h3>\n\n\n\n<p>Redesign-ul de admin este parte din Phase 3: Collaboration, \u00een roadmap-ul Gutenberg. Munca pe aceast\u0103 direc\u021bie a \u00eenceput \u00een 2023, c\u00e2nd Mat\u00edas Ventura (Gutenberg Lead Architect) \u0219i-a publicat viziunea pentru modernizarea experien\u021bei de administrare, iar ulterior a demonstrat layout-uri noi \u00een State of the Word 2023.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">De ce nu a ajuns \u00een 6.9 \u0219i ce \u0219tim despre timeline<\/h3>\n\n\n\n<p>Un early preview al redesign-ului, care fusese ini\u021bial planificat s\u0103 vin\u0103 al\u0103turi de WordPress 6.9, a fost pus pe pauz\u0103 \u00een septembrie. \u00cen update-ul de roadmap, ini\u021biativa a fost marcat\u0103 ca \u201eno longer planned based on the current state of work\u201d.<\/p>\n\n\n\n<p>Momentan, nu exist\u0103 un timeline pentru c\u00e2nd admin-ul redesenat ar putea ajunge efectiv \u00een WordPress. Ultima \u00eemprosp\u0103tare major\u0103 a admin-ului a fost livrat\u0103 \u00een WordPress 3.8, adic\u0103 acum mai bine de un deceniu.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">PHP minim 7.4: \u201ecompelling reasons\u201d, dar f\u0103r\u0103 decizie final\u0103<\/h2>\n\n\n\n<p>Un alt subiect care atinge direct dezvoltatorii \u0219i companiile de hosting: ridicarea versiunii minime suportate de PHP la 7.4. \u00cen \u00eent\u00e2lnire s-au explorat \u201ecompelling reasons\u201d pentru aceast\u0103 schimbare, \u00eens\u0103 nu s-a luat o decizie \u00een cadrul sesiunii.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">De ce \u00eempinge proiectul spre 7.4 (din perspectiv\u0103 practic\u0103)<\/h3>\n\n\n\n<p>Discu\u021bia a fost centrat\u0103 pe limitele practice ale compatibilit\u0103\u021bii cu versiuni vechi de PHP. Argumentele principale:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>compatibilitatea cu PHP mai vechi oblig\u0103 WordPress s\u0103 p\u0103streze constr\u00e2ngeri care adaug\u0103 bloat (cod \u0219i condi\u021bion\u0103ri \u00een plus) \u0219i \u00eencetinesc dezvoltarea<\/li>\n\n\n<li>PHP 7.4 ar muta codebase-ul spre typing mai consistent, ceea ce ajut\u0103 at\u00e2t dezvoltatorii, c\u00e2t \u0219i sistemele AI s\u0103 \u00een\u021beleag\u0103 mai u\u0219or codul<\/li>\n\n\n<li>multe SDK-uri AI third-party cer deja versiuni mai noi de PHP; un minim prea jos blocheaz\u0103 adoptarea lor \u00een proiect<\/li>\n\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Echilibrul: progres f\u0103r\u0103 a \u201el\u0103sa pe cineva \u00een urm\u0103\u201d<\/h3>\n\n\n\n<p>\u00centreaga conversa\u021bie a fost \u00eencadrat\u0103 ca un exerci\u021biu de echilibru: proiectul vrea s\u0103 progreseze, dar f\u0103r\u0103 s\u0103 piard\u0103 utilizatori \u0219i f\u0103r\u0103 s\u0103 creeze o barier\u0103 brusc\u0103 pentru site-urile care \u00eenc\u0103 ruleaz\u0103 pe infrastructur\u0103 veche. De aici \u0219i faptul c\u0103, cel pu\u021bin \u00een aceast\u0103 \u00eent\u00e2lnire, nu s-a anun\u021bat o schimbare concret\u0103.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Ce urmeaz\u0103 dup\u0103 check-in: puncte de follow-up asumate<\/h2>\n\n\n\n<p>Jonathan Desrosiers a notat o list\u0103 de ac\u021biuni de follow-up rezultate din sesiune. Printre ele:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>propunerea unor formate de \u00eent\u00e2lnire mai deschise \u0219i semi-deschise<\/li>\n\n\n<li>publicarea programului de release pentru 2026<\/li>\n\n\n<li>confirmarea func\u021bionalit\u0103\u021bilor \u021bintite pentru WordPress 7.0 \u0219i, posibil, 7.1<\/li>\n\n\n<li>evaluarea practic\u0103 a ideii de a coordona release-urile cu evenimente in-person<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Concluzie: 2026 se anun\u021b\u0103 din nou \u201erapid\u201d, dar cu decizii de funda\u021bie<\/h2>\n\n\n\n<p>Revenirea la trei release-uri majore \u00een 2026 schimb\u0103 a\u0219tept\u0103rile pentru toat\u0103 lumea: de la echipele care \u00eentre\u021bin pluginuri \u0219i teme, p\u00e2n\u0103 la hosting \u0219i agen\u021bii care planific\u0103 upgrade-uri \u0219i compatibilit\u0103\u021bi. \u00cen acela\u0219i timp, discu\u021biile pentru WordPress 7.0 arat\u0103 c\u0103 proiectul se uit\u0103 la decizii de funda\u021bie: un strat standard pentru integrarea AI (WordPress AI Client), o modernizare de admin care promite mai degrab\u0103 consisten\u021b\u0103 \u0219i refresh dec\u00e2t o ruptur\u0103, \u0219i presiunea tot mai mare de a ridica minimul de PHP pentru a elimina fr\u00e2nele tehnice.<\/p>\n\n\n<div class=\"references-section\">\n                <h2>Referin\u021be \/ Surse<\/h2>\n                <ul class=\"references-list\"><li><a href=\"https:\/\/www.therepository.email\/wordpress-returns-to-three-major-releases-in-2026-as-planning-begins-for-7-0\" target=\"_blank\" rel=\"noopener noreferrer\">WordPress Returns to Three Major Releases in 2026 as Planning Begins for 7.0<\/a><\/li><li><a href=\"https:\/\/make.wordpress.org\/core\/2025\/11\/26\/core-committers-check-in-november-2025\/\" target=\"_blank\" rel=\"noopener noreferrer\">Core Committers Check-in \u2013 November 2025<\/a><\/li><li><a href=\"https:\/\/www.therepository.email\/wordpress-slows-to-one-major-release-per-year-and-not-everyone-agrees-with-how-it-happened\" target=\"_blank\" rel=\"noopener noreferrer\">WordPress slows to one major release per year &#8211; and not everyone agrees with how it happened<\/a><\/li><li><a href=\"https:\/\/www.therepository.email\/wp-engine-expands-legal-fight-against-automattic-and-matt-mullenweg-with-antitrust-claims\" target=\"_blank\" rel=\"noopener noreferrer\">WP Engine expands legal fight against Automattic and Matt Mullenweg with antitrust claims<\/a><\/li><li><a href=\"https:\/\/www.therepository.email\/automattic-scales-back-wordpress-contributions-to-match-wp-engine-amid-legal-battle\" target=\"_blank\" rel=\"noopener noreferrer\">Automattic scales back WordPress contributions to match WP Engine amid legal battle<\/a><\/li><li><a href=\"https:\/\/www.therepository.email\/wordpress-6-9-confirmed-for-late-2025-with-roadmap-on-the-way\" target=\"_blank\" rel=\"noopener noreferrer\">WordPress 6.9 Confirmed for December 2025 With Roadmap on the Way<\/a><\/li><li><a href=\"https:\/\/www.therepository.email\/wordpress-6-9-beta-1-now-available-and-ready-for-testing\" target=\"_blank\" rel=\"noopener noreferrer\">WordPress 6.9 Beta 1 Now Available and Ready for Testing<\/a><\/li><li><a href=\"https:\/\/www.therepository.email\/wordpress-scales-back-to-one-major-release-in-2025\" target=\"_blank\" rel=\"noopener noreferrer\">WordPress Scales Back to One Major Release in 2025<\/a><\/li><li><a href=\"https:\/\/www.therepository.email\/wordpress-could-see-just-one-major-release-per-year-under-new-proposal\" target=\"_blank\" rel=\"noopener noreferrer\">WordPress Could See Just One Major Release Per Year Under New Proposal<\/a><\/li><li><a href=\"https:\/\/www.therepository.email\/understanding-the-abilities-api-what-it-is-why-it-matters-and-how-its-going-to-transform-wordpress\" target=\"_blank\" rel=\"noopener noreferrer\">Understanding the Abilities API: What It Is, Why It Matters, and How It\u2019s Going to Transform WordPress<\/a><\/li><li><a href=\"https:\/\/www.therepository.email\/wordpress-ai-team-publishes-first-roadmap-focused-on-developer-tools-and-infrastructure\" target=\"_blank\" rel=\"noopener noreferrer\">WordPress AI Team publishes first roadmap focused on developer tools and infrastructure<\/a><\/li><li><a href=\"https:\/\/make.wordpress.org\/ai\/2025\/11\/21\/introducing-the-wordpress-ai-client-sdk\/\" target=\"_blank\" rel=\"noopener noreferrer\">Introducing the WordPress AI Client SDK<\/a><\/li><li><a href=\"https:\/\/github.com\/WordPress\/php-ai-client\" target=\"_blank\" rel=\"noopener noreferrer\">php-ai-client<\/a><\/li><li><a href=\"https:\/\/www.therepository.email\/state-of-the-word-2025-set-for-san-francisco-coinciding-with-wordpress-6-9-release\" target=\"_blank\" rel=\"noopener noreferrer\">State of the Word 2025 set for San Francisco, coinciding with WordPress 6.9 release<\/a><\/li><li><a href=\"https:\/\/make.wordpress.org\/core\/2023\/07\/12\/admin-design\/\" target=\"_blank\" rel=\"noopener noreferrer\">Admin design<\/a><\/li><\/ul>\n            <\/div>","protected":false},"excerpt":{"rendered":"<p>Dup\u0103 un 2026 anun\u021bat ini\u021bial ca \u201eone major release\u201d, planul se schimb\u0103: WordPress \u021binte\u0219te din nou trei versiuni majore. \u00cen paralel, \u00eencep deciziile grele pentru 7.0: ce intr\u0103 \u00een core, cum arat\u0103 admin-ul \u0219i ce facem cu PHP-ul minim.<\/p>\n","protected":false},"author":31,"featured_media":203,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[18],"tags":[27,25,26,103,10],"class_list":["post-205","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ecosistem-wordpress","tag-ai","tag-gutenberg","tag-php","tag-release-management","tag-wordpress"],"_links":{"self":[{"href":"https:\/\/helloblog.io\/ro\/wp-json\/wp\/v2\/posts\/205","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/helloblog.io\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/helloblog.io\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/helloblog.io\/ro\/wp-json\/wp\/v2\/users\/31"}],"replies":[{"embeddable":true,"href":"https:\/\/helloblog.io\/ro\/wp-json\/wp\/v2\/comments?post=205"}],"version-history":[{"count":0,"href":"https:\/\/helloblog.io\/ro\/wp-json\/wp\/v2\/posts\/205\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/helloblog.io\/ro\/wp-json\/wp\/v2\/media\/203"}],"wp:attachment":[{"href":"https:\/\/helloblog.io\/ro\/wp-json\/wp\/v2\/media?parent=205"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/helloblog.io\/ro\/wp-json\/wp\/v2\/categories?post=205"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/helloblog.io\/ro\/wp-json\/wp\/v2\/tags?post=205"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}