The future of WordPress 2027: Data liberation and the new admin

As we approach the release of WordPress 6.9 and look towards version 7.0 in 2027, the world’s most popular CMS represents something very different than it did in 2020. The “Gutenberg Phase 3” (Collaboration) is maturing, and the community is now looking at Phase 4: Multilingual and the broader Data Liberation initiative.

What could the WordPress of 2027 look like for developers and agencies? Our bet: faster, more open, and fundamentally redesigned. Everything below is a forecast drawn from the public direction of the project, not a list of shipped features.

Here are WPPoland’s core predictions and analysis for the 2027 roadmap.

#1. The redesigned admin: Goodbye wp-admin?

The left-hand sidebar menu of wp-admin has been with us since WordPress 2.7 (2008). We expect 2027 to be the year it finally retires. If that happens, it will not be a cosmetic refresh but a rethink of how people interact with the CMS.

#The unified canvas

The distinction between “The Dashboard” and “The Site Editor” is vanishing, and we expect the two to merge into one contextual canvas.

• Contextual Editing: You would not go to “Settings” to change the site title. You click the title in the editor and change it where you see it.
• JavaScript-First: The new admin is likely to be a Single Page Application (SPA). Transitions become instant, and saving a post no longer reloads the page.
• Customizability: Agencies could curate the admin experience natively, locking down specific blocks and branding the interface without hacking functions.php. For teams handing sites over to non-technical editors, that is the part that matters day to day.

#What changes for developers

Developers who built a career on PHP hooks for admin customisation will need a wider toolkit. React and the WordPress REST API move from “nice to have” to baseline. The PHP core itself stays stable: our expectation is that only the presentation layer moves, so server-side skills keep their value.

Learn more about professional WordPress development at WPPoland.

#2. Data liberation: Trust through openness

One of Matt Mullenweg’s key initiatives for the mid-2020s has been Data Liberation, arguably the most counterintuitive project in the history of WordPress.

#The paradox of lock-in

Historically, SaaS platforms try to lock you in. Wix, Squarespace and Shopify make it deliberately awkward to take your content elsewhere. We expect WordPress 2027 to go the opposite way.

• Universal Export: A standardized JSON/ZIP format that would let you move an entire site (content, media and design) to another CMS or another WordPress host in one step, instead of fragmented WXR files that drop images and metadata.
• Import from anywhere: Data Liberation is not only about leaving. It also covers solid importers from Wix, Squarespace, Ghost, Medium and similar platforms, which makes moving to WordPress easier.
• Why?: By making it easy to leave, WordPress makes people confident to stay. It becomes the “Switzerland of the Web”, the neutral, safe place for your data. Once you know you are not trapped, the fear of committing goes away.

#What it means for enterprise buyers

For large organisations, Data Liberation removes one of the standard objections to WordPress: vendor lock-in risk. A CTO or enterprise architect can sign off on WordPress knowing a clean exit path exists. Our prediction is that this raises enterprise adoption rather than lowering it.

#3. The death of the “theme”

What will a theme be in 2027? Almost certainly not a folder of PHP templates. The shift has been gradual, and we expect 2027 to be where it reaches its logical end.

#Style.json and patterns

• Global Styles: The visual identity of a site is defined in theme.json (or its successor). Colours, typography, spacing and shadows live in one declarative configuration file.
• Pattern Libraries: A “theme” becomes a curated collection of Block Patterns. You would not buy a theme so much as subscribe to a pattern provider, and combine those patterns into whatever layout you need.
• The End of Child Themes: Child themes stop being necessary for style overrides. You use the Global Styles interface and export your changes as a variation, which also removes a common source of breakage: conflicts between parent and child themes.

#What this means for agencies

Agencies that sold packaged premium themes need a different business model. We expect the value to move to:

1. Design systems: consistent, scalable pattern libraries built for a specific brand.
2. Brand translation: turning a brand identity into a custom theme.json configuration.
3. Migration and optimisation: moving clients from legacy PHP themes to modern block architecture.

#4. AI in the core

Until 2025, AI was plugin territory. By 2027, we expect it to be native. The point is not replacing people but removing repetitive tasks that eat time.

#Local LLMs?

There is discussion about bundling lightweight, local-first LLMs (or connecting to browser-based AI APIs) directly in Core.

• Auto-Alt Text: The media library could generate alt text on upload. Beyond convenience, that helps web accessibility, and for anyone selling into the EU it supports compliance with the European Accessibility Act.
• Content Summaries: The “Excerpt” field is pre-filled with an AI summary. Editors review and adjust instead of starting from a blank field.
• Pattern Generation: Ask for “a pricing table with 3 columns” and the block editor builds it from core blocks, with no page builder or third-party plugin involved.

#AI-assisted translation

Phase 4 (Multilingual) combined with core AI would allow assisted translation inside the editor. An editor writes in one language and gets draft versions in others that only need human review. For multilingual publishers this could turn a slow, expensive process into a normal editorial step.

#5. Multilingual is native (phase 4)

For 20 years, we needed WPML or Polylang. Phase 4 is set to change that, and it is probably the update multilingual publishers are waiting for most.

#Canonical multilingual

• Standardized Database Schema: The expectation is that core tables will support translations officially, with no more wp_icl_translations bolted on the side and translation relationships handled in the data structure itself.
• Performance: Native query support would mean multilingual sites would no longer pay the extra queries and joins that translation plugins add today, because translations become part of the architecture rather than an add-on.
• Impact: This would kill a large segment of the plugin market but massively improve the experience for global enterprises. For English-language businesses serving Canada, the EU or other bilingual markets, a single core-supported setup is a real simplification.

#What changes for content strategy

With native multilingual, a global content strategy gets simpler. One WordPress site could serve several languages with clean URLs, automatic hreflang and central translation management, instead of separate installs or a complex Multisite network per language. If search visibility across markets matters to you, see our GEO and LLMO optimisation service.

#6. The rise of “WordPress distros”

With the core becoming more modular, we expect specialized distributions to appear, the way Linux has Ubuntu, Fedora and Arch for different jobs.

• E-Commerce Distro: A pre-packaged WordPress tuned solely for WooCommerce (no blog bloat), with performance focused on catalogues, carts and checkout.
• Headless Distro: A stripped-down API-only version for use with Next.js or Astro: no front-end theme, no unnecessary admin assets, just the REST/GraphQL API and the content editor.
• Creator Distro: A simplified version for newsletter authors, competing directly with Substack and Ghost, with subscriptions and email distribution built in.
• Enterprise Distro: Aimed at organisations with strict security, compliance and governance requirements, with SAML authentication, corporate directory integration and content approval workflows. Related: our WordPress security audit.

#7. The WordPress ecosystem in 2027

#The role of agencies

“Install WordPress and pick a theme” stops being a service anyone pays for. We expect successful agencies to focus on:

• Solution architecture: choosing the right mix of core, plugins and external services for each business case.
• AI integration: configuring core AI features for a client’s specific editorial workflow.
• Global content strategy: using native multilingual for sites that span several markets and languages.
• Performance at scale: keeping enterprise sites within good Core Web Vitals under heavy load.

#The plugin ecosystem

Plugins that duplicate what moves into core (multilingual, basic AI, patterns) would lose relevance. The ones likely to thrive offer genuinely specialised functionality: CRM integrations, custom business logic and niche tools core will never cover.

#8. Preparing for 2027: practical steps

None of this requires waiting for a release. These steps pay off whichever way the roadmap lands:

1. Move to block themes now: If you still run a classic PHP theme, start the transition to a block theme (FSE). The longer you wait, the more painful it gets.
2. Learn React: If the admin goes JavaScript-first, React and the block API are where customisation work will happen.
3. Adopt theme.json: Define your site’s styles in theme.json instead of custom CSS.
4. Plan for multilingual: If your site will need several languages, structure content with translation in mind. Moving from WPML or Polylang to native multilingual will be easier if the content is already well organised.
5. Experiment with AI: Get familiar with AI tools for content work, so you know how to use them well once they sit inside the editor.

Talks from WordCamp Europe and WordCamp US are published on WordPress.tv, and they are a free way to follow where core contributors are taking these projects.

#9. Conclusion: The operating system of the open web

In 2027, we expect WordPress to be less of a “blogging tool” and more of an Operating System for the Web: the base layer of data ownership, user management and block rendering on which everything else is built.

For developers, the practical consequence is to build block-first: custom blocks registered through block.json, block themes with theme.json, and content stored in structures that the Data Liberation importers and exporters can read. Code built around the classic editor and shortcodes is the part most likely to need rework.

The future is open. Are you ready? Learn more about professional WordPress development at WPPoland.