WordPress 7.0 - Everything New! - CourtneyR.dev's 2nd Brain

WordPress 7.0 - Everything New! ![rw-book-cover](https://img.youtube.com/vi/-X6lEpJ6RKU/maxresdefault.jpg) 🔗 **Source:** [WordPress 7.0 - Everything New!](https://www.youtube.com/watch?v=-X6lEpJ6RKU) > [!note]+ Document Notes > tags: #wordpress #wordpress7 #block-editor #ai-integration #collaboration #revisions #navigation #fonts > author: Ivra - WinnersTube > source: YouTube > reference: https://www.youtube.com/watch?v=-X6lEpJ6RKU > date created: 2024-12-19 10:30 > > # 🏷️ Title: WordPress 7.0 - Everything New! >  ## 🧰 Action Inbox - [H1] Test WordPress 7.0 beta features before April 9, 2026 release — comprehensive overview/demo #wordpress7 #beta-testing - [H2] Prepare for AI API integration in existing plugins — infrastructure planning/development #ai-integration #plugin-development - [H3] Update PHP versions to 8+ before WordPress 7.0 release — compatibility/security requirements #php-upgrade #compatibility ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - [WordPress 7.0 Beta](https://wordpress.org) - [WordPress Developer Documentation](https://developer.wordpress.org) ## 📝 Summary - WordPress 7.0 scheduled for April 9, 2026 release with major UI/UX improvements - New AI API infrastructure allows unified AI key management across plugins - Enhanced collaborative editing features similar to Google Docs - Improved revisions system with visual previews - Client-side media processing reduces server load - Drops support for PHP 7.2 and 7.3, requires PHP 8+ ## 📖 Main Content WordPress 7.0 represents a significant evolution in the platform's capabilities, focusing on improved user experience, AI integration infrastructure, and collaborative workflows. The release introduces substantial visual improvements with enhanced contrast and smoother page transitions, making the admin interface more accessible and professional. The most significant architectural change is the Web Client AI API, which provides standardized infrastructure for plugins to integrate AI features using shared API keys rather than separate billing systems. This addresses the current fragmentation where each plugin requires its own AI service subscriptions. Enhanced collaboration features bring Google Docs-style real-time editing to WordPress, allowing multiple users to simultaneously work on content with comments and live previews. The revisions system receives a complete overhaul with visual diff comparisons showing actual content changes rather than code-level modifications. Technical improvements include client-side media processing (reducing server load), new breadcrumbs and icons blocks, enhanced navigation menu customization, improved CSS handling, and better font management across all theme types. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/-X6lEpJ6RKU?t=0) — [H1] WordPress 7.0 Release Overview - Key idea: WordPress 7.0 scheduled for April 9, 2026 with major improvements - Evidence: "WordPress 7.0 is scheduled to release on April of 9, 2026" #### ⏱️ [01:30](https://youtu.be/-X6lEpJ6RKU?t=90) — [H2] Visual Design Improvements - Key idea: Enhanced contrast and darker colors improve readability - Evidence: "the 7.0 version colors are more contrasty, little darker, and easier to read" #### ⏱️ [02:45](https://youtu.be/-X6lEpJ6RKU?t=165) — [H3] Command Palette Integration - Key idea: Notification area replaced with keyboard shortcut display - Evidence: "notification now on screen does show the keyboard shortcut right there" #### ⏱️ [03:15](https://youtu.be/-X6lEpJ6RKU?t=195) — [H2] Smoother Page Transitions - Key idea: Fade transitions replace jarring page reloads in admin - Evidence: "It's like a fade transition that you apply in video editing" #### ⏱️ [05:30](https://youtu.be/-X6lEpJ6RKU?t=330) — [H1] Web Client AI API Infrastructure - Key idea: Unified AI key management eliminates plugin-specific billing - Evidence: "you can add your own AI keys to WordPress and then plugins that build AI functionalities on top can use the same infrastructure" #### ⏱️ [08:45](https://youtu.be/-X6lEpJ6RKU?t=525) — [H1] Collaborative Writing Features - Key idea: Real-time collaboration like Google Docs coming to WordPress - Evidence: "multiple people will be able to collaborate on a single blog post or page" #### ⏱️ [10:15](https://youtu.be/-X6lEpJ6RKU?t=615) — [H2] Enhanced Revisions System - Key idea: Visual diff previews replace code-based comparisons - Evidence: "you can actually see the image which was added. Makes the job a lot easier" #### ⏱️ [12:30](https://youtu.be/-X6lEpJ6RKU?t=750) — [H3] Cover Block Video Embedding - Key idea: Remote video URL embedding added to cover blocks - Evidence: "embed video URL. So, if you have public library of videos available, then you can use that" #### ⏱️ [14:00](https://youtu.be/-X6lEpJ6RKU?t=840) — [H2] Navigation Menu Customization - Key idea: Custom overlay templates for mobile navigation menus - Evidence: "you also have one more extra option which is the overlay template" #### ⏱️ [16:45](https://youtu.be/-X6lEpJ6RKU?t=1005) — [H3] New Breadcrumbs and Icons Blocks - Key idea: Native breadcrumbs and SVG icons blocks added - Evidence: "you don't have to have any SVG icon library imported or downloaded" #### ⏱️ [18:30](https://youtu.be/-X6lEpJ6RKU?t=1110) — [H3] Per-Block CSS Customization - Key idea: Inline CSS editing for individual blocks - Evidence: "you also get additional CSS. So if you just want to add tweak shadow a little bit" #### ⏱️ [20:15](https://youtu.be/-X6lEpJ6RKU?t=1215) — [H3] Improved Heading Block Workflow - Key idea: Direct heading level selection streamlines content creation - Evidence: "instantly I can see I can select H4 if I want to" #### ⏱️ [21:30](https://youtu.be/-X6lEpJ6RKU?t=1290) — [H2] Universal Font Management - Key idea: Font management extends to non-block themes - Evidence: "you can now manage your fonts entirely even if you're using non-block based themes" #### ⏱️ [23:45](https://youtu.be/-X6lEpJ6RKU?t=1425) — [H1] Client-Side Media Processing - Key idea: Browser-based image processing reduces server load and costs - Evidence: "use your own web browser capability which are free to use to actually do the processing" #### ⏱️ [26:30](https://youtu.be/-X6lEpJ6RKU?t=1590) — [H3] PHP Version Requirements - Key idea: PHP 7.2 and 7.3 support dropped, requires PHP 8+ - Evidence: "officially has dropped support for insecure versions of PHP. That means 7.2 and 7.3" ## 📚 References - [WordPress Official Site](https://wordpress.org) - [WordPress Developer Hub](https://developer.wordpress.org) - [PHP Version Support](https://www.php.net/supported-versions.php) ## 🗣️ Paraphrase - WordPress 7.0 brings a comprehensive visual refresh with improved contrast and smoother navigation transitions that make the admin interface more professional and accessible - The new AI API infrastructure centralizes artificial intelligence integration, allowing plugins to share user-provided API keys instead of requiring separate subscriptions for each service - Enhanced collaboration tools enable real-time multi-user editing with visual revision tracking, bringing Google Docs-style workflows to WordPress content creation ## 📰 Newsletter WordPress 7.0 is shaping up to be a game-changing release! Scheduled for April 2026, this major update brings exciting improvements that will transform how we build and collaborate on WordPress sites. The standout feature is the new AI API infrastructure that lets you use your own ChatGPT or Claude API keys across all your AI-powered plugins. No more juggling multiple subscriptions! Plus, real-time collaborative editing is coming, making team content creation as smooth as Google Docs. Visual improvements include better contrast, smoother transitions, and enhanced revision tracking with actual content previews. New blocks for breadcrumbs and icons, plus universal font management for all theme types, round out the user experience upgrades. Start preparing now by updating to PHP 8+ and exploring the beta to plan your transition strategy. Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### WordPress - Core: Test WordPress 7.0 beta features and compatibility with existing plugins - Core AI: Develop guidelines for AI API key management and plugin integration standards - Community: Create migration guides and documentation for PHP version requirements - Training: Develop curricula for new collaborative editing and AI features - Design: Document accessibility improvements in new visual design system - Documentation: Update DevHub with new block types and API changes - Hosting: Prepare infrastructure guides for client-side media processing requirements #### DevRel - Developer advocacy: Create demos showcasing AI API integration possibilities - Education: Host workshops on collaborative editing workflows and new block development - Developer experience: Update documentation for new CSS customization options - Developer marketing: Highlight performance benefits of client-side media processing - Community management: Gather feedback on beta features and prioritize improvements ## 🧪 Hypotheses - Client-side media processing will significantly reduce hosting costs for image-heavy WordPress sites - Unified AI API management will accelerate adoption of AI features across the WordPress ecosystem - Real-time collaborative editing will increase WordPress adoption among content teams and agencies - Visual design improvements will reduce cognitive load and increase admin productivity ### 📊 Methodology - Performance benchmarks comparing server-side vs client-side image processing resource usage - User testing studies measuring task completion time with new vs old revision interfaces - Plugin adoption analysis before and after AI API infrastructure implementation - Accessibility compliance testing for new visual design elements ### ❓ Questions - How will client-side media processing handle browser compatibility and fallback scenarios? - What security measures protect AI API keys stored in WordPress installations? - Will collaborative editing support real-time conflict resolution for simultaneous edits? ### 🔮 Future Research - Impact of AI API standardization on WordPress plugin ecosystem development - Performance implications of always-iframed post editor architecture - User adoption patterns for new collaborative editing workflows ### 💡 Implications - Practice: Teams need training on collaborative editing workflows and AI integration - Policy: Organizations must establish AI API key management and usage policies - Security: Client-side processing requires new security considerations for media handling - Education: Developer training needed for new PHP primitives and block registration methods - Funding: Hosting cost reductions from client-side processing may impact budget planning ### 🧠 Learning Styles Assessment Reading level estimate: Flesch-Kincaid Grade Level 9 #### 👀 Visual learners - Present: Side-by-side comparisons, UI screenshots, visual diff demonstrations - Improve: Architecture diagrams for AI API infrastructure, workflow charts #### 🔊 Aural learners - Present: Video demonstration with narration explaining each feature - Improve: Audio-only summary of key changes for accessibility #### 🗣️ Verbal learners - Present: Clear explanations of technical concepts, analogies to familiar tools - Improve: Glossary of new terms, comparison tables with existing features #### 🧩 Kinesthetic learners - Present: Hands-on demo with beta installation and testing - Improve: Step-by-step setup guides, interactive feature exploration #### 🧠 Logical learners - Present: Structured feature breakdown, technical specifications - Improve: Decision trees for migration planning, feature dependency maps #### 🧑‍🤝‍🧑 Social learners - Present: Community discussion of new features and use cases - Improve: Collaborative planning sessions, peer review of implementation strategies #### 🧘‍♀️ Solitary learners - Present: Comprehensive documentation for independent exploration - Improve: Self-paced learning modules, personal testing environments #### 🌿 Naturalistic learners - Present: Evolution of WordPress ecosystem and feature development - Improve: Environmental impact analysis of client-side vs server-side processing ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear headings and timestamp navigation structure - Improve: Alternative text for UI comparison screenshots #### Keyboard navigation - Present: Video player keyboard controls available - Improve: Transcript with keyboard shortcut documentation #### Contrast and readability - Present: High contrast in WordPress 7.0 interface improvements - Improve: Color-blind friendly descriptions of visual changes #### Text resizing and reflow - Present: Responsive video player and text content - Improve: Scalable interface mockups and diagrams #### Media and captions - Present: Video demonstration with audio narration - Improve: Auto-generated captions and downloadable transcript #### Forms and interactions - Present: Clear demonstration of new block interfaces - Improve: Accessible form examples for new features ### 🌍 DEIB Assessment #### Cultural breadth - Present: English-language demonstration with global WordPress focus - Improve: Multi-language examples, international hosting considerations #### Inclusive language - Present: Technical explanations without jargon assumptions - Improve: Plain-language alternatives for complex concepts #### Neurodiversity support - Present: Structured presentation with clear section breaks - Improve: Content warnings for rapidly changing UI demonstrations #### Representation - Present: Focus on technical features rather than user demographics - Improve: Diverse use case examples, varied team collaboration scenarios #### Psychological safety - Present: Encouraging tone about upcoming improvements - Improve: Clear migration timelines to reduce anxiety about changes ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Feature descriptions based on beta testing and official announcements - Inductive strength: Performance predictions based on similar client-side processing implementations - Causal reasoning: Clear connections between infrastructure changes and developer benefits - Analogical strength: Effective comparison to Google Docs for collaborative editing #### Fallacies - None identified: Presenter clearly distinguishes between shipped features and planned functionality #### Tone of voice - Overall tone: Enthusiastic and informative, with clear technical explanations and practical focus on user benefits ### 🛡️ DARVO Analysis - Deny: No defensive patterns identified - Attack: No attacks on critics or alternative approaches - Reverse victim/offender: No victim/offender dynamics present - Emotional cues and rhetoric: Positive enthusiasm for improvements without dismissing current functionality ## 🎯 Conclusion WordPress 7.0 represents a significant evolution focusing on user experience, collaboration, and AI integration infrastructure. The April 2026 release will require PHP 8+ and introduces game-changing features like unified AI API management, real-time collaborative editing, and client-side media processing. Organizations should begin planning their migration strategy, testing beta features, and preparing teams for enhanced collaborative workflows. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] WordPress 7.0 introduces unified AI API infrastructure > [!quote] [WordPress 7.0 - Everything New!](https://www.youtube.com/watch?v=-X6lEpJ6RKU) by [[Ivra - WinnersTube]] via [[YouTube]]. Published 2024. Accessed 2024-12-19. > "you can add your own AI keys to WordPress and then --- ## Full Transcript [00:00] One of the biggest changes coming to [00:01] WordPress, WordPress 7.0 is scheduled to [00:03] release on April of 9, 2026. So, just a [00:05] few weeks from the date of this [00:06] recording. So, in this video, I'm going [00:08] to show you sideby-side differences of [00:09] WordPress 7.0 and the recent release of [00:12] WordPress, which is 6.9.4. And I'll go [00:14] through all the differences so you can [00:16] see and follow along and discount what's [00:18] new in WordPress 7.0. Let's begin. So, I [00:21] have two websites set up so that I can [00:23] show you differences side by side. This [00:25] is the first website. This is WordPress [00:27] 6.9.4 4 right now, which is the recent [00:29] public release of WordPress. And this is [00:32] the 7.0 release. You can even see it [00:34] here. You're using a development version [00:36] 7.0. I'm using the beta 5. And the first [00:39] important difference you see is the [00:41] visual difference. I'll switch back. So [00:44] you can see the original WordPress [00:45] colors, they look good, but the 7.0 [00:47] version colors are more contrasty, [00:49] little darker, and easier to read in my [00:52] opinion. So if you see here, you can see [00:54] the text styles and how the contrast is. [00:56] And if I switch instantly, you'll see [00:58] the text is more nuanced. The contrast [01:00] is higher. And even the highlight color [01:02] of the blue, the traditional blue is [01:04] darker. I think this is a welcome [01:06] change. It makes very easy to focus on. [01:08] And the typography is quite clearer. If [01:11] I go back, you can see the difference is [01:13] quite big. So that's the first change. [01:16] One small tweak I also saw between [01:18] WordPress versions was if you go back [01:20] here if you saw this which was uh number [01:22] of notifications you had comments [01:24] updates everything else that has been [01:26] replaced with control K or command K if [01:29] you're on a Mac to showcase that you can [01:31] actually use the command pallet so if I [01:32] press control K it opens in the command [01:34] pallet but if you go back and use the [01:36] command pallet here it'll work the same [01:38] way but the notification now on screen [01:41] does uh show the keyboard shortcut right [01:43] there so that's the big change visually [01:46] There's also one more big visual change [01:47] when you're navigating between screens. [01:49] So, let me show you that as well. Going [01:51] back to 6.9. Let me go back to the [01:53] dashboard. So, now in the dashboard, [01:55] I'll go to a couple of pages right now [01:58] in WordPress 6.9.4. The pages menu, the [02:01] plugins menu. And you probably seen this [02:03] all the time, right? How the transition [02:05] happens. So, if I go to the pages [02:07] section, you'll see that the page [02:08] refreshes. Then we see the pages section [02:10] or the plug-in section. And if I go this [02:13] and do this to the plug-in section, [02:14] you'll see that in WordPress 7.0, the [02:17] transition is improved. It just feels [02:18] like the entire page isn't reloading and [02:21] this feels smoother. So, let me do it on [02:23] now WordPress 7.0 so you can pay [02:25] attention. I'll go to the dashboard. [02:32] You saw the transition was a little more [02:33] smoother, right? It's like a fade [02:35] transition that you apply in video [02:36] editing. Sometimes I do it on my videos [02:38] as well. I'll demonstrate by going into [02:40] the plug-in section and then going into [02:41] the pages section as well. See how [02:43] smooth the transition is. If I go to the [02:45] post section, you'll see the transition [02:47] feels a lot more smoother. [snorts] So, [02:49] I think it's a welcome change. It makes [02:51] uh overall appearance of WordPress a lot [02:53] more smoother. It feels it's more [02:54] responsive and it just gives it's it's [02:57] less jarring than WordPress 6.9.4. And I [02:59] say uh with the original WordPress [03:01] version, I didn't feel it jarring, but [03:03] now since I use this, that feels a [03:05] little jarring that hey, how will we be [03:07] living with this? So that's a welcome [03:08] change in WordPress 7.2 as well. The [03:11] next big change in WordPress is a web [03:13] client AI API. So let me demonstrate or [03:16] talk about it because it's not something [03:18] I can demonstrate right now because it's [03:19] still in the planning phase. And the you [03:21] can think about it like this. The [03:22] infrastructure for whatever I'm going to [03:25] talk about is right now that's what's [03:27] been placed in WordPress 7.0. When will [03:29] it be publicly available and the impact [03:31] of it? You'll see it later. I'll explain [03:33] it this way that you have the app store [03:35] and the play store on your phone, right? [03:37] So the app store and play store don't [03:39] make a huge impact on your life but the [03:41] apps inside the play store and app app [03:43] store make a huge difference. So it's [03:45] similar to this. So the uh web client AI [03:48] API is the infrastructure that will [03:50] allow plugins and other services to use [03:53] AI features. We all know that AI is [03:55] making a huge impact on everyone's life. [03:57] You can design websites, create content, [03:59] do a lot of things in with AI. And the [04:01] future or of how at least at least I'm [04:04] understanding it is that you will have [04:05] AI ingrained with every process. Now the [04:08] challenge is for example many plugins do [04:09] offer AI services. For example if you [04:11] use all of an SEO it has its own AI [04:14] features for content summarization FAQ [04:16] generation images uh and lot of other [04:19] things that it can do but it uses its [04:21] own AI keys. So you have to purchase [04:23] credits separately and that's the how [04:26] it's built. Now this system uh can [04:28] become chaotic if a lot of plugins want [04:29] to add AI features. So everything is [04:31] it's uh I say uh congested in the same [04:34] place. So what WordPress has done is [04:36] they're building the infrastructure so [04:38] that you can add your own AI keys to [04:40] WordPress and then plugins that build AI [04:43] functionalities on top can use the same [04:45] infrastructure, same AI keys. So if you [04:47] let's say use chat GP or claude, you can [04:49] add your own AI keys and then whenever a [04:51] plug-in has an AI functionality, it'll [04:53] use your own AI keys instead of having [04:55] to have different billings and also [04:56] problems. So that's the infrastructure. [04:58] So a couple of important things to [04:59] understand that yeah, this is just an [05:01] infrastructure thing right now and it's [05:03] in the planning phase. So this has been [05:05] introduced. It's not something that will [05:06] be available immediately. But I'm [05:08] assuming when it will be public, more [05:10] plug-in developers will start [05:11] integrating AI into their workflows. And [05:13] I'm assuming that in the future [05:15] WordPress might introduce native [05:16] features about uh content writing uh [05:19] headline optimization all that things. [05:22] But the plug-in infrastructure is what [05:23] will make the huge difference and it's a [05:25] standard way I think as a more clear way [05:27] to interact with AI. Yeah. By using your [05:30] own API keys. So again a welcome change [05:32] the web client AI API in WordPress. [05:34] Another you change coming to WordPress [05:36] 7.0. The next big feature in WordPress [05:39] 7.0 O is a very welcome change [05:41] especially if you are writing content in [05:44] WordPress and if you have multiple [05:45] people writing you'll find this change [05:47] welcome. You might remember the notes [05:49] feature that was shipped a couple of [05:50] versions ago. So on a WordPress website [05:52] you could just leave a note so that [05:54] other people can actually see the note [05:56] make changes similar to how you can [05:58] leave comments in Google Docs. Now the [06:00] important thing is that uh the next big [06:02] change coming to WordPress 7.0 is a [06:05] complete collaborative writing [06:07] experience. Now, it's not shipped in the [06:08] beta version, but it's planned. So, the [06:11] idea being that similar to how on Google [06:13] Docs, if you share a document with [06:15] multiple people, multiple people can [06:16] leave comments, but multiple can also [06:18] write content at the same time in the [06:20] same doc. You can see a preview of [06:22] what's what people are doing. So, the [06:24] same functionality is supposed to be [06:26] coming to WordPress very soon where [06:28] multiple people will be able to [06:29] collaborate on a single blog post or [06:31] page or whatever you're creating. The [06:33] benefit is obvious that you can leave [06:36] comments, you can collaborate and have [06:38] content written at it together. So [06:40] that's a very big change coming to [06:42] WordPress 7.0. And if you have a team of [06:44] writers, if multiple write content, you [06:45] write content, collaborate with writers, [06:47] this is going to be a change. It's not [06:49] shipped in the beta, so I can't demo it [06:50] right now, but again, a huge change [06:52] coming to WordPress 7.0 or maybe 7.x. [06:56] The next big change in WordPress 7.0 is [06:59] how the revisions work. If you are a [07:01] writer and you write content, you know [07:03] how revisions can be important. But till [07:06] WordPress 7.0, uh the revisions feature [07:09] was not great. Let me demonstrate. So [07:11] this is a revision of a blog post that I [07:13] have on WordPress 6.9.4. [07:16] You can see that it gives you a code [07:17] view. So actually making decisions about [07:20] what was done, what wasn't done is not [07:23] the easiest, right? So if you notice, [07:26] you might see, oh, this was added, but [07:28] it's an image, but you don't see the [07:29] image. So it's not easy to make those [07:31] decisions. So what was added, what was [07:33] removed, not a great experience. But [07:34] WordPress 7.0 has a much better [07:36] experience. If I go to 7.0, this is how [07:39] the revisions look like. I do have the [07:41] slider on top. And this is the first [07:43] version. So you see everything is in [07:44] green. Gives you easy visual preview to [07:46] see things that were added. If I scroll [07:49] to the next revision, you can see that [07:51] this section was added, which is [07:53] actually an image. So you can actually [07:54] see the image which was added. Makes the [07:56] job a lot easier. And then if I go here [07:59] to the last version, I can see two red [08:01] segments. If I click here, it shows that [08:03] there was headings here that I actually [08:06] removed. So it's much easier to [08:07] understand what's going on when it comes [08:09] to revisions. Again, another welcome [08:11] change to WordPress 7.0. The next big [08:14] change in WordPress 7.0 is how the cover [08:17] block works. Let me demonstrate. So this [08:19] is WordPress 6.9.4. I added a cover [08:22] block and it looks how it looks like, [08:24] right? With our blog, you can add [08:25] images, videos, and if I click here, you [08:28] know, if you go to add media, you can [08:29] just click it, open media library, [08:31] upload, use featured image, or I could [08:33] just use the buttons here. But WordPress [08:35] 7.0 has a new trick up its sleeve. If I [08:38] go to WordPress 7.0, this is the cover [08:40] block. If I click on it, if I click add [08:41] media, you see a fourth option, which is [08:44] embed video URL. So, if you have public [08:47] library of videos available, then you [08:49] can use that and add that directly to [08:51] the cover block. The rest of the [08:52] functionality works the same way. You [08:54] can use overlays, add text, everything [08:56] else. But WordPress can now handle [08:58] remote videos in the cover block and it [09:00] handles the looping and everything [09:01] automatically. Again, a useful feature. [09:03] And I'm not sure if uh the video is [09:05] actually downloaded to your site and [09:06] then used or it directly plays via the [09:09] remote server because that uh will make [09:11] a huge difference on how resources are [09:13] utilized. So if I get more information, [09:15] I'll leave that in the comments. But [09:16] again, useful change in WordPress 7.0. [09:19] The next big change is with navigation [09:22] menus in WordPress 7.0. There are few [09:24] different changes and the implications [09:26] even better. So let me show you [09:28] directly. So this is WordPress 6.9.4 and [09:31] if you add a navigation block whether [09:32] you're using the block editor or just [09:35] adding navigation menus to a page or [09:36] post doesn't matter the differences will [09:38] be the same. So I just added the [09:40] navigation menu and if you add the go to [09:42] the navigation block settings you see [09:44] the settings. You can see the navigation [09:45] menu here which is the list view and in [09:47] the settings you have justifications [09:49] orientation. You can change the [09:50] hamburger icon and if you go to the [09:52] preview section of that you can actually [09:54] see that navigation actually I works if [09:56] the I say the screen width is reduced. [09:59] So it actually works but you had limited [10:02] customization on how the actual menu [10:05] look like. Let me give you a preview [10:07] here. If I go here and click you can see [10:09] this overlay comes on screen as the [10:11] mobile menu which is great but there's [10:12] no customization. WordPress 7.0 0 [10:14] changes that if I go to WordPress 7.0 uh [10:18] let me fix this menu first and I'll then [10:20] resume the video. So I change the menu [10:22] to the main menu here and you can see [10:24] the menu. If I click on the block you [10:26] can see the menu and inside the settings [10:28] you have the similar settings right you [10:29] have the visibility you have the icon [10:31] selection but you also have one more [10:33] extra option which is the overlay [10:36] template. So you can see the overlay [10:37] template is default you also have [10:39] options and you can create a new overlay [10:41] template. So if I click this button, you [10:43] see we'll go back or we'll go to the uh [10:46] see creation menu where you'll to create [10:49] and change things around. So this is a [10:51] different kind of menu. But the point [10:53] here is that if you go here in the [10:55] design section and you click this menu, [10:57] now you have a completely new overlay [11:00] created for your mobile menu. Of course [11:02] you have the design tool. So you can [11:03] change the size, you can change the [11:04] actual menu inside the menu, but you [11:07] have these design controls that you can [11:08] actually use and without having to do [11:10] lot of CSS trickery. Now you'll have a [11:13] completely new overlay that you can use [11:15] for your mobile menus. And great change [11:17] again in WordPress 7.0. [11:20] WordPress 7.0 also introduces two new [11:22] blocks. The breadcrumbs block and the [11:25] icons block. Let me demonstrate. This is [11:27] WordPress 6.9.4. If I tap forward slash [11:30] and type bread, I see bread comes coming [11:33] from all in SEO, not native WordPress. [11:35] And if I go and type in icons, I see [11:39] social icons coming from different [11:40] plugins, but not the actual icons. In [11:42] WordPress 7.0, that changes. If I come [11:45] here and type breadcrumbs, [11:48] now you can see all NEO breadcrumbs, [11:50] which you can use, of course, is a great [11:51] product, but the regular breadcrumbs [11:54] also can show up and they'll uh inherit [11:56] the styles of your theme. So they're [11:57] much easier to use. You can also [11:59] customize the separator. You can change [12:01] some settings and you can move things [12:03] around and you can also style them. [12:05] Padding, size, all the regular things [12:07] that you have access to blocks [12:08] customization in WordPress. Now the [12:11] icons block is also useful. Let me also [12:12] demonstrate that. So I'll click here and [12:15] I type in icons and I can add icons. Now [12:19] if you've used any kind of SVG icons, [12:21] you know how icons work. But the idea is [12:23] that you don't have to have any SVG icon [12:26] library imported or downloaded or [12:28] imported as a plug-in. Now you have some [12:30] native uh I'd say SVG icons in WordPress [12:33] and you can have customizations directly [12:35] here. So I'll choose an icon and this [12:37] will open up the actual library. So it's [12:39] it's just starting out. So it's not as [12:41] extensive as any icon library but it [12:43] exists directly in WordPress. So if I [12:45] click the mobile icon here, I can go [12:47] here. I can make the size bigger if I [12:50] want to and I can even add a let's say [12:53] try and add a color here. So I'll try to [12:55] add a overlay color and now we have a [12:58] beautiful icon here SVG icon so it can [13:00] scale well. So kind of works directly in [13:03] WordPress 7.0. Pretty easy stuff. [13:06] Another big change in WordPress 7.0 is [13:08] with regards to CSS and how you can add [13:10] CSS. Now you already know that you can [13:12] add CSS classes on any block that you [13:15] like. If I show you WordPress 6.9.4 4. [13:18] Uh this is how it works. You select a [13:20] block, you go to the block settings and [13:22] on the bottom you have HTML anchor and [13:24] additional CSS classes. So you can add [13:26] any classes that you have created and [13:28] those classes will be applied to the [13:30] block. So this is how it works in 6.9.4. [13:33] But now you have a big change for any [13:35] small change you want to make. You don't [13:37] have to write a class for that. In [13:39] WordPress 7.0, not only do you get [13:41] additional CSS classes, but you also get [13:43] additional CSS. So if you just want to [13:45] add tweak shadow a little bit or any [13:47] other property without having to uh add [13:50] a new class of CSS, you can just write [13:52] that CSS code here. So this is great for [13:54] small tweaks that you don't have to uh [13:57] apply throughout the website and you can [13:59] just make quick changes to your website. [14:00] Again, a great change in WordPress 7.0. [14:03] Another improvement in WordPress 7.0 is [14:05] with regards to template paths and [14:07] synced patterns. If you use FE, this [14:09] might be useful. You already know that [14:10] you can create template paths or sync [14:12] patterns that can work throughout your [14:14] website to keep your designs consistent [14:15] and speed it up. Now there few different [14:17] changes. I'm not going to demonstrate [14:18] but u the idea being that it'll now be [14:21] easier to actually make changes to uh [14:23] those patterns and same blocks if you [14:25] want to. And one of the differences will [14:27] be how easy it will be to understand [14:29] which patterns you're uh actually [14:30] editing. Let me demonstrate with another [14:32] example in WordPress uh regular [14:34] WordPress. This is 7.0 but this has been [14:36] around for a long time. If you're making [14:38] changes to let's say this block, uh [14:40] sometimes it can be distracting if [14:41] everything is in its focus. So you have [14:43] a distraction free mode or also [14:45] spotlight mode. So if you go here and [14:47] you can turn on spotlight mode. So then [14:49] what happens is whatever block you're [14:50] working on that is the only block that's [14:52] highlighted and rest of the blocks kind [14:54] of blur in the background. The same [14:55] feature is coming to sync patterns and [14:57] template paths. So that now it's easier [14:59] for you to understand where you're [15:01] making the changes and focus on the [15:02] editing process. Another welcome change [15:04] in WordPress 7.0. The next big change in [15:07] WordPress 7.0 is a quality of life [15:09] improvement on how headings not work but [15:12] how you use headings. Let me [15:13] demonstrate. So this is WordPress 6.9.4. [15:16] If I wanted to apply a heading, I just [15:18] type in heading and of course we can [15:20] have a heading block here. And then the [15:22] heading block, you see that default is [15:24] H2. So I can type something. Don't [15:27] figure out what I've written. And then I [15:28] can change the heading to whatever [15:30] heading I want. Now this is a three-step [15:32] process instead of just being a onestep [15:34] process. WordPress 7.0 window simplifies [15:36] this. So if I go here, I type in heading [15:39] instantly I can see I can select H4 if I [15:42] want to and then do this. It's pretty [15:45] easy, right? So that's how you do it. [15:47] Another big change in WordPress 7.0 is [15:49] how fonts will be handled. If you've [15:51] used WordPress for a long time, then you [15:52] know that unless you're using a block [15:54] theme or yeah, only with block themes, [15:56] you can have some sort of organization [15:58] when it comes to fonts. But now that [16:00] change is no longer true or that fact is [16:02] no longer true. With WordPress 7.0, to [16:04] you can now manage your fonts entirely [16:07] uh even if you're using non-block based [16:09] themes. So this is WordPress 6.9.4 and [16:12] if you scroll the appearance you just [16:13] see themes editor and starter sites uh [16:15] depending on what plugins you install [16:17] and of course uh only fonts can be or [16:20] fonts can be managed only if inside the [16:22] editing section or the full site editing [16:24] section. But in WordPress 7.0 I'm not [16:26] using a blockbased theme. If I go to [16:28] appearance section I see all these [16:29] things but I also see fonts which is a [16:31] huge thing. So if I go to fonts, you'll [16:33] see that now we can have multiple [16:35] features with regards to fonts directly [16:37] on a WordPress website. So again, this [16:39] might be in beta, something might be [16:40] broken, might not work as well, but you [16:43] can still use it. So we have fonts [16:45] library. So any font you install, you [16:48] can have install fonts. If you connect [16:49] to Google fonts, you can actually see [16:50] all Google fonts here and install [16:52] certain fonts. And you can even upload [16:55] your fonts. Now, this is a huge change [16:56] because I know I have had this pro [16:58] problem and I had to figure out a plugin [17:00] and install a plugin to install custom [17:01] fonts and then all that good stuff. Uh, [17:04] but now all that functionality is right [17:05] now built into WordPress 7.0. Pretty [17:08] [clears throat] awesome. Another huge [17:10] change which I can't demonstrate is [17:12] client side media processing. So, you [17:14] know that whenever you upload images to [17:16] your WordPress website, it's ideal if [17:18] you optimize and resize them. And the [17:21] solution has been that either we do all [17:24] the things up front uh on your computer [17:26] or use an external service or you use a [17:28] plug-in on your site to process the [17:30] images. Now most of the time what [17:32] happens is that these services they do [17:34] two things either they use your own [17:36] servers resources to do whatever [17:38] processing compression resolution [17:42] even cropping the images or they use [17:44] external services which they'll charge [17:45] for which is fine but WordPress 7.0 is [17:48] bringing a new kind of thing which is a [17:50] client side media processing. So instead [17:53] of using your servers resources or [17:56] external services, it'll actually use [17:58] your own web browser capability which [18:00] are free to use to actually do the [18:03] processing of the images automatically [18:05] before the uh the actual images get [18:08] uploaded to your server. So it might [18:11] eliminate the need of having plugins [18:13] actually doing a lot of the heavy [18:14] lifting or even if you use plugins and [18:16] plugins might extend this functionality [18:18] directly that they will do this. So they [18:21] might uh either be faster, they will use [18:24] less of your server resources or if they [18:26] use external services it'll cost you [18:27] less money because most of the heavy [18:29] lifting will be done by the browser. [18:31] Again a huge welcome change. And if this [18:33] is enabled by default a lot of people [18:35] have this problem when they upload [18:37] images they don't realize it. they have [18:38] two big images and which slows down [18:40] their website. So if uh this can be [18:42] configured pre-upload so anybody [18:45] uploading any kind of image can [18:46] automatically be processed before this [18:49] uh image is uploaded to the site and can [18:51] be processed automatically without [18:53] spending any server resources which is [18:55] awesome right so this feature uh the [18:57] technical details are not clear to me [18:59] right now but if they are I might make a [19:01] short about it so make sure you're [19:02] subscribed but it is a welcome change in [19:04] WordPress 7.0. Apart from this, there's [19:07] a few developer related updates which [19:09] I'm not uh I I don't understand 100% but [19:12] I'm going to read them out so that you [19:13] can uh understand what's going on. So [19:15] you have the client signed abilities API [19:18] uh which introduces a standardized [19:20] client sign registry for WordPress [19:22] capabilities uh including abilities and [19:24] workflow API with filter and search [19:26] functionality and improved command [19:28] pallet. So this is something that [19:29] developers can take advantage of. You [19:31] also have an always iframed post editor. [19:34] So the post editor is always I if framed [19:36] regardless of the API version of the [19:38] block use uh which ensures a consistent [19:40] experience and separates UI styles from [19:42] your theme. This is for developers again [19:44] PHP only block registration developers [19:47] can generate blocks and patterns [19:48] entirely server side using using PHP. [19:51] These autoregister with the block API [19:53] and include autogenerated inspector [19:55] controls. And then you also have UI [19:57] primitives and components. The WordPress [19:59] UI package receives a big update with [20:01] new standardized components including [20:02] drop downs, tool tips, field sets, and [20:04] visually hidden elements. And code [20:06] mirror update. The code mirror library [20:08] will be updated to 5.6.65.40 [20:12] allowing for more flexible extensibility [20:14] of code editing interfaces. And PHP [20:17] support version change. Uh WordPress 7.0 [20:20] now officially has dropped support. This [20:22] this part as I understand officially has [20:24] dropped support for insecure versions of [20:26] PHP. That means 7.2 and 7.3 are no [20:30] longer supported by WordPress 7.2. So I [20:33] think WordPress, if you're using [20:35] WordPress, you should be at least on [20:36] PHP8 that has the highest performance. [20:39] So make sure to update. And if you don't [20:40] know how, I think I've made a couple of [20:41] videos about it or you can ask your [20:42] hosting provider to update your servers [20:45] uh PHP to the latest version which is [20:47] supported so that you can get the best [20:48] security, best performance out of your [20:50] WordPress installation. So those are all [20:52] the new features in WordPress 7.0. Which [20:54] one has been your favorite? Let me know [20:56] in the comments and make sure to [20:57] subscribe and do all that good stuff and [20:59] make sure to watch our shots as well. [21:00] You can follow us on Instagram, Tik Tok [21:02] and all the other channels where we post [21:03] shots almost daily and uh you can just [21:06] uh let let us know any feedback in the [21:08] comments as well. You're watching Ivra [21:10] from Winners YouTube channel and I'll [21:12] catch you in the next video. Take care.  📄 **Full text:** ![[Full Document Contents/Articles/WordPress 7.0 - Everything New!|WordPress 7.0 - Everything New!, YouTube]] ## Highlights - version, I didn't feel it jarring, but now since I use this, that feels a little jarring that hey, how will we be living with this? So that's a welcome change in WordPress 7.2 as well. The next big change in WordPress is a web client AI API. So let me demonstrate or talk about it because it's not something I can demonstrate right now because it's still in the planning phase. And the you can think about it like this. The infrastructure for whatever I'm going to talk about is right now that's what's been placed in WordPress 7.0. When will it be publicly available and the impact ([View Highlight](https://read.readwise.io/read/01kmzmgzwxqhvqq6dpjmwzqq6x)) - Tags: 👻 ai highlighted - page or whatever you're creating. The benefit is obvious that you can leave comments, you can collaborate and have content written at it together. So that's a very big change coming to WordPress 7.0. And if you have a team of writers, if multiple write content, you write content, collaborate with writers, this is going to be a change. It's not shipped in the beta, so I can't demo it right now, but again, a huge change coming to WordPress 7.0 or maybe 7.x. The next big change in WordPress 7.0 is how the revisions work. If you are a ([View Highlight](https://read.readwise.io/read/01kmzmgzxnqnnhwqkbwf3gc81j)) - Tags: 👻 ai highlighted - automatically. Again, a useful feature. And I'm not sure if uh the video is actually downloaded to your site and then used or it directly plays via the remote server because that uh will make a huge difference on how resources are utilized. So if I get more information, I'll leave that in the comments. But again, useful change in WordPress 7.0. The next big change is with navigation menus in WordPress 7.0. There are few different changes and the implications even better. So let me show you directly. So this is WordPress 6.9.4 and ([View Highlight](https://read.readwise.io/read/01kmzmgzywefpn7p0bmvttc4cz)) - Tags: 👻 ai highlighted - longer supported by WordPress 7.2. So I think WordPress, if you're using WordPress, you should be at least on PHP8 that has the highest performance. So make sure to update. And if you don't know how, I think I've made a couple of videos about it or you can ask your hosting provider to update your servers uh PHP to the latest version which is supported so that you can get the best security, best performance out of your WordPress installation. So those are all the new features in WordPress 7.0. Which one has been your favorite? Let me know in the comments and make sure to subscribe and do all that good stuff and make sure to watch our shots as well. ([View Highlight](https://read.readwise.io/read/01kmzmh02b61ty27fymmp68xy3)) - Tags: 👻 ai highlighted