{"id":164,"date":"2026-02-05T06:56:21","date_gmt":"2026-02-05T05:56:21","guid":{"rendered":"https:\/\/helloblog.io\/cs\/wordpress-v-roce-2026-miri-zpet-ke-trem-velkym-vydanim-startuje-i-planovani-7-0\/"},"modified":"2026-02-05T06:56:21","modified_gmt":"2026-02-05T05:56:21","slug":"wordpress-v-roce-2026-miri-zpet-ke-trem-velkym-vydanim-startuje-i-planovani-7-0","status":"publish","type":"post","link":"https:\/\/helloblog.io\/cs\/wordpress-v-roce-2026-miri-zpet-ke-trem-velkym-vydanim-startuje-i-planovani-7-0\/","title":{"rendered":"WordPress v roce 2026 m\u00ed\u0159\u00ed zp\u011bt ke t\u0159em velk\u00fdm vyd\u00e1n\u00edm. Startuje i pl\u00e1nov\u00e1n\u00ed 7.0"},"content":{"rendered":"\n<p>WordPress projekt podle intern\u00edch pozn\u00e1mek z pravideln\u00e9ho setk\u00e1n\u00ed core committer\u016f znovu po\u010d\u00edt\u00e1 s t\u00edm, \u017ee v roce 2026 vyjdou <strong>t\u0159i major verze<\/strong>. Z\u00e1rove\u0148 u\u017e b\u011b\u017e\u00ed prvn\u00ed debaty o tom, co by mohlo (a co by naopak nem\u011blo) stihnout WordPress 7.0 \u2013 v\u010detn\u011b t\u00e9mat jako redesign administrace, minim\u00e1ln\u00ed podporovan\u00e1 verze PHP nebo to, jakou roli bude hr\u00e1t AI v budouc\u00edm v\u00fdvoji.<\/p>\n\n\n\n<p>Cel\u00e9 shrnut\u00ed vych\u00e1z\u00ed z \u201eCore Committers Check-in \u2013 November 2025\u201c, kde se core committe\u0159i a veden\u00ed projektu bavili o kadenci vyd\u00e1v\u00e1n\u00ed, na\u010dasov\u00e1n\u00ed a kandid\u00e1tn\u00edch funkc\u00edch. Setk\u00e1n\u00ed prob\u011bhlo pod <strong>Chatham House Rule<\/strong> (\u00fa\u010dastn\u00edci mohou sd\u00edlet informace, ale ne p\u0159i\u0159azovat konkr\u00e9tn\u00ed v\u00fdroky konkr\u00e9tn\u00edm lidem nebo organizac\u00edm).<\/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\/11\/2026\/02\/core-committers-check-in-feature-img.jpg\" alt=\"Screenshot p\u0159\u00edsp\u011bvku na Make WordPress Core s n\u00e1zvem Core Committers Check-in \u2013 November 2025\" class=\"wp-image-163\" srcset=\"https:\/\/helloblog.io\/app\/uploads\/sites\/11\/2026\/02\/core-committers-check-in-feature-img.jpg 2000w, https:\/\/helloblog.io\/app\/uploads\/sites\/11\/2026\/02\/core-committers-check-in-feature-img-300x200.jpg 300w, https:\/\/helloblog.io\/app\/uploads\/sites\/11\/2026\/02\/core-committers-check-in-feature-img-1024x682.jpg 1024w, https:\/\/helloblog.io\/app\/uploads\/sites\/11\/2026\/02\/core-committers-check-in-feature-img-768x512.jpg 768w, https:\/\/helloblog.io\/app\/uploads\/sites\/11\/2026\/02\/core-committers-check-in-feature-img-1536x1024.jpg 1536w, https:\/\/helloblog.io\/app\/uploads\/sites\/11\/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<h2 class=\"wp-block-heading\">Pro\u010d je \u201et\u0159i major releasy\u201c zm\u011bna kurzu<\/h2>\n\n\n\n<p>To, \u017ee se WordPress vrac\u00ed ke t\u0159em major vyd\u00e1n\u00edm ro\u010dn\u011b, je v\u00fdznamn\u00fd obrat oproti d\u0159\u00edv\u011bj\u0161\u00edmu sd\u011blen\u00ed z pr\u016fb\u011bhu roku, kdy v\u00fdkonn\u00e1 \u0159editelka projektu Mary Hubbard ozn\u00e1mila, \u017ee v roce 2026 m\u00e1 vyj\u00edt <strong>jen jedna major verze<\/strong>. D\u016fvodem tehdy m\u011bly b\u00fdt \u201eprob\u00edhaj\u00edc\u00ed pr\u00e1vn\u00ed z\u00e1le\u017eitosti\u201c \u2013 v kontextu se mluvilo o soudn\u00edm sporu s WP Engine \u2013 a tak\u00e9 o tom, \u017ee Automattic do\u010dasn\u011b <strong>pozastavil \u010d\u00e1st p\u0159\u00edsp\u011bvk\u016f do WordPressu<\/strong> v n\u00e1vaznosti na prob\u00edhaj\u00edc\u00ed pr\u00e1vn\u00ed konflikt.<\/p>\n\n\n\n<p>Aktu\u00e1ln\u00ed pl\u00e1nov\u00e1n\u00ed tedy \u0159\u00edk\u00e1: zp\u00e1tky k vy\u0161\u0161\u00ed frekvenci. Nejde ale o definitivn\u00ed roadmapu do detailu; z pozn\u00e1mek je c\u00edtit sp\u00ed\u0161 \u201ez\u00e1m\u011br\u201c a pot\u0159eba dopracovat konkr\u00e9tn\u00ed harmonogram a c\u00edle jednotliv\u00fdch vyd\u00e1n\u00ed.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Kadence pro 2026: WordPress 7.0 m\u00ed\u0159\u00ed na b\u0159ezen nebo duben<\/h2>\n\n\n\n<p>Podle pozn\u00e1mek publikovan\u00fdch na Make WordPress Core je z\u00e1m\u011br v roce 2026 obnovit kadenci <strong>t\u0159\u00ed major vyd\u00e1n\u00ed<\/strong>. U WordPressu 7.0 se zmi\u0148uje c\u00edlen\u00ed na <strong>b\u0159ezen nebo duben<\/strong>.<\/p>\n\n\n\n<p>Varianta vyd\u00e1n\u00ed v \u00fanoru se na setk\u00e1n\u00ed vy\u0159adila. D\u016fvod je \u010dist\u011b praktick\u00fd: <strong>Beta 1<\/strong> by v takov\u00e9m p\u0159\u00edpad\u011b vych\u00e1zela na za\u010d\u00e1tku ledna \u2013 tedy v dob\u011b, kdy je \u010d\u00e1st p\u0159isp\u011bvatel\u016f je\u0161t\u011b na dovolen\u00fdch \u2013 a nav\u00edc n\u011bkolik rozpracovan\u00fdch v\u011bc\u00ed by se \u010dasov\u011b nestihlo dot\u00e1hnout.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Budou se major releasy \u010dasovat na \u201eflagship\u201c akce?<\/h2>\n\n\n\n<p>Na stole byla i my\u0161lenka sladit budouc\u00ed major vyd\u00e1n\u00ed s velk\u00fdmi komunitn\u00edmi ud\u00e1lostmi. Jako precedent se zmi\u0148uje leto\u0161n\u00ed vypu\u0161t\u011bn\u00ed WordPressu 6.9 v obdob\u00ed State of the Word.<\/p>\n\n\n\n<p>Z\u00e1rove\u0148 padly i d\u016fle\u017eit\u00e9 protiargumenty: koordinovat vyd\u00e1n\u00ed podle cestov\u00e1n\u00ed, \u010dasov\u00fdch p\u00e1sem a dostupnosti release squadu i p\u0159isp\u011bvatel\u016f zvy\u0161uje organiza\u010dn\u00ed slo\u017eitost. V\u00fdsledek diskuse je, \u017ee to z\u016fst\u00e1v\u00e1 <strong>mo\u017enost<\/strong>, ne hotov\u00fd pl\u00e1n, a t\u00e9ma je ozna\u010den\u00e9 k dal\u0161\u00edmu rozpracov\u00e1n\u00ed.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Co by mohlo b\u00fdt ve WordPressu 7.0: kandid\u00e1ti z p\u016fvodn\u00edho scope pro 6.9<\/h2>\n\n\n\n<p>V diskusi se objevilo n\u011bkolik funkc\u00ed, kter\u00e9 byly p\u016fvodn\u011b zva\u017eovan\u00e9 pro WordPress 6.9 a te\u010f se \u0159e\u0161\u00ed jako potenci\u00e1ln\u00ed kandid\u00e1ti pro 7.0. Konkr\u00e9tn\u011b:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>template activation (aktivace \u0161ablon \/ templ\u00e1t\u016f \u2013 v kontextu pr\u00e1ce s templaty ve WordPressu)<\/li>\n\n\n<li>Tabs block (blok \u201ez\u00e1lo\u017eek\u201c)<\/li>\n\n\n<li>client-side abilities pro Abilities API (tedy \u010d\u00e1st schopnost\u00ed dostupn\u00e1 na stran\u011b klienta)<\/li>\n\n\n<li>client-side media editing (editace m\u00e9di\u00ed na stran\u011b klienta)<\/li>\n\n<\/ul>\n\n\n\n<p>Z t\u011bchto bod\u016f ale nejv\u011bt\u0161\u00ed prostor dostalo t\u00e9ma AI \u2013 konkr\u00e9tn\u011b WordPress AI Client.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">WordPress AI Client: pro\u010d je to pro core tak l\u00e1kav\u00e9<\/h2>\n\n\n\n<p>Nejrozs\u00e1hlej\u0161\u00ed \u010d\u00e1st debaty se to\u010dila kolem <strong>WordPress AI Client<\/strong>. Jde o jeden ze \u010dty\u0159 \u201eBuilding Blocks\u201c (stavebn\u00edch kamen\u016f) AI t\u00fdmu a nov\u011b se v\u00e1\u017en\u011b zva\u017euje, jestli by se nem\u011bl st\u00e1t sou\u010d\u00e1st\u00ed j\u00e1dra (core).<\/p>\n\n\n\n<p>D\u016fle\u017eit\u00fd kontext: <strong>WordPress AI Client ve verzi 0.1.0<\/strong> vy\u0161el kr\u00e1tce p\u0159ed setk\u00e1n\u00edm. C\u00edl je nab\u00eddnout \u201enativn\u00ed\u201c a z\u00e1rove\u0148 <strong>provider-agnostic<\/strong> p\u0159\u00edstup (tj. nez\u00e1visl\u00fd na konkr\u00e9tn\u00edm poskytovateli) k tomu, jak pluginy a \u0161ablony komunikuj\u00ed s AI slu\u017ebami. N\u00e1stroj p\u0159izp\u016fsobuje projekt <em>PHP AI Client<\/em> WordPress konvenc\u00edm a v\u00fdvoj\u00e1\u0159sk\u00fdm zvyklostem.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Jak AI Client technicky zapad\u00e1 do WordPress ekosyst\u00e9mu<\/h3>\n\n\n\n<p>Z pozn\u00e1mek a souvisej\u00edc\u00edch ozn\u00e1men\u00ed vypl\u00fdv\u00e1 n\u011bkolik konkr\u00e9tn\u00edch vlastnost\u00ed, kter\u00e9 jsou pro WordPress ekosyst\u00e9m z\u00e1sadn\u00ed:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li><strong>Pou\u017e\u00edv\u00e1 WordPress HTTP API<\/strong> \u2013 tedy standardn\u00ed vrstvu pro HTTP po\u017eadavky v ekosyst\u00e9mu WordPressu, m\u00edsto aby si ka\u017ed\u00fd plugin tahal vlastn\u00ed implementaci.<\/li>\n\n\n<li><strong>Centralizuje API kl\u00ed\u010de<\/strong> do obrazovky \u201eAI Credentials\u201c \u2013 pluginy a \u0161ablony pak nemus\u00ed ka\u017ed\u00e1 \u0159e\u0161it vlastn\u00ed ukl\u00e1d\u00e1n\u00ed a UI pro p\u0159\u00edstupov\u00e9 \u00fadaje.<\/li>\n\n\n<li><strong>\u0158e\u0161\u00ed v\u00fdb\u011br modelu bez hard-codingu poskytovatele<\/strong> \u2013 v\u00fdvoj\u00e1\u0159 pluginu by nem\u011bl b\u00fdt nucen natvrdo integrovat konkr\u00e9tn\u00ed AI slu\u017ebu jen proto, aby nab\u00eddl jednu funkci.<\/li>\n\n\n<li>Je postaven\u00fd tak, aby se kolem n\u011bj dalo stav\u011bt stabiln\u00ed API a n\u00e1stroje pro ekosyst\u00e9m (v kombinaci s dal\u0161\u00edmi iniciativami).<\/li>\n\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Co je v pl\u00e1nu pro dal\u0161\u00ed verze AI Clientu<\/h3>\n\n\n\n<p>V ozn\u00e1men\u00fdch pl\u00e1nech do budoucna se zmi\u0148uj\u00ed konkr\u00e9tn\u00ed roz\u0161\u00ed\u0159en\u00ed:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>podpora <strong>Abilities API<\/strong><\/li>\n\n\n<li><strong>REST endpointy<\/strong> (rozhran\u00ed pro pr\u00e1ci p\u0159es WordPress REST API)<\/li>\n\n\n<li>client-side <strong>Prompt Builder<\/strong> (n\u00e1stroj na stran\u011b klienta pro skl\u00e1d\u00e1n\u00ed prompt\u016f)<\/li>\n\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Argument pro core: jednotn\u00e9 z\u00e1klady m\u00edsto rozt\u0159\u00ed\u0161t\u011bn\u00fdch integrac\u00ed<\/h3>\n\n\n\n<p>V pozn\u00e1mk\u00e1ch ze setk\u00e1n\u00ed zazn\u00edv\u00e1 pom\u011brn\u011b jasn\u00fd d\u016fvod, pro\u010d je AI Client vn\u00edman\u00fd jako siln\u00fd kandid\u00e1t pro core: m\u00e1 motivovat ekosyst\u00e9m, aby stav\u011bl na pevn\u00fdch z\u00e1kladech (nap\u0159\u00edklad pr\u00e1v\u011b na Abilities API), m\u00edsto aby ka\u017ed\u00fd plugin implementoval AI \u201epo sv\u00e9m\u201c.<\/p>\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>Pozn\u00e1mky ze setk\u00e1n\u00ed (Core Committers Check-in \u2013 November 2025)<\/cite><\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">AI v j\u00e1d\u0159e: agnostic p\u0159\u00edstup jako tvrd\u00fd po\u017eadavek<\/h2>\n\n\n\n<p>Sou\u010dasn\u011b se \u0159e\u0161ily i limity a rizika. V pozn\u00e1mk\u00e1ch je explicitn\u011b uveden\u00e9, \u017ee WordPress <strong>mus\u00ed z\u016fstat agnostic<\/strong> \u2013 tedy \u017ee nen\u00ed dlouhodob\u011b udr\u017eiteln\u00e9 p\u0159ibalit jeden konkr\u00e9tn\u00ed AI model nebo podporovat jen vybran\u00e9 third\u2011party slu\u017eby.<\/p>\n\n\n\n<p>Padla i pozn\u00e1mka, \u017ee dlouhodob\u00e9 mo\u017enosti m\u016f\u017eou p\u0159ij\u00edt t\u0159eba s nastupuj\u00edc\u00edmi modely b\u011b\u017e\u00edc\u00edmi \u201estrojov\u011b\u201c nebo na \u00farovni prohl\u00ed\u017ee\u010de, ale \u017e\u00e1dn\u00fd konkr\u00e9tn\u00ed sm\u011br se na setk\u00e1n\u00ed nevybral.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Nejd\u0159\u00edv use-cases v \u201edefault WordPressu\u201c<\/h3>\n\n\n\n<p>Ne\u017e se rozhodne o p\u0159\u00edpadn\u00e9m zahrnut\u00ed do core, chce komunita jasn\u00e9, srozumiteln\u00e9 sc\u00e9n\u00e1\u0159e pou\u017eit\u00ed p\u0159\u00edmo v z\u00e1kladn\u00edm WordPressu. Jako p\u0159\u00edklady zmi\u0148ovan\u00e9 v debat\u011b:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>vyhled\u00e1v\u00e1n\u00ed v Media Library podle konkr\u00e9tn\u00edho obsahu \/ t\u00e9matu (nap\u0159. naj\u00edt fotky s ur\u010dit\u00fdm motivem)<\/li>\n\n\n<li>generov\u00e1n\u00ed newsletter\u016f na z\u00e1klad\u011b ned\u00e1vno publikovan\u00e9ho obsahu<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Redesign administrace: sp\u00ed\u0161 facelift ne\u017e revoluce<\/h2>\n\n\n\n<p>Dal\u0161\u00ed velk\u00e9 t\u00e9ma byla <strong>modernizace administrace<\/strong>. Zazn\u011blo up\u0159esn\u011bn\u00ed, \u017ee aktu\u00e1ln\u00ed snaha nem\u00ed\u0159\u00ed na kompletn\u00ed p\u0159estavbu, ale sp\u00ed\u0161 na \u201efresh coat of paint\u201c \u2013 tedy vizu\u00e1ln\u00ed a UX osv\u011b\u017een\u00ed toho, co u\u017e existuje, m\u00edsto tot\u00e1ln\u00edho p\u0159eps\u00e1n\u00ed.<\/p>\n\n\n\n<p>Tohle navazuje na debaty z \u010dervencov\u00e9ho kvart\u00e1ln\u00edho setk\u00e1n\u00ed, kde se \u0159e\u0161ilo, jestli redesign otestovat experiment\u00e1ln\u011b v pluginu Gutenberg, nebo ho vydat jako samostatn\u00fd plugin ve stylu \u201eMP7\u201c \u2013 co\u017e je z\u00e1m\u011brn\u00e1 nar\u00e1\u017eka na MP6 z roku 2013, kdy se \u010d\u00e1st funkc\u00ed nejd\u0159\u00edv vyv\u00edjela jako plugin (\u201efeature as a plugin\u201c) a n\u00e1sledn\u011b ovlivnila redesign administrace ve WordPressu 3.8.<\/p>\n\n\n\n<p>Redesign administrace pat\u0159\u00ed do <strong>Phase 3: Collaboration<\/strong> na Gutenberg roadmap\u011b. Pr\u00e1ce na tom za\u010dala u\u017e v roce 2023, kdy Mat\u00edas Ventura (Gutenberg Lead Architect) sd\u00edlel vizi modern\u011bj\u0161\u00ed admin zku\u0161enosti a pozd\u011bji ukazoval nov\u00e9 layouty i v r\u00e1mci State of the Word 2023.<\/p>\n\n\n\n<p>Zaj\u00edmav\u00fd detail: ran\u00fd n\u00e1hled redesignu administrace, kter\u00fd m\u011bl p\u016fvodn\u011b vyj\u00edt spole\u010dn\u011b s WordPress 6.9, byl v z\u00e1\u0159\u00ed odlo\u017een. Aktualizovan\u00e1 roadmapa tehdy uvedla, \u017ee to \u201eu\u017e nen\u00ed v pl\u00e1nu na z\u00e1klad\u011b aktu\u00e1ln\u00edho stavu pr\u00e1ce\u201c.<\/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\">Timeline zat\u00edm nikde<\/h4>\n\n\n<p>V pozn\u00e1mk\u00e1ch z\u016fst\u00e1v\u00e1, \u017ee pro redesign administrace st\u00e1le nen\u00ed stanoven\u00fd term\u00edn. Posledn\u00ed v\u00fdrazn\u00e9 osv\u011b\u017een\u00ed administrace je star\u00e9 v\u00edc ne\u017e dek\u00e1du \u2013 WordPress 3.8.<\/p>\n\n<\/div>\n\n\n\n<h2 class=\"wp-block-heading\">Minim\u00e1ln\u00ed PHP verze: debata o posunu na PHP 7.4<\/h2>\n\n\n\n<p>Setk\u00e1n\u00ed se dotklo i ot\u00e1zky, jestli nenastal \u010das zvednout minim\u00e1ln\u00ed podporovanou verzi PHP na <strong>7.4<\/strong>. Ne\u0161lo o ozn\u00e1men\u00e9 rozhodnut\u00ed, ale o hled\u00e1n\u00ed \u201ep\u0159esv\u011bd\u010div\u00fdch d\u016fvod\u016f\u201c, pro\u010d to ud\u011blat.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Pro\u010d zva\u017eovat PHP 7.4: m\u00e9n\u011b kompatibility, v\u00edc prostoru pro v\u00fdvoj<\/h3>\n\n\n\n<p>Argumentace byla postaven\u00e1 hlavn\u011b na praktick\u00fdch limitech:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Star\u0161\u00ed PHP verze nut\u00ed WordPress dr\u017eet kompatibilitu, kter\u00e1 p\u0159id\u00e1v\u00e1 <strong>bloat<\/strong> (zbyte\u010dnou z\u00e1t\u011b\u017e v k\u00f3du) a zpomaluje v\u00fdvoj.<\/li>\n\n\n<li>PHP 7.4 by posunulo k\u00f3d sm\u011brem ke <strong>konzistentn\u011bj\u0161\u00edmu typov\u00e1n\u00ed<\/strong>, co\u017e m\u016f\u017ee zjednodu\u0161it \u00fadr\u017ebu i orientaci v k\u00f3du.<\/li>\n\n\n<li>Zazn\u011blo i to, \u017ee konzistentn\u011bj\u0161\u00ed typov\u00e1n\u00ed pom\u00e1h\u00e1 nejen lidem, ale i <strong>AI syst\u00e9m\u016fm<\/strong> l\u00e9pe porozum\u011bt k\u00f3du.<\/li>\n\n\n<li>\u0158ada third\u2011party AI SDK u\u017e dnes vy\u017eaduje nov\u011bj\u0161\u00ed PHP; p\u0159\u00edli\u0161 n\u00edzk\u00e9 minimum blokuje mo\u017enost tyto knihovny rozumn\u011b pou\u017e\u00edt.<\/li>\n\n<\/ul>\n\n\n\n<p>Sou\u010dasn\u011b se zd\u016fraz\u0148ovalo, \u017ee jde o hled\u00e1n\u00ed rovnov\u00e1hy mezi posunem vp\u0159ed a t\u00edm, aby WordPress nep\u0159estal b\u00fdt pou\u017eiteln\u00fd pro \u010d\u00e1st u\u017eivatel\u016f. Na setk\u00e1n\u00ed nepadlo \u017e\u00e1dn\u00e9 fin\u00e1ln\u00ed rozhodnut\u00ed.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Co bude n\u00e1sledovat: otev\u0159en\u011bj\u0161\u00ed setk\u00e1n\u00ed a konkr\u00e9tn\u011bj\u0161\u00ed pl\u00e1n pro 2026<\/h2>\n\n\n\n<p>Z\u00e1v\u011brem se v pozn\u00e1mk\u00e1ch objevuje seznam navazuj\u00edc\u00edch krok\u016f, kter\u00e9 si komunita odn\u00e1\u0161\u00ed k dopracov\u00e1n\u00ed:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>navrhnout otev\u0159en\u011bj\u0161\u00ed a \u201esemi-open\u201c form\u00e1ty setk\u00e1n\u00ed<\/li>\n\n\n<li>publikovat vyd\u00e1vac\u00ed harmonogram pro rok 2026<\/li>\n\n\n<li>potvrdit c\u00edlen\u00e9 funkce pro WordPress 7.0 a p\u0159\u00edpadn\u011b i 7.1<\/li>\n\n\n<li>vyhodnotit, jestli je praktick\u00e9 koordinovat vyd\u00e1n\u00ed s osobn\u00edmi (in-person) akcemi<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Shrnut\u00ed pro v\u00fdvoj\u00e1\u0159e: na co se p\u0159ipravit u\u017e te\u010f<\/h2>\n\n\n\n<p>Pokud stav\u00ed\u0161 pluginy, \u0161ablony nebo integrace kolem WordPressu, z aktu\u00e1ln\u00edch sign\u00e1l\u016f je dobr\u00e9 vn\u00edmat hlavn\u011b t\u0159i v\u011bci: (1) major vyd\u00e1n\u00ed budou v roce 2026 pravd\u011bpodobn\u011b \u010dast\u011bj\u0161\u00ed (t\u0159i m\u00edsto jednoho), co\u017e zved\u00e1 n\u00e1roky na pr\u016fb\u011b\u017en\u00e9 testov\u00e1n\u00ed kompatibility; (2) AI Client se tla\u010d\u00ed do role spole\u010dn\u00e9ho z\u00e1kladu, ale s d\u016frazem na provider-agnostic p\u0159\u00edstup a jasn\u00e9 default use-cases; (3) ot\u00e1zka minima PHP 7.4 z\u016fst\u00e1v\u00e1 otev\u0159en\u00e1, ale argumenty pro posun se hromad\u00ed \u2013 zejm\u00e9na kv\u016fli rychlosti v\u00fdvoje a kompatibilit\u011b s modern\u00edmi SDK.<\/p>\n\n\n<div class=\"references-section\">\n                <h2>Reference \/ Zdroje<\/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, 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.chathamhouse.org\/about-us\/chatham-house-rule\" target=\"_blank\" rel=\"noopener noreferrer\">Chatham House Rule<\/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\/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\">WordPress 6.9 launch during the State of the Word<\/a><\/li><li><a href=\"https:\/\/make.wordpress.org\/core\/2023\/07\/12\/admin-design\/\" target=\"_blank\" rel=\"noopener noreferrer\">Admin design (Mat\u00edas Ventura vision post)<\/a><\/li><\/ul>\n            <\/div>","protected":false},"excerpt":{"rendered":"<p>Po obdob\u00ed zpomalen\u00ed se WordPress podle pozn\u00e1mek z Core Committers Check-in vrac\u00ed k rytmu t\u0159\u00ed major verz\u00ed ro\u010dn\u011b. Ve h\u0159e je WordPress 7.0 na b\u0159ezen\/duben, AI Client v j\u00e1d\u0159e, facelift administrace i debata o minimu PHP 7.4.<\/p>\n","protected":false},"author":33,"featured_media":162,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17],"tags":[29,24,26,28,10],"class_list":["post-164","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\/cs\/wp-json\/wp\/v2\/posts\/164","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/helloblog.io\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/helloblog.io\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/helloblog.io\/cs\/wp-json\/wp\/v2\/users\/33"}],"replies":[{"embeddable":true,"href":"https:\/\/helloblog.io\/cs\/wp-json\/wp\/v2\/comments?post=164"}],"version-history":[{"count":0,"href":"https:\/\/helloblog.io\/cs\/wp-json\/wp\/v2\/posts\/164\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/helloblog.io\/cs\/wp-json\/wp\/v2\/media\/162"}],"wp:attachment":[{"href":"https:\/\/helloblog.io\/cs\/wp-json\/wp\/v2\/media?parent=164"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/helloblog.io\/cs\/wp-json\/wp\/v2\/categories?post=164"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/helloblog.io\/cs\/wp-json\/wp\/v2\/tags?post=164"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}