{"id":7774,"date":"2026-03-14T12:05:43","date_gmt":"2026-03-14T09:05:43","guid":{"rendered":"https:\/\/devmaverick.com\/?p=7774"},"modified":"2026-03-14T12:13:09","modified_gmt":"2026-03-14T09:13:09","slug":"wordpress-7-0-and-my-wordpress","status":"publish","type":"post","link":"https:\/\/devmaverick.com\/wordpress-7-0-and-my-wordpress\/","title":{"rendered":"WordPress 7.0 and My WordPress"},"content":{"rendered":"
In April we’ll be getting a new version of WordPress, a major update.<\/p>\n
As I’m writing this article, WordPress 7.0 is on beta 5<\/a>.<\/p>\n Here’s the complete list of features planned for WordPress 7.0:<\/p>\n A few of the features I’m looking forward to:<\/p>\n You can now run WordPress directly in your browser by visiting my.wordpress.net<\/a>.<\/p>\n A WordPress instance that runs directly in your browser, locally, and is saved for future sessions. So if you come back later and visit the address, everything you worked on will still be there.<\/p>\n It’s not hosted anywhere, it can’t be accessed from the outside. It’s a local instance that even supports installing themes and plugins.<\/p>\n Its purpose seems to be more geared toward keeping a personal journal or organizing information, with a strong focus on privacy, since everything is stored on your device.<\/p>\n Not a development tool like Studio or Local.<\/p>\n If it becomes popular, I think we’ll see a lot of hosting services or plugins that let you sync from this local instance directly to the server where your site lives.<\/p>\n One example would be working on your articles directly in this instance, and when you’re ready, triggering a sync that pushes everything to your production site.<\/p>\n The same could apply across devices \u2014 if you want to open it on your laptop or phone, you’d always have the latest version synced between them.<\/p>\n For now, it comes with a few available apps, different from what we’re used to in WP:<\/p>\n More details:<\/p>\n WordPress 7.0 In April we’ll be getting a new version of WordPress, a major update. As I’m writing this article, WordPress 7.0 is on beta 5. Here’s the complete list of […]<\/p>\n","protected":false},"author":2,"featured_media":7783,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[40],"tags":[157,43],"class_list":["post-7774","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wordpress","tag-gutenberg","tag-wordpress"],"yoast_head":"\n\n
\n
\nThis seems like an incredibly useful feature. Many of us are already familiar with this kind of collaboration from Figma, where you can leave comments on a design, tag someone, and mark an issue as resolved. Having this available in Gutenberg opens up a lot of possibilities. The marketing team can work on drafts and leave suggestions and comments until they reach the final version. Much more natural than making changes in a document.<\/li>\n
\nAn API integration that can then be called and used from plugins or themes, but in a centralized way, trying to use the model you’ve defined in WP.<\/li>\n
\nThe ability to create blocks directly from PHP. There are some limitations around the fields that can be used with these blocks, but at least now this option exists for those who don’t want to use React.
\nhttps:\/\/make.wordpress.org\/core\/2026\/03\/03\/php-only-block-registration\/<\/a><\/li>\n
\nBetter control over navigation, including on mobile.<\/li>\n
\nIn my opinion, this is the most important update for editing in Gutenberg. A lot of people prefer to use Elementor or Kadence simply because Gutenberg doesn’t offer the ability to control core blocks based on the device’s breakpoint. I hope it will be implemented in 7.0, with support not just for hiding certain blocks at different screen sizes, but also for applying different values for padding, margin, background-color, and so on.<\/li>\n<\/ul>\nMy WordPress<\/h2>\n
\n
<\/p>\n\n