WordPress core t\u00edm za\u010dal konkr\u00e9tne rie\u0161i\u0165, ako bude vyzera\u0165 release cadence (tempo vyd\u00e1vania) v roku 2026 \u2013 a pod\u013ea zverejnen\u00fdch pozn\u00e1mok zo \u0161tvr\u0165ro\u010dn\u00e9ho stretnutia core committerov je \u201eintention\u201c (z\u00e1mer) vr\u00e1ti\u0165 sa sp\u00e4\u0165 k trom ve\u013ek\u00fdm verzi\u00e1m za rok. Popri term\u00ednoch sa otvorili aj t\u00e9my, ktor\u00e9 bud\u00fa pre v\u00fdvoj\u00e1rov d\u00f4le\u017eit\u00e9: skor\u00e9 pl\u00e1novanie WordPressu 7.0, pokra\u010duj\u00faci redizajn administr\u00e1cie a aj to, ako sa do bud\u00facnosti premietne AI (umelej inteligencie) v samotnom jadre.<\/p>\n\n\n\n
Stretnutie prebehlo pod Chatham House Rule<\/a>, \u010do v praxi znamen\u00e1, \u017ee \u00fa\u010dastn\u00edci m\u00f4\u017eu zdie\u013ea\u0165 obsah diskusie, ale bez prip\u00edsania konkr\u00e9tnych v\u00fdrokov konkr\u00e9tnym osob\u00e1m. Pre komunitu je tak\u00fdto form\u00e1t kompromis: dostaneme smerovanie a rozhodovacie krit\u00e9ri\u00e1, ale nie intern\u00e9 cit\u00e1cie.<\/p>\n\n\n\n Z\u00e1mer na rok 2026 predstavuje odklon od skor\u0161ej komunik\u00e1cie z toho ist\u00e9ho roka, ke\u010f v\u00fdkonn\u00e1 riadite\u013eka WordPress projektu Mary Hubbard ozn\u00e1mila, \u017ee v roku 2026 by sa mal vyda\u0165 iba jeden major release. D\u00f4vodom mali by\u0165 \u201eongoing legal matters\u201c \u2013 nar\u00e1\u017eka na s\u00fadny spor okolo WP Engine \u2013 a tie\u017e fakt, \u017ee Automattic v tom \u010dase pozastavil (resp. v\u00fdrazne obmedzil) pr\u00edspevky do WordPressu.<\/p>\n\n\n\n V praxi to znamen\u00e1, \u017ee pl\u00e1novanie releasov sa zjavne znova stabilizuje a core t\u00edm si ver\u00ed vr\u00e1ti\u0165 sa k rytmu, na ktor\u00fd je ekosyst\u00e9m (agent\u00fary, hosteri, autori pluginov a t\u00e9m) historicky zvyknut\u00fd.<\/p>\n\n\n\n Pod\u013ea pozn\u00e1mok zo stretnutia, ktor\u00e9 na Make WordPress Core publikoval core committer Jonathan Desrosiers, sa WordPress 7.0 predbe\u017ene mieri na marec alebo apr\u00edl 2026. Febru\u00e1rov\u00fd term\u00edn sa vyhodnotil ako nere\u00e1lny \u2013 beta 1 by vy\u0161la u\u017e za\u010diatkom janu\u00e1ra, ke\u010f je \u010das\u0165 prispievate\u013eov e\u0161te na dovolenk\u00e1ch, a z\u00e1rove\u0148 viacer\u00e9 rozpracovan\u00e9 funkcie by neboli pripraven\u00e9 v\u010das.<\/p>\n\n\n\n V diskusii padol aj n\u00e1pad koordinova\u0165 bud\u00face major release-y s ve\u013ek\u00fdmi komunitn\u00fdmi udalos\u0165ami \u2013 podobne, ako sa tento rok WordPress 6.9 sp\u00e1jal so State of the Word. Z\u00e1rove\u0148 v\u0161ak zaznelo, \u017ee tak\u00e1to koordin\u00e1cia by priniesla \u010fal\u0161iu vrstvu komplik\u00e1ci\u00ed: cestovanie, \u010dasov\u00e9 p\u00e1sma a dostupnos\u0165 release squad (t\u00edmu, ktor\u00fd release riadi) aj prispievate\u013eov.<\/p>\n\n\n\n D\u00f4le\u017eit\u00fd detail: nejde o hotov\u00fd pl\u00e1n, sk\u00f4r o mo\u017enos\u0165 ozna\u010den\u00fa na \u010fal\u0161iu diskusiu.<\/p>\n\n\n\n V r\u00e1mci pl\u00e1novania 7.0 sa spom\u00ednali aj funkcie, ktor\u00e9 boli p\u00f4vodne zva\u017eovan\u00e9 pre WordPress 6.9. Ako kandid\u00e1ti pre 7.0 zazneli:<\/p>\n\n\n\n Z poh\u013eadu v\u00fdvoj\u00e1ra je podstatn\u00e9, \u017ee nejde len o jeden \u201eheadline\u201c feature. 7.0 sa m\u00f4\u017ee sta\u0165 vydan\u00edm, ktor\u00e9 posp\u00e1ja viac rozpracovan\u00fdch l\u00edni\u00ed: blokov\u00fd editor, nov\u00e9 API a postupn\u00e9 pos\u00favanie WordPressu smerom k modernej\u0161iemu v\u00fdvoj\u00e1rskemu z\u00e1kladu.<\/p>\n\n\n\n Najviac priestoru si na stretnut\u00ed zobral WordPress AI Client \u2013 jedna zo \u0161tyroch \u201eBuilding Blocks\u201c (stavebn\u00fdch kame\u0148ov) od AI t\u00edmu, ktor\u00e1 sa u\u017e re\u00e1lne posudzuje ako kandid\u00e1t na za\u010dlenenie do jadra.<\/p>\n\n\n\n WordPress AI Client je nat\u00edvny, provider-agnostic (nez\u00e1visl\u00fd od konkr\u00e9tneho poskytovate\u013ea) sp\u00f4sob, ako maj\u00fa pluginy a t\u00e9my komunikova\u0165 so slu\u017ebami umelej inteligencie. Prakticky ide o SDK vrstvu, ktor\u00e1 preber\u00e1 koncepty z PHP AI Client<\/a>, ale prisp\u00f4sobuje ich WordPress konvenci\u00e1m a infra\u0161trukt\u00fare.<\/p>\n\n\n\n Verzia 0.1.0 WordPress AI Clientu vy\u0161la \u201eminul\u00fd t\u00fd\u017ede\u0148\u201c (v kontexte pozn\u00e1mok zo stretnutia). U\u017e v tejto ranej f\u00e1ze m\u00e1 nieko\u013eko konkr\u00e9tnych technick\u00fdch vlastnost\u00ed, ktor\u00e9 s\u00fa pre ekosyst\u00e9m k\u013e\u00fa\u010dov\u00e9:<\/p>\n\n\n\n A roadmapa pre \u010fal\u0161ie verzie je postaven\u00e1 na doplnen\u00ed vrstiev, ktor\u00e9 s\u00fa pre produk\u010dn\u00e9 pou\u017eitie z\u00e1sadn\u00e9:<\/p>\n\n\n\n Argument, ktor\u00fd z pozn\u00e1mok vyznieva najjasnej\u0161ie, je \u201efoundation first\u201c: ak m\u00e1 ekosyst\u00e9m budova\u0165 AI funkcionalitu, je v\u00fdhodnej\u0161ie, aby existoval spolo\u010dn\u00fd z\u00e1klad, na ktorom sa pluginy a t\u00e9my zhodn\u00fa. V pozn\u00e1mkach to priamo formuluj\u00fa tak, \u017ee AI Client pom\u00e1ha motivova\u0165 ekosyst\u00e9m stava\u0165 na pevn\u00fdch z\u00e1kladoch (napr\u00edklad Abilities API) a preto by jeho ide\u00e1lnym domovom mohol by\u0165 pr\u00e1ve Core. Kombin\u00e1cia s\u00favisiacich API m\u00e1 pod\u013ea nich odomkn\u00fa\u0165 ve\u013ea mo\u017enost\u00ed pre v\u00fdvoj\u00e1rov aj majite\u013eov webov.<\/p>\n\n\n\n Z\u00e1rove\u0148 sa otvorene pomenovali obmedzenia, ktor\u00e9 by museli plati\u0165, ak by AI Client mal by\u0165 s\u00fa\u010das\u0165ou core:<\/p>\n\n\n\n Sk\u00f4r ne\u017e sa urob\u00ed rozhodnutie o core integr\u00e1cii, prispievatelia chc\u00fa ma\u0165 pomenovan\u00e9 konkr\u00e9tne scen\u00e1re pou\u017eitia v r\u00e1mci \u201edefault WordPress\u201c \u2013 teda v \u0161tandardnej in\u0161tal\u00e1cii bez z\u00e1vislosti na \u0161pecifick\u00fdch komer\u010dn\u00fdch pluginoch. Ako pr\u00edklady zazneli:<\/p>\n\n\n\n T\u00e9ma redizajnu wp-admin sa vracia opakovane, ale tentoraz je d\u00f4le\u017eit\u00e9, \u010do presne sa komunikuje ako cie\u013e. Pod\u013ea pozn\u00e1mok \u00fa\u010dastn\u00edci dostali inform\u00e1ciu, \u017ee redizajn nem\u00e1 by\u0165 kompletn\u00fd overhaul, ale sk\u00f4r \u201enov\u00fd n\u00e1ter\u201c a refresh toho, \u010do u\u017e existuje.<\/p>\n\n\n\n T\u00e1to formul\u00e1cia je podstatn\u00e1 aj pre o\u010dak\u00e1vania: menej pravdepodobn\u00fd je ve\u013ek\u00fd jednorazov\u00fd skok, viac pravdepodobn\u00e1 postupn\u00e1 moderniz\u00e1cia UI, layoutov a konzistencie.<\/p>\n\n\n\n U\u017e na j\u00falovom \u0161tvr\u0165ro\u010dnom stretnut\u00ed sa rie\u0161ilo, ako redizajn testova\u0165: bu\u010f ako experiment v Gutenberg plugine, alebo ako samostatn\u00fd \u201eMP7\u201c plugin. Ide o historick\u00fa paralelu na MP6 \u2013 model \u201efeature as a plugin\u201c z roku 2013, ktor\u00fd pripravil p\u00f4du pre redizajn administr\u00e1cie vo WordPress 3.8.<\/p>\n\n\n\n Redizajn administr\u00e1cie je s\u00fa\u010das\u0165ou Phase 3: Collaboration na Gutenberg roadmape. Pr\u00e1ce v tomto smere sa za\u010dali v roku 2023, ke\u010f Gutenberg Lead Architect Mat\u00edas Ventura zdie\u013eal svoju v\u00edziu moderniz\u00e1cie admin experience a nesk\u00f4r ukazoval nov\u00e9 layouty aj po\u010das State of the Word 2023.<\/p>\n\n\n\n Zauj\u00edmav\u00fd moment je, \u017ee skor\u00fd preview redizajnu administr\u00e1cie mal p\u00f4vodne vyjs\u0165 spolu s WordPress 6.9, no v septembri bol odlo\u017een\u00fd \u2013 roadmapa sa aktualizovala s t\u00fdm, \u017ee to \u201eno longer planned based on the current state of work\u201c (u\u017e to nie je pl\u00e1novan\u00e9 vzh\u013eadom na aktu\u00e1lny stav rozpracovanosti).<\/p>\n\n\n\n Moment\u00e1lne st\u00e1le neexistuje verejn\u00fd term\u00edn, kedy sa redizajnovan\u00e1 administr\u00e1cia re\u00e1lne dostane do core. Posledn\u00fd ve\u013ek\u00fd refresh je pritom star\u0161\u00ed ne\u017e dek\u00e1da (WordPress 3.8).<\/p>\n\n\n\n \u010eal\u0161ia v\u00fdvoj\u00e1rsky citliv\u00e1 t\u00e9ma: minim\u00e1lna podporovan\u00e1 verzia PHP. Na stretnut\u00ed sa h\u013eadali \u201ecompelling reasons\u201c (siln\u00e9 d\u00f4vody), pre\u010do by sa minimum malo posun\u00fa\u0165 na PHP 7.4.<\/p>\n\n\n\n Argument\u00e1cia sa opierala o praktick\u00e9 limity star\u0161\u00edch PHP verzi\u00ed. Star\u00e9 verzie n\u00fatia WordPress dr\u017ea\u0165 sp\u00e4tn\u00fa kompatibilitu sp\u00f4sobom, ktor\u00fd prid\u00e1va bloat (nadbyto\u010dn\u00fa komplik\u00e1ciu\/objem) a spoma\u013euje v\u00fdvoj. PHP 7.4 by z\u00e1rove\u0148 posunulo codebase bli\u017e\u0161ie ku konzistentnej\u0161iemu typovaniu, \u010do u\u013eah\u010duje porozumenie k\u00f3du nielen v\u00fdvoj\u00e1rom, ale aj AI syst\u00e9mom, ktor\u00e9 sa pou\u017e\u00edvaj\u00fa pri anal\u00fdze a generovan\u00ed k\u00f3du.<\/p>\n\n\n\n Padol aj ve\u013emi pragmatick\u00fd d\u00f4vod: ve\u013ea third-party AI SDK u\u017e dnes vy\u017eaduje nov\u0161ie PHP verzie. Ak WordPress dr\u017e\u00ed minimum pr\u00edli\u0161 n\u00edzko, projekt si t\u00fdm zatv\u00e1ra dvere k pou\u017e\u00edvaniu existuj\u00facich kni\u017en\u00edc a integr\u00e1ci\u00ed (alebo si ich mus\u00ed reimplementova\u0165\/obch\u00e1dza\u0165).<\/p>\n\n\n\n Z\u00e1rove\u0148 sa to cel\u00e9 r\u00e1movalo ako h\u013eadanie rovnov\u00e1hy medzi progresom a t\u00fdm, aby pou\u017e\u00edvatelia \u201enezostali pozadu\u201c. Na stretnut\u00ed nepadlo rozhodnutie.<\/p>\n\n\n\n Jonathan Desrosiers v z\u00e1vere pozn\u00e1mok uviedol viacero follow-up bodov, ktor\u00e9 maj\u00fa posun\u00fa\u0165 pl\u00e1novanie do konkr\u00e9tnej\u0161ej roviny:<\/p>\n\n\n\n Ak vyv\u00edja\u0161 pluginy, t\u00e9my alebo udr\u017eiava\u0161 WordPress stack pre klientov, toto s\u00fa moment\u00e1lne najpraktickej\u0161ie implik\u00e1cie z diskusie core t\u00edmu:<\/p>\n\n\n\n Po obdob\u00ed spoma\u013eovania sa WordPress pod\u013ea pozn\u00e1mok core committerov chce v roku 2026 vr\u00e1ti\u0165 k trom major releasom. V hre je WordPress 7.0 na jar, WordPress AI Client v core, \u201efresh coat of paint\u201c pre admin a diskusia o minim\u00e1lnom PHP 7.4.<\/p>\n","protected":false},"author":38,"featured_media":175,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[49],"tags":[29,24,31,79,10],"class_list":["post-176","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ekosystem-wordpress","tag-ai","tag-core","tag-gutenberg","tag-php","tag-wordpress"],"_links":{"self":[{"href":"https:\/\/helloblog.io\/sk\/wp-json\/wp\/v2\/posts\/176","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/helloblog.io\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/helloblog.io\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/helloblog.io\/sk\/wp-json\/wp\/v2\/users\/38"}],"replies":[{"embeddable":true,"href":"https:\/\/helloblog.io\/sk\/wp-json\/wp\/v2\/comments?post=176"}],"version-history":[{"count":0,"href":"https:\/\/helloblog.io\/sk\/wp-json\/wp\/v2\/posts\/176\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/helloblog.io\/sk\/wp-json\/wp\/v2\/media\/175"}],"wp:attachment":[{"href":"https:\/\/helloblog.io\/sk\/wp-json\/wp\/v2\/media?parent=176"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/helloblog.io\/sk\/wp-json\/wp\/v2\/categories?post=176"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/helloblog.io\/sk\/wp-json\/wp\/v2\/tags?post=176"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}N\u00e1vrat k trom major verzi\u00e1m v roku 2026 (a pre\u010do to je zmena)<\/h2>\n\n\n\n
WordPress 7.0 cieli na marec alebo apr\u00edl 2026<\/h2>\n\n\n\n
Bud\u00fa sa major release-y viaza\u0165 na \u201eflagship\u201c eventy? Zatia\u013e len hypot\u00e9za<\/h3>\n\n\n\n
\u010co m\u00f4\u017ee prinies\u0165 WordPress 7.0: kandid\u00e1ti z p\u00f4vodn\u00e9ho scope pre 6.9<\/h2>\n\n\n\n
\n\n
Najv\u00e4\u010d\u0161ia debata: WordPress AI Client ako kandid\u00e1t do core<\/h2>\n\n\n\n
\u010co je WordPress AI Client (a pre\u010do je to d\u00f4le\u017eit\u00e9 pre pluginy a t\u00e9my)<\/h3>\n\n\n\n
\n\n
\n\n
Pre\u010do ho committers pova\u017euj\u00fa za dobr\u00e9ho kandid\u00e1ta do core<\/h3>\n\n\n\n
Limity a podmienky: WordPress mus\u00ed zosta\u0165 agnostick\u00fd<\/h3>\n\n\n\n
\n\n
Pred rozhodnut\u00edm chc\u00fa jasn\u00e9 use case-y v \u201edefault WordPress\u201c<\/h3>\n\n\n\n
\n\n
Redizajn administr\u00e1cie: sk\u00f4r \u201efresh coat of paint\u201c ne\u017e radik\u00e1lny prekop<\/h2>\n\n\n\n
Experiment v plugin-e? Gutenberg alebo \u201eMP7\u201c koncept<\/h3>\n\n\n\n
Kde to sed\u00ed na Gutenberg roadmape a \u010do sa stalo s preview pri 6.9<\/h3>\n\n\n\n
Diskusia o zv\u00fd\u0161en\u00ed minim\u00e1lnej verzie PHP na 7.4<\/h2>\n\n\n\n
Pre\u010do to core t\u00edm rie\u0161i: bloat, r\u00fdchlos\u0165 v\u00fdvoja a zrozumite\u013enos\u0165 k\u00f3du<\/h3>\n\n\n\n
AI SDKs a minim\u00e1lne PHP: praktick\u00e1 bari\u00e9ra<\/h3>\n\n\n\n
\u010co bude nasledova\u0165: otvorenej\u0161ie form\u00e1ty a konkr\u00e9tnej\u0161\u00ed pl\u00e1n pre 2026<\/h2>\n\n\n\n
\n\n
Zhrnutie pre v\u00fdvoj\u00e1rov: \u010do si z toho odnies\u0165 teraz<\/h2>\n\n\n\n
\n\n
Referencie \/ Zdroje<\/h2>\n