{"id":201,"date":"2026-02-05T06:56:30","date_gmt":"2026-02-05T05:56:30","guid":{"rendered":"https:\/\/helloblog.io\/hr\/wordpress-2026-tri-velika-izdanja-planiranje-7-0-ai-client-admin-redizajn-php-7-4\/"},"modified":"2026-02-05T06:56:30","modified_gmt":"2026-02-05T05:56:30","slug":"wordpress-2026-tri-velika-izdanja-planiranje-7-0-ai-client-admin-redizajn-php-7-4","status":"publish","type":"post","link":"https:\/\/helloblog.io\/hr\/wordpress-2026-tri-velika-izdanja-planiranje-7-0-ai-client-admin-redizajn-php-7-4\/","title":{"rendered":"WordPress u 2026. opet cilja na tri velika izdanja: rano planiranje za 7.0, AI Client u jezgru i novi smjer za admin"},"content":{"rendered":"\n<p>Na posljednjem kvartalnom sastanku Core committersa (Core Committers Check-in \u2013 November 2025) WordPress projekt je otvorio temu koja direktno utje\u010de na sve nas koji gradimo teme, pluginove i produkcijske siteove: ritam velikih izdanja u 2026. i vrlo rano pozicioniranje WordPressa 7.0.<\/p>\n\n\n\n<p>Prema bilje\u0161kama sa sastanka objavljenima na Make WordPress Core, namjera je vratiti se na <strong>tri velika (major) izdanja<\/strong> u 2026. Uz to, na stolu su konkretne teme: koje \u0107e se funkcionalnosti preliti u 7.0, kako \u0107e izgledati admin redizajn, gdje AI ulazi u pri\u010du i ho\u0107e li WordPress podi\u0107i minimalnu podr\u017eanu verziju PHP-a.<\/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\/22\/2026\/02\/core-committers-check-in-feature-img.jpg\" alt=\"Snimka zaslona blog objave \u201cCore Committers Check-in \u2013 November 2025\u201d\" class=\"wp-image-200\" srcset=\"https:\/\/helloblog.io\/app\/uploads\/sites\/22\/2026\/02\/core-committers-check-in-feature-img.jpg 2000w, https:\/\/helloblog.io\/app\/uploads\/sites\/22\/2026\/02\/core-committers-check-in-feature-img-300x200.jpg 300w, https:\/\/helloblog.io\/app\/uploads\/sites\/22\/2026\/02\/core-committers-check-in-feature-img-1024x682.jpg 1024w, https:\/\/helloblog.io\/app\/uploads\/sites\/22\/2026\/02\/core-committers-check-in-feature-img-768x512.jpg 768w, https:\/\/helloblog.io\/app\/uploads\/sites\/22\/2026\/02\/core-committers-check-in-feature-img-1536x1024.jpg 1536w, https:\/\/helloblog.io\/app\/uploads\/sites\/22\/2026\/02\/core-committers-check-in-feature-img-400x267.jpg 400w\" sizes=\"auto, (max-width: 2000px) 100vw, 2000px\" \/><figcaption class=\"wp-element-caption\">\/<em> Izvorna naslovna slika uz \u010dlanak o Core Committers Check-in sastanku <\/em>\/ \u2014 <em>Forr\u00e1s: The Repository<\/em><\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Povratak na tri major izdanja u 2026.<\/h2>\n\n\n\n<p>Najva\u017eniji zaklju\u010dak sastanka: WordPress se u 2026. \u017eeli vratiti na ritam od <strong>tri velika izdanja godi\u0161nje<\/strong>. To je zaokret u odnosu na raniju poruku iz iste godine, kada je izvr\u0161na direktorica Mary Hubbard komunicirala da bi 2026. trebala imati samo <strong>jedno<\/strong> major izdanje zbog \u201congoing legal matters\u201d &#8211; \u0161to se u kontekstu industrije povezivalo s WP Engine tu\u017ebom, kao i s Automatticovim smanjenjem doprinosa WordPressu tijekom pravnog spora.<\/p>\n\n\n\n<p>Sastanak je odr\u017ean pod <strong>Chatham House Rule<\/strong> (pravilo koje omogu\u0107uje slobodniju raspravu uz ograni\u010denja oko atribucije), a uz cadence\/raspored dotaknute su i teme oko WordPressa 7.0, admin redizajna, AI-ja te minimalne PHP verzije.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">WordPress 7.0 cilja na o\u017eujak ili travanj (velja\u010da otpada)<\/h2>\n\n\n\n<p>Prema bilje\u0161kama sa sastanka, WordPress 7.0 se okvirno cilja za <strong>o\u017eujak ili travanj<\/strong>. Velja\u010da je eksplicitno odba\u010dena kao opcija jer bi to gurnulo <strong>beta 1<\/strong> u rani sije\u010danj &#8211; period kada je velik dio kontribucijske baze na godi\u0161njim odmorima, a i nekoliko trenutno razvijanih funkcionalnosti ne bi bile spremne na vrijeme.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Uskla\u0111ivanje izdanja s flagship eventima: ideja postoji, plan jo\u0161 ne<\/h2>\n\n\n\n<p>Na sastanku se otvorila i ideja da se budu\u0107a major izdanja poku\u0161aju uskladiti s \u201cflagship\u201d doga\u0111ajima (u duhu ovogodi\u0161njeg scenarija gdje se WordPress 6.9 poklopio sa State of the Word). Me\u0111utim, zaklju\u010dak je da bi takva koordinacija unijela dodatnu slo\u017eenost: putovanja, vremenske zone, te dostupnost release squada i kontribuktora.<\/p>\n\n\n\n<p>Drugim rije\u010dima: to je zasad <strong>mogu\u0107nost<\/strong>, ne \u010dvrst plan, i ozna\u010deno je kao tema za dodatnu raspravu.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">\u0160to bi moglo u\u0107i u WordPress 7.0: kandidati iz 6.9 i nekoliko novih naglasaka<\/h2>\n\n\n\n<p>Dio funkcionalnosti koje su ranije bile razmatrane za WordPress 6.9 ponovno su spomenute kao kandidati za 7.0. U bilje\u0161kama se navode:<\/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 mogu\u0107nosti za Abilities API<\/li>\n\n\n<li>client-side media editing<\/li>\n\n<\/ul>\n\n\n\n<p>Ipak, najopse\u017eniji dio rasprave nije bio o blokovima ili editoru, nego o AI infrastrukturi &#8211; konkretno o <strong>WordPress AI Clientu<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">WordPress AI Client: za\u0161to je 0.1.0 va\u017ean i za\u0161to se razmatra core<\/h2>\n\n\n\n<p>WordPress AI Client je jedan od \u010detiri \u201cBuilding Blocks\u201d koje je definirao AI Team, a sada se ozbiljno razmatra i kao kandidat za uklju\u010divanje u <strong>core<\/strong> (jezgru WordPressa). Prema navodima, <strong>WordPress AI Client 0.1.0<\/strong> je iza\u0161ao tjedan prije sastanka.<\/p>\n\n\n\n<p>U praksi, WordPress AI Client je klijentski sloj (SDK) koji pru\u017ea <strong>nativan, provider-agnostic<\/strong> na\u010din da pluginovi i teme razgovaraju s AI servisima. \u201cProvider-agnostic\u201d ovdje zna\u010di: plugin ne mora biti vezan uz jednog dobavlja\u010da\/model, niti hardkodirati integraciju za odre\u0111eni vendor.<\/p>\n\n\n\n<p>Projekt prilago\u0111ava postoje\u0107i <strong>PHP AI Client<\/strong> WordPress konvencijama. Bitne tehni\u010dke to\u010dke koje su istaknute:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Koristi <strong>WordPress HTTP API<\/strong> za mre\u017enu komunikaciju (umjesto da svaki plugin nosi vlastite HTTP implementacije).<\/li>\n\n\n<li>Centralizira API klju\u010deve u zasebnom ekranu: <strong>\u201cAI Credentials\u201d<\/strong> (umjesto da svaki plugin radi vlastite postavke i pohranu tajni).<\/li>\n\n\n<li>Rje\u0161ava odabir modela bez potrebe da pluginovi hardkodiraju specifi\u010dne providere.<\/li>\n\n<\/ul>\n\n\n\n<p>U bilje\u0161kama je navedeno i \u0161to se o\u010dekuje u budu\u0107im izdanjima AI Clienta:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Dodavanje podr\u0161ke za <strong>Abilities API<\/strong>.<\/li>\n\n\n<li>Dodavanje <strong>REST endpointa<\/strong>.<\/li>\n\n\n<li>Dodavanje client-side <strong>Prompt Buildera<\/strong> (alat za izgradnju promptova na klijentskoj strani).<\/li>\n\n<\/ul>\n\n\n\n<p>Argument za core je prili\u010dno jasan: ako WordPress \u017eeli da ekosustav gradi AI funkcionalnosti na konzistentnim temeljima (npr. Abilities API), onda je smisleno da klju\u010dni dio infrastrukture \u017eivi u jezgru, a ne da se fragmentira kroz deset razli\u010ditih pluginova sa svojim rje\u0161enjima.<\/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>Meeting notes (Make WordPress Core)<\/cite><\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Ograni\u010denja: WordPress \u017eeli ostati agnosti\u010dan (bez \u201czaklju\u010davanja\u201d na jedan model ili vendor)<\/h3>\n\n\n\n<p>Jedan od klju\u010dnih uvjeta koji se provla\u010di kroz raspravu: WordPress \u201cwill always remain agnostic\u201d. Drugim rije\u010dima, uklju\u010divanje to\u010dno odre\u0111enog AI modela, ili integracija samo s dijelom third-party servisa, dugoro\u010dno se ne smatra odr\u017eivim.<\/p>\n\n\n\n<p>Spomenute su i dugoro\u010dnije mogu\u0107nosti koje bi mogle do\u0107i s razvojem modela na razini ure\u0111aja ili browsera (machine-based ili browser-level modeli), ali bez odabira konkretnog smjera u ovom trenutku.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Prije odluke: tra\u017ee se jasni use-caseovi u \u201cdefault WordPressu\u201d<\/h3>\n\n\n\n<p>Prije nego \u0161to se povu\u010de potez prema coreu, kontribuktori \u017eele jasne, \u201cdefault WordPress\u201d primjere uporabe &#8211; ne\u0161to \u0161to ima smisla za WordPress out-of-the-box, a ne samo za specijalizirane pluginove.<\/p>\n\n\n\n<p>Kao primjeri su navedeni:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Pretra\u017eivanje Media Libraryja po specifi\u010dnom sadr\u017eaju\/tematici (npr. prona\u0107i slike s odre\u0111enim subjektom).<\/li>\n\n\n<li>Generiranje newslettera na temelju nedavnog sadr\u017eaja.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Admin redizajn: \u201csvje\u017ei sloj boje\u201d, ne kompletna rekonstrukcija<\/h2>\n\n\n\n<p>Admin redizajn je i dalje na radaru, ali je nagla\u0161eno da cilj nije \u201cfull overhaul\u201d. Prema bilje\u0161kama, radi se o pristupu koji je vi\u0161e <strong>\u201cnew coat of paint\u201d<\/strong>: osvje\u017eiti postoje\u0107e, a ne izgraditi potpuno novi admin iz nule.<\/p>\n\n\n\n<p>Ovo poja\u0161njenje dolazi nakon ranijih rasprava (srpanjski kvartalni sastanak) gdje se govorilo o testiranju redizajna kao eksperimenta kroz Gutenberg plugin, ili kroz zaseban \u201cMP7\u201d plugin &#8211; referenca na MP6 iz 2013. koji je kao \u201cfeature as a plugin\u201d postavio smjer za admin redizajn u WordPressu 3.8.<\/p>\n\n\n\n<p>Admin redizajn se uklapa u <strong>Phase 3: Collaboration<\/strong> na Gutenberg roadmapu. Rad na toj liniji je krenuo 2023., kada je Gutenberg Lead Architect Mat\u00edas Ventura podijelio viziju modernizacije admin iskustva, a kasnije je demonstrirao nove layoute tijekom State of the Word 2023.<\/p>\n\n\n\n<p>Va\u017ean detalj za o\u010dekivanja: rani preview admin redizajna koji je bio planiran uz WordPress 6.9 je u rujnu maknut s roadmapa uz napomenu da je \u201cno longer planned based on the current state of work\u201d.<\/p>\n\n\n\n<p>Trenutno <strong>nema vremenskog okvira<\/strong> kada bi redizajnirani admin mogao stvarno u\u0107i u WordPress. Posljednje veliko osvje\u017eenje admina je staro vi\u0161e od desetlje\u0107a (WordPress 3.8).<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Minimalni PHP: rasprava o podizanju na PHP 7.4 (bez odluke)<\/h2>\n\n\n\n<p>Jo\u0161 jedna tema s velikim prakti\u010dnim utjecajem: razmatrani su \u201ccompelling reasons\u201d za podizanje minimalno podr\u017eane PHP verzije na <strong>PHP 7.4<\/strong>.<\/p>\n\n\n\n<p>Rasprava se vrtjela oko vrlo konkretnih ograni\u010denja:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Podr\u0161ka za stare PHP verzije prisiljava WordPress da zadr\u017ei kompatibilnost koja dodaje \u201cbloat\u201d i usporava razvoj.<\/li>\n\n\n<li>PHP 7.4 bi gurnuo codebase prema konzistentnijem tipiziranju (consistent typing), \u0161to olak\u0161ava razumijevanje i developerima i AI sustavima.<\/li>\n\n\n<li>Mnogi third-party AI SDK-ovi ve\u0107 zahtijevaju novije PHP verzije; prenizak minimum blokira njihovu upotrebu u WordPress kontekstu.<\/li>\n\n<\/ul>\n\n\n\n<p>Kako je u bilje\u0161kama nazna\u010deno, okvir rasprave je balans izme\u0111u napretka i odr\u017eavanja \u0161iroke baze korisnika &#8211; uz jasnu namjeru da se nikoga ne \u201cotka\u010di\u201d preko no\u0107i. Na samom sastanku nije donesena odluka.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">\u0160to slijedi: otvoreniji formati, raspored izdanja i fokus za 7.0 (mo\u017eda i 7.1)<\/h2>\n\n\n\n<p>Jonathan Desrosiers je u bilje\u0161kama naveo i konkretne follow-up stavke koje bi trebale do\u0107i nakon ovog check-ina:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Predlo\u017eiti otvorenije i \u201csemi-open\u201d formate sastanaka.<\/li>\n\n\n<li>Objaviti raspored (release schedule) za 2026.<\/li>\n\n\n<li>Potvrditi ciljane funkcionalnosti za 7.0 i mogu\u0107e 7.1.<\/li>\n\n\n<li>Procijeniti je li uskla\u0111ivanje izdanja s doga\u0111ajima u\u017eivo prakti\u010dno (putovanja, vremenske zone, dostupnost ljudi).<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Sa\u017eetak za developere: \u0161to pratiti u idu\u0107im mjesecima<\/h2>\n\n\n\n<p>Ako odr\u017eava\u0161 teme\/pluginove ili radi\u0161 na enterprise WordPressu, nekoliko je jasnih signala iz ovog sastanka: WordPress se \u017eeli vratiti br\u017eem ritmu (tri major izdanja), WordPress 7.0 se ve\u0107 cilja za rano prolje\u0107e, AI se poku\u0161ava postaviti na zajedni\u010dke temelje kroz AI Client, admin redizajn ide evolucijski, a minimalni PHP \u0107e se vjerojatno ponovno sna\u017eno otvoriti kao tema &#8211; s PHP 7.4 kao konkretnim pragom o kojem se pri\u010da (zasad bez kona\u010dne odluke).<\/p>\n\n\n<div class=\"references-section\">\n                <h2>Reference \/ Izvori<\/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.chathamhouse.org\/about-us\/chatham-house-rule\" target=\"_blank\" rel=\"noopener noreferrer\">Chatham House Rule<\/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\">only one major release would ship in 2026<\/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\/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\">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>Nakon najave da bi 2026. mogla imati samo jedno veliko izdanje, WordPress sada ponovno cilja na tri. U fokusu su rani planovi za 7.0, admin redizajn kao evolucija (ne revolucija) i ozbiljna rasprava o WordPress AI Clientu u coreu.<\/p>\n","protected":false},"author":42,"featured_media":199,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[31],"tags":[26,19,24,25,10],"class_list":["post-201","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wordpress-ekosustav","tag-ai","tag-core","tag-gutenberg","tag-php","tag-wordpress"],"_links":{"self":[{"href":"https:\/\/helloblog.io\/hr\/wp-json\/wp\/v2\/posts\/201","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/helloblog.io\/hr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/helloblog.io\/hr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/helloblog.io\/hr\/wp-json\/wp\/v2\/users\/42"}],"replies":[{"embeddable":true,"href":"https:\/\/helloblog.io\/hr\/wp-json\/wp\/v2\/comments?post=201"}],"version-history":[{"count":0,"href":"https:\/\/helloblog.io\/hr\/wp-json\/wp\/v2\/posts\/201\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/helloblog.io\/hr\/wp-json\/wp\/v2\/media\/199"}],"wp:attachment":[{"href":"https:\/\/helloblog.io\/hr\/wp-json\/wp\/v2\/media?parent=201"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/helloblog.io\/hr\/wp-json\/wp\/v2\/categories?post=201"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/helloblog.io\/hr\/wp-json\/wp\/v2\/tags?post=201"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}