{"id":182,"date":"2026-02-05T06:56:29","date_gmt":"2026-02-05T05:56:29","guid":{"rendered":"https:\/\/helloblog.io\/lt\/wordpress-2026-grizta-prie-triju-pagrindiniu-leidimu-prasideda-7-0-planavimas\/"},"modified":"2026-02-05T06:56:29","modified_gmt":"2026-02-05T05:56:29","slug":"wordpress-2026-grizta-prie-triju-pagrindiniu-leidimu-prasideda-7-0-planavimas","status":"publish","type":"post","link":"https:\/\/helloblog.io\/lt\/wordpress-2026-grizta-prie-triju-pagrindiniu-leidimu-prasideda-7-0-planavimas\/","title":{"rendered":"WordPress 2026 m. gr\u012f\u017eta prie trij\u0173 pagrindini\u0173 leidim\u0173: startuoja ankstyvas 7.0 planavimas"},"content":{"rendered":"\n<p>2025 m. pabaigos \u201eCore Committers Check-in\u201c (ketvirtinis susitikimas tarp branduolio komiteri\u0172 ir projekto vadovyb\u0117s) atne\u0161\u0117 reik\u0161ming\u0105 naujien\u0105: 2026 m. WordPress planuoja gr\u012f\u017eti prie trij\u0173 pagrindini\u0173 (major) leidim\u0173 ritmo. Tuo pa\u010diu jau prad\u0117tos ankstyvos diskusijos apie WordPress 7.0 krypt\u012f: kokios funkcijos gal\u0117t\u0173 patekti \u012f 7.0, kaip jud\u0117s admin dizaino perpie\u0161imas, koki\u0105 viet\u0105 ekosistemoje u\u017eims AI \u012frankiai ir ar laikas kelti minimali\u0105 palaikom\u0105 PHP versij\u0105.<\/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\/20\/2026\/02\/core-committers-check-in-feature-img.jpg\" alt=\"WordPress \u012fra\u0161o ekrano nuotrauka \u201eCore Committers Check-in \u2013 November 2025\u201c\" class=\"wp-image-181\" srcset=\"https:\/\/helloblog.io\/app\/uploads\/sites\/20\/2026\/02\/core-committers-check-in-feature-img.jpg 2000w, https:\/\/helloblog.io\/app\/uploads\/sites\/20\/2026\/02\/core-committers-check-in-feature-img-300x200.jpg 300w, https:\/\/helloblog.io\/app\/uploads\/sites\/20\/2026\/02\/core-committers-check-in-feature-img-1024x682.jpg 1024w, https:\/\/helloblog.io\/app\/uploads\/sites\/20\/2026\/02\/core-committers-check-in-feature-img-768x512.jpg 768w, https:\/\/helloblog.io\/app\/uploads\/sites\/20\/2026\/02\/core-committers-check-in-feature-img-1536x1024.jpg 1536w, https:\/\/helloblog.io\/app\/uploads\/sites\/20\/2026\/02\/core-committers-check-in-feature-img-400x267.jpg 400w\" sizes=\"auto, (max-width: 2000px) 100vw, 2000px\" \/><figcaption class=\"wp-element-caption\">\/ Make WordPress Core publikuot\u0173 susitikimo u\u017era\u0161\u0173 iliustracija. \u2014 <em>Forr\u00e1s: The Repository \/ Make WordPress Core<\/em><\/figcaption><\/figure>\n\n\n\n<p>Svarbus kontekstas: met\u0173 prad\u017eioje WordPress vykdomoji direktor\u0117 Mary Hubbard buvo paskelbusi, kad 2026 m. planuojamas tik vienas pagrindinis leidimas \u2013 motyvuojant \u201evykstan\u010diais teisiniais klausimais\u201c. Tai buvo siejama su WP Engine ie\u0161kiniu bei Automattic sprendimu pristabdyti WordPress ind\u0117l\u012f ir \u201esulyginti\u201c j\u012f su WP Engine, kol t\u0119siasi teisin\u0117 kova. Dabar, remiantis \u0161io ketvir\u010dio susitikimo u\u017era\u0161ais, kryptis v\u0117l kei\u010diasi \u2013 \u012f trij\u0173 major versij\u0173 model\u012f.<\/p>\n\n\n\n<div class=\"wp-block-group callout callout-info is-style-info is-layout-flow wp-block-group-is-layout-flow\" style=\"border-width:1px;border-radius:8px;padding-top:1rem;padding-right:1.5rem;padding-bottom:1rem;padding-left:1.5rem\">\n\n<h4 class=\"wp-block-heading callout-title\">Apie susitikimo format\u0105<\/h4>\n\n\n<p>Susitikimas vyko taikant <a href=\"https:\/\/www.chathamhouse.org\/about-us\/chatham-house-rule\">Chatham House Rule<\/a> \u2013 tai rei\u0161kia, kad galima cituoti bendr\u0105 turin\u012f, bet neatskleisti, kas konkre\u010diai k\u0105 pasak\u0117.<\/p>\n\n<\/div>\n\n\n\n<h2 class=\"wp-block-heading\">2026 m. leidim\u0173 ritmas: \u201eintencija\u201c gr\u012f\u017eti prie trij\u0173 major versij\u0173<\/h2>\n\n\n\n<p>Remiantis Make WordPress Core \u012fra\u0161u su susitikimo u\u017era\u0161ais (juos publikavo core committer Jonathan Desrosiers), komanda \u012fvardijo ai\u0161ki\u0105 \u201eintencij\u0105\u201c 2026 m. atnaujinti trij\u0173 pagrindini\u0173 leidim\u0173 per metus ritm\u0105. Kaip orientyras 7.0 versijai minimas kovo arba baland\u017eio laikotarpis.<\/p>\n\n\n\n<p>Vasario leidimas buvo atmestas. Prie\u017eastis prakti\u0161ka: jei 7.0 b\u016bt\u0173 taikomasi \u012f vasar\u012f, \u201ebeta 1\u201c krist\u0173 \u012f pa\u010di\u0105 sausio prad\u017ei\u0105, kai daug dalyvi\u0173 dar atostogauja. Be to, dalis \u0161iuo metu vystom\u0173 funkcij\u0173 papras\u010diausiai nesp\u0117t\u0173 pasiekti tokio brandos lygio, kad b\u016bt\u0173 realu jas stabiliai i\u0161leisti pagal tok\u012f grafik\u0105.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Ar major leidimai bus derinami su did\u017eiaisiais renginiais?<\/h3>\n\n\n\n<p>Susitikime taip pat aptarta id\u0117ja ateities major leidimus derinti prie \u201eflagship\u201c rengini\u0173 \u2013 pana\u0161iai kaip \u0161iemet WordPress 6.9 i\u0161leidimas buvo susietas su \u201eState of the Word\u201c.<\/p>\n\n\n\n<p>Visgi \u0161iai id\u0117jai \u012fvardinta ir kaina: leidim\u0173 derinimas prie kelioni\u0173, laiko zon\u0173, release squad (leidimo komandos) bei platesni\u0173 bendruomen\u0117s paj\u0117gum\u0173 gali prid\u0117ti nema\u017eai koordinavimo sud\u0117tingumo. D\u0117l to tai \u0161iuo metu laikoma galimybe, o ne patvirtintu planu, ir pa\u017eym\u0117ta kaip tema tolimesn\u0117ms diskusijoms.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Kas gal\u0117t\u0173 patekti \u012f WordPress 7.0: nuo Tabs bloko iki AI Client<\/h2>\n\n\n\n<p>Kartu su leidim\u0173 planavimu aptartos ir funkcijos, kurios i\u0161 prad\u017ei\u0173 buvo numatytos WordPress 6.9 apimtyje, bet dabar svarstomos kaip kandidat\u0117s \u012f 7.0. Tarp pamin\u0117t\u0173 kryp\u010di\u0173:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Template activation (\u0161ablon\u0173 aktyvavimas)<\/li>\n\n\n<li>Tabs block (korteli\u0173 \/ skirtuk\u0173 blokas)<\/li>\n\n\n<li>Client-side galimyb\u0117s Abilities API kontekste<\/li>\n\n\n<li>Client-side media editing (kliento pus\u0117s medijos redagavimas)<\/li>\n\n<\/ul>\n\n\n\n<p>Vis d\u0117lto did\u017eiausia ir i\u0161samiausia diskusij\u0173 dalis sukosi apie WordPress AI Client \u2013 komponent\u0105, kuris dabar jau rimtai svarstomas kaip kandidatas b\u016bti \u012ftrauktas \u012f WordPress core.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">WordPress AI Client: kas tai ir kod\u0117l tai svarbu branduoliui<\/h3>\n\n\n\n<p>WordPress AI Client \u2013 tai native (platformi\u0161kai \u201esavas\u201c) ir provider-agnostic (tiek\u0117jo at\u017evilgiu neutralus) b\u016bdas pluginams ir temoms integruotis su AI paslaugomis. Praktikoje tai rei\u0161kia, kad kuriant AI funkcionalum\u0105 nereikia kiekvienam \u012fskiepiui atskirai \u201eprisiri\u0161ti\u201c prie vieno konkretaus tiek\u0117jo ar hardcodinti specifini\u0173 modeli\u0173 \u2013 atsiranda bendras, WordPress stili\u0173 atitinkantis sluoksnis integracijoms.<\/p>\n\n\n\n<p>Pagal paskelbt\u0105 informacij\u0105, WordPress AI Client 0.1.0 versija pasirod\u0117 prie\u0161 savait\u0119 iki aptariamo susitikimo. Ji adaptuoja <a href=\"https:\/\/github.com\/WordPress\/php-ai-client\">PHP AI Client<\/a> \u012f WordPress konvencijas ir sprend\u017eia kelias labai prakti\u0161kas problemas:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Naudoja WordPress HTTP API u\u017eklausoms \u012f AI paslaugas (vietoje to, kad kiekvienas \u012fskiepis atsine\u0161t\u0173 savo HTTP sluoksn\u012f).<\/li>\n\n\n<li>Centralizuoja API raktus per \u201eAI Credentials\u201c ekran\u0105 (viena vieta valdyti kredencialus).<\/li>\n\n\n<li>Sprend\u017eia modelio parinkim\u0105 taip, kad pluginams nereik\u0117t\u0173 hardcodinti konkre\u010di\u0173 provider\u2019i\u0173.<\/li>\n\n\n<li>Formuoja pagrind\u0105 ekosistemai kurti ant bendr\u0173 pamat\u0173, susijusi\u0173 su Abilities API.<\/li>\n\n<\/ul>\n\n\n\n<p>Taip pat ai\u0161kiai \u012fvardinta, kas planuojama ateities AI Client laidose:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Abilities API palaikymas<\/li>\n\n\n<li>REST endpoint\u2019ai<\/li>\n\n\n<li>Client-side Prompt Builder (kliento pus\u0117s u\u017eklaus\u0173 \/ prompt\u0173 konstruktorius)<\/li>\n\n<\/ul>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>Because the AI client is a great way to encourage the ecosystem to build around solid foundations (such as the Abilities API), the ideal home for this is Core itself. The combining of these related APIs will unlock so many possibilities for developers and site owners.<\/p>\n<cite>Susitikimo u\u017era\u0161ai (Make WordPress Core)<\/cite><\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Core \u012ftraukimo ribos: WordPress turi likti neutralus<\/h3>\n\n\n\n<p>Jei AI Client keliaus \u012f core, komanda ai\u0161kiai akcentuoja kelis apribojimus ir principus. Pirmas \u2013 WordPress \u201evisada i\u0161liks agnostinis\u201c: \u012ftraukti konkret\u0173 AI model\u012f arba integruotis tik su dalimi tre\u010di\u0173j\u0173 \u0161ali\u0173 paslaug\u0173 ilgalaik\u0117je perspektyvoje n\u0117ra tvaru.<\/p>\n\n\n\n<p>Taip pat buvo paliestos ir ilgalaik\u0117s galimyb\u0117s: ateityje daugiau potencialo gali atsirasti i\u0161 besiformuojan\u010di\u0173 machine-based ar browser-level modeli\u0173 (pvz., veikian\u010di\u0173 ar\u010diau \u012frenginio \/ nar\u0161ykl\u0117s). Ta\u010diau jokios krypties susitikime nebuvo pasirinkta.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Prie\u0161 sprendim\u0105 \u2013 ai\u0161k\u016bs \u201edefault WordPress\u201c naudojimo scenarijai<\/h3>\n\n\n\n<p>Prie\u0161 priimant sprendim\u0105 d\u0117l AI Client vietos core, dalyviai nori matyti ai\u0161kiai suformuluotus naudojimo scenarijus \u201edefault WordPress\u201c aplinkoje \u2013 t. y. k\u0105 AI duos ne tik integruotojams ar produkt\u0173 komandoms, bet ir standartinei WordPress instaliacijai. Kaip pavyzd\u017eiai minimi:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Medijos bibliotekos paie\u0161ka pagal konkret\u0173 turin\u012f \/ tem\u0105 (pvz., rasti nuotraukas su tam tikru objektu ar siu\u017eetu).<\/li>\n\n\n<li>Naujienlai\u0161ki\u0173 generavimas remiantis neseniai publikuotu turiniu.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Admin perpie\u0161imas: ne revoliucija, o \u201e\u0161vie\u017eias da\u017e\u0173 sluoksnis\u201c<\/h2>\n\n\n\n<p>Kita svarbi tema \u2013 admin s\u0105sajos (wp-admin) atnaujinimas. Susitikimo metu dalyviams buvo ai\u0161kiai pasakyta, kad tikslas n\u0117ra pilnas perstatymas nuo nulio. Vietoje to kalbama apie \u201enew coat of paint\u201c \u2013 t. y. \u0161velnesn\u012f atnaujinim\u0105, kuris atgaivina tai, kas jau yra, bet nesiekia radikaliai keisti vis\u0173 admin paradigmini\u0173 sprendim\u0173.<\/p>\n\n\n\n<p>\u0160is patikslinimas svarbus d\u0117l ankstesnio konteksto: per liepos ketvir\u010dio susitikim\u0105 buvo aptarta, ar perpie\u0161im\u0105 testuoti kaip eksperiment\u0105 Gutenberg \u012fskiepyje, ar leisti atskir\u0105 \u201eMP7\u201c \u012fskiep\u012f. Tai b\u016bt\u0173 aliuzija \u012f MP6 \u2013 2013 m. \u201efeature as a plugin\u201c model\u012f (kai funkcija pirmiausia vystoma kaip \u012fskiepis), kuris stipriai suformavo WordPress 3.8 admin dizaino atnaujinim\u0105.<\/p>\n\n\n\n<p>Admin perpie\u0161imas yra Gutenberg kelrod\u017eio (roadmap) Phase 3: Collaboration dalis. Darbai \u0161ia kryptimi prasid\u0117jo 2023 m., kai Gutenberg Lead Architect Mat\u00edas Ventura pasidalijo savo vizija modernizuoti administravimo patirt\u012f, o v\u0117liau 2023 m. \u201eState of the Word\u201c metu demonstravo naujus i\u0161d\u0117stymus.<\/p>\n\n\n\n<p>\u012edomi detal\u0117: ankstyvas admin perpie\u0161imo \u201epreview\u201c, kur\u012f i\u0161 prad\u017ei\u0173 buvo planuota i\u0161leisti kartu su WordPress 6.9, rugs\u0117j\u012f buvo pad\u0117tas \u012f \u0161al\u012f. Roadmap atnaujinime tuomet atsirado formuluot\u0117, kad tai \u201eno longer planned based on the current state of work\u201c \u2013 kitaip tariant, pagal esam\u0105 progreso b\u016bkl\u0119 tai neb\u0117ra suplanuota.<\/p>\n\n\n\n<p>\u0160iuo metu vis dar n\u0117ra ai\u0161kios datos, kada perpie\u0161tas admin gal\u0117t\u0173 pasiekti WordPress core. Paskutinis didelis admin atnaujinimas buvo i\u0161leistas daugiau nei prie\u0161 de\u0161imtmet\u012f \u2013 WordPress 3.8 laikais.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Minimalios PHP versijos k\u0117limas: kod\u0117l kalbama apie 7.4?<\/h2>\n\n\n\n<p>Susitikime taip pat ie\u0161kota \u201e\u012ftikinam\u0173 prie\u017eas\u010di\u0173\u201c kelti minimali\u0105 palaikom\u0105 PHP versij\u0105 iki 7.4. Diskusija buvo labiau apie realius techninius limitus nei apie formal\u0173 \u201enor\u0105 atsinaujinti\u201c.<\/p>\n\n\n\n<p>Pagrindin\u0117 argument\u0173 a\u0161is tokia: senesn\u0117s PHP versijos ver\u010dia WordPress ilgai i\u0161laikyti suderinamumo sluoksnius, kurie didina \u201ebloat\u201c (apkrautum\u0105) ir l\u0117tina vystym\u0105. PHP 7.4 riba, pagal aptartus motyvus, leist\u0173:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Jud\u0117ti link nuoseklesnio tipavimo (typing) visame kode.<\/li>\n\n\n<li>Palengvinti kodo \u201esuprantamum\u0105\u201c tiek \u017emon\u0117ms programuotojams, tiek AI sistemoms, kurios analizuoja kod\u0105.<\/li>\n\n\n<li>Atsiri\u0161ti nuo dalies dirbtini\u0173 apribojim\u0173, kuriuos kelia labai seni PHP palaikymo \u012fsipareigojimai.<\/li>\n\n<\/ul>\n\n\n\n<p>Dar vienas prakti\u0161kas argumentas \u2013 tre\u010di\u0173j\u0173 \u0161ali\u0173 AI SDK. Buvo pasteb\u0117ta, kad nema\u017ea j\u0173 dalis jau reikalauja naujesni\u0173 PHP versij\u0173. Jei WordPress minimumas lieka per \u017eemas, projektas negali realisti\u0161kai naudoti toki\u0173 SDK (arba tai tampa neproporcingai sud\u0117tinga).<\/p>\n\n\n\n<p>Tuo pa\u010diu diskusija ai\u0161kiai buvo \u012fr\u0117minta kaip balanso paie\u0161ka: progresas prie\u0161 suderinamum\u0105 ir nor\u0105 \u201enepalikti nieko u\u017e borto\u201c. Susitikimo metu sprendimas nebuvo priimtas.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Kas toliau: atviri formatai, grafikas ir 7.0\/7.1 apimtys<\/h2>\n\n\n\n<p>Susitikimo pabaigoje Jonathan Desrosiers u\u017efiksavo kelis konkre\u010dius \u201efollow-up\u201c punktus, kuriuos komanda nor\u0117t\u0173 pajudinti po \u0161ios sesijos:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Pasi\u016blyti atviresnius ir pusiau atvirus susitikim\u0173 formatus (more open and semi-open meeting formats).<\/li>\n\n\n<li>Publikuoti 2026 m. leidim\u0173 grafik\u0105 (release schedule).<\/li>\n\n\n<li>Patvirtinti taikomas 7.0 (ir galimai 7.1) funkcijas.<\/li>\n\n\n<li>\u012evertinti, ar realu ir prakti\u0161ka major leidimus koordinuoti su gyvais, fiziniais renginiais (in-person events).<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Trumpa santrauka WordPress k\u016br\u0117jams<\/h2>\n\n\n\n<p>Jei dirbi su WordPress produktais ar klientiniais projektais, i\u0161 \u0161i\u0173 diskusij\u0173 verta i\u0161sine\u0161ti kelis ai\u0161kius signalus. 2026 m. v\u0117l taikomasi \u012f trij\u0173 major leidim\u0173 ritm\u0105, o 7.0 langas realisti\u0161kai stumiamas \u012f kov\u0105\u2013baland\u012f. AI kryptis stipr\u0117ja per AI Client (provider\u2019i\u0173 at\u017evilgiu neutral\u0173 SDK sluoksn\u012f), admin atnaujinimas pozicionuojamas kaip evoliucija, o ne revoliucija, o PHP minimumo k\u0117limas iki 7.4 gr\u012f\u017eta \u012f rimtesn\u0119 darbotvark\u0119 \u2013 nors sprendim\u0173 kol kas n\u0117ra.<\/p>\n\n\n<div class=\"references-section\">\n                <h2>Nuorodos \/ \u0160altiniai<\/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\/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:\/\/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:\/\/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>WordPress branduolio komanda planuoja 2026 m. v\u0117l leisti tris pagrindines versijas, o WordPress 7.0 taikomasi \u012f kovo\u2013baland\u017eio lang\u0105. Kartu ant stalo \u2013 AI Client \u012ftraukimas \u012f core, atsargus admin atnaujinimas ir diskusija d\u0117l minimalaus PHP.<\/p>\n","protected":false},"author":2,"featured_media":180,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[25,20,26,27,18],"class_list":["post-182","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wordpress","tag-ai","tag-gutenberg","tag-php","tag-release-management","tag-wordpress-core"],"_links":{"self":[{"href":"https:\/\/helloblog.io\/lt\/wp-json\/wp\/v2\/posts\/182","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/helloblog.io\/lt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/helloblog.io\/lt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/helloblog.io\/lt\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/helloblog.io\/lt\/wp-json\/wp\/v2\/comments?post=182"}],"version-history":[{"count":0,"href":"https:\/\/helloblog.io\/lt\/wp-json\/wp\/v2\/posts\/182\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/helloblog.io\/lt\/wp-json\/wp\/v2\/media\/180"}],"wp:attachment":[{"href":"https:\/\/helloblog.io\/lt\/wp-json\/wp\/v2\/media?parent=182"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/helloblog.io\/lt\/wp-json\/wp\/v2\/categories?post=182"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/helloblog.io\/lt\/wp-json\/wp\/v2\/tags?post=182"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}