Drupal 12 development concept showing a modern content management dashboard and AI integration

1. What Is Drupal 12?

Drupal 12 is the next major version of the Drupal open-source content management system.

It continues the architectural direction established by Drupal 10 and Drupal 11, with a focus on modern development standards, improved dependencies, cleaner APIs and long-term maintainability.

Drupal is widely used for projects that require:

  • Complex content structures.
  • Multiple user roles and permissions.
  • Enterprise content management.
  • Multilingual websites.
  • Large publishing platforms.
  • Government and educational portals.
  • E-commerce applications.
  • Headless and decoupled architectures.
  • Custom business applications.

Unlike a simple website builder, Drupal provides a flexible framework for building structured, scalable and highly customized digital platforms.

Drupal 12 continues this approach while removing older implementation patterns that have become unnecessary or outdated.

2. Drupal 12 Release Date and Development Timeline

Drupal 12 is scheduled for release in December 2026.

According to the official Drupal core release schedule, the current planned milestones are:

Milestone Expected date
Drupal 12 Alpha September 2026
Drupal 12 Beta 1 Week of September 14, 2026
Drupal 12 Release Candidate 1 Week of November 9, 2026
Drupal 12.0.0 Stable Release Week of December 7, 2026
Drupal 11.5.0 Release Week of December 7, 2026
Drupal 10 End of Life December 9, 2026

The release schedule is maintained by the Drupal core release managers, and planned dates can change if release requirements are not completed.

The beta and release-candidate versions are primarily intended for testing, compatibility checks and development preparation. They should not be treated as production-ready alternatives to the stable release.

For development teams, this period is particularly important because contributed modules, custom themes and existing applications need compatibility testing before production upgrades.

3. What Is New in Drupal 12 Compared to Older Versions?

One important thing to understand is that Drupal 12 is primarily a platform modernization release rather than a complete redesign of the CMS.

Many improvements that users associate with the Drupal 12 experience were introduced during Drupal 11’s development cycle. Drupal 12 builds on those improvements and removes older code and dependencies.

Let’s examine the major changes.

3.1 Updated PHP Requirements

One of the most important technical changes is the updated PHP requirement.

Drupal 12 requires PHP 8.5 or later.

This means organizations running older PHP environments will need to plan infrastructure updates before upgrading.

PHP modernization provides a foundation for using newer language features, maintaining compatibility with current libraries and reducing dependence on outdated code.

Development teams should review:

  • Current PHP versions.
  • Composer dependencies.
  • Custom module compatibility.
  • Third-party library requirements.
  • Hosting environment compatibility.
  • Automated deployment configurations.

Businesses should not assume that an existing Drupal 10 or Drupal 11 hosting environment will automatically support Drupal 12.

3.2 Updated Symfony and Development Dependencies

Drupal relies on several external PHP libraries and frameworks.

Drupal 12 introduces important dependency updates, including:

  • Symfony 8.1.
  • Guzzle 8.0.
  • PHPUnit 12.5.
  • Updated development and testing dependencies.

These updates help Drupal remain aligned with the modern PHP ecosystem.

For developers, this also means that older custom implementations and contributed modules may require changes.

Dependency compatibility should be checked before starting an upgrade.

3.3 Removal of Deprecated Modules and Code

One of the biggest differences between Drupal 11 and Drupal 12 is the removal of functionality that has already been deprecated.

Some modules and extensions removed from Drupal core include:

  • Ban.
  • Contact.
  • Field Layout.
  • History.
  • Migrate Drupal.
  • Migrate Drupal UI.
  • Settings Tray.
  • Shortcut.
  • Telephone.
  • Stable 9.

Some of these extensions may be available through contributed projects, while others require developers to use alternative approaches.

It is important to understand that removing a module from core does not necessarily mean that the functionality can no longer be implemented.

For example, the Migrate Drupal and Migrate Drupal UI modules have been removed from core, but the underlying Migrate API remains available.

Before upgrading, developers should identify whether the website depends on any removed extensions and plan the appropriate replacement.

3.4 Modernization of the Drupal Codebase

Drupal 12 continues the work of simplifying the core codebase.

This includes removing deprecated APIs, modernizing PHP implementations and improving consistency across the codebase.

Some development changes include:

  • Greater adoption of modern PHP coding practices.
  • Constructor property promotion in core.
  • Updated static analysis standards.
  • Removal of legacy testing approaches.
  • Updated dependency compatibility.
  • Improved maintainability of core components.

For developers maintaining custom Drupal modules, this makes it important to review deprecated functions and older implementation patterns.

3.5 HTMX 4 Integration

Another notable development is the move to HTMX 4.

HTMX allows developers to build dynamic website interactions using HTML attributes and server-driven responses, reducing the need for large amounts of custom JavaScript.

Drupal introduced HTMX integration in its core development direction during Drupal 11.3, and Drupal 12 moves forward with HTMX 4.

Potential development benefits include:

  • More dynamic forms.
  • Partial page updates.
  • Improved interactive interfaces.
  • Server-driven UI interactions.
  • Reduced dependence on custom JavaScript for certain workflows.

This does not mean JavaScript frameworks such as React or Vue are no longer necessary.

HTMX is particularly useful for server-rendered applications, while React and similar frameworks remain appropriate for highly interactive applications and decoupled frontends.

3.6 Improved Development and Testing Standards

Drupal 12 also moves toward newer testing and code-quality standards.

PHPUnit 12.5 and PHPStan level 3 are among the important development changes.

These improvements help development teams identify problems earlier, maintain code quality and build more reliable custom modules.

For organizations maintaining large Drupal applications, consistent testing is particularly important because even a relatively small core upgrade can affect multiple integrations and custom workflows.

3.7 Improved Security Foundations

Drupal 12 introduces updated platform requirements and removes older code that is no longer part of the supported development direction.

The default password hashing algorithm also changes to Argon2id, subject to the necessary PHP environment support and configuration.

Other important security practices remain essential:

  • Regular security updates.
  • Secure authentication.
  • Proper user permissions.
  • Secure API integrations.
  • Database protection.
  • File upload validation.
  • Security testing.
  • Dependency monitoring.

A major version upgrade does not automatically make an existing website secure. Security still depends on implementation quality, configuration, maintenance and timely updates.

4. Drupal 12 Compared to Drupal 10 and Drupal 11

Understanding the differences between versions helps businesses decide whether they should upgrade immediately or prepare for a staged migration.

Area Drupal 10 Drupal 11 Drupal 12
PHP support PHP 8.1+ baseline, depending on minor release PHP 8.3+ baseline PHP 8.5+
Architecture Modern Drupal architecture Further modernization More deprecated code removed
Dependencies Older supported dependencies Updated Symfony and libraries New major dependency versions
HTMX Not a core integration in the original Drupal 10 release Core integration introduced during Drupal 11 HTMX 4 direction
Admin experience Claro and Toolbar-era experience Navigation improvements and Gin experimentation Continues modern admin direction
Development standards Modern PHP practices Improved APIs and tooling Further cleanup and updated testing
AI capabilities Contributed AI ecosystem available Expanding AI ecosystem AI-ready foundation, with AI features primarily through ecosystem integrations
Long-term direction Older supported major version Current platform generation New major platform generation

The table describes the overall version direction rather than suggesting that every feature first appeared in Drupal 12.

For example, the Navigation module and experimental Gin administration theme were already introduced during Drupal 11 development.

5. Important Drupal Improvements Introduced During Drupal 11

To understand Drupal 12 properly, it is also useful to look at the improvements that arrived in Drupal 11.

These features are particularly relevant because Drupal 12 builds upon the work completed in the previous major version.

Navigation Module

The Navigation module provides a more modern administrative navigation experience.

It helps administrators access content, configuration and other management areas through an improved interface.

This is particularly useful for websites with large content teams and complex administration requirements.

Gin Administration Theme

Gin provides a modern administration experience with features such as improved layouts, visual refinements and dark mode.

It is intended to provide a more contemporary experience for Drupal administrators.

Drupal Recipes

Recipes allow developers to package and apply predefined site configurations.

For example, a development team could prepare a recipe for:

  • A publishing website.
  • An event management system.
  • An e-commerce application.
  • A multilingual website.
  • A custom content management workflow.

Recipes help standardize common implementation patterns and reduce repetitive configuration work.

Drupal Canvas

Drupal Canvas is part of the wider effort to make Drupal page building and content creation more intuitive.

It focuses on providing a visual experience for assembling pages and managing components.

It is particularly relevant to teams that want more control over page layouts without requiring developers to manually implement every content change.

These developments are important because they make Drupal more approachable for editors, marketers and professional website-building teams.

6. How AI Is Changing Drupal Development

Artificial intelligence is becoming an important part of modern web development.

Drupal is also moving toward an AI-enabled ecosystem, where AI can assist developers, content editors, administrators and business users.

The Drupal AI ecosystem provides opportunities to connect large language models, automation tools and intelligent services with Drupal websites.

AI should not be considered a replacement for Drupal’s core functionality. Instead, it can extend the platform and help automate tasks that traditionally require manual work.

6.1 AI-Powered Content Creation

Content teams often spend considerable time preparing articles, product descriptions, metadata and website content.

AI integration can help editors:

  • Generate initial article drafts.
  • Create product descriptions.
  • Suggest SEO titles and meta descriptions.
  • Generate summaries.
  • Rewrite content for different audiences.
  • Suggest content categories and tags.
  • Prepare multilingual content drafts.

For example, an editor working on a Drupal website could provide a topic and generate an initial article draft through an integrated AI service.

The editor can then review, modify and approve the content before publishing.

6.2 AI-Assisted Content Management

AI can also help administrators and editors work with existing website content.

Potential applications include:

  • Finding outdated content.
  • Identifying duplicate articles.
  • Categorizing content automatically.
  • Generating content summaries.
  • Suggesting internal links.
  • Identifying missing metadata.
  • Preparing content for review.

For large publishing websites, these capabilities can make content management more efficient.

6.3 AI-Powered Search

Traditional website search often depends on matching exact keywords.

AI-powered semantic search can understand the meaning and intent behind a user’s query.

For example, a user searching for “how to protect my business website from cyberattacks” could receive relevant articles about website security, vulnerability testing and data protection even when those exact words do not appear together in the content.

A Drupal semantic search solution may combine:

  • Content indexing.
  • Text embeddings.
  • Vector databases.
  • Semantic retrieval.
  • AI-generated answers.
  • Access-aware content filtering.

This can be particularly useful for government portals, educational platforms, documentation websites and enterprise knowledge bases.

6.4 AI Chatbots and Website Assistants

Drupal websites can integrate AI-powered chatbots that answer visitor questions using approved website content.

For example:

A university website could provide an AI assistant that helps students find admission requirements, course information, application deadlines and fee details.

A government website could provide an assistant that explains available services and guides users to the correct forms.

An e-commerce website could use an AI assistant to help customers locate products and understand product information.

A well-designed implementation should retrieve answers from trusted sources and provide links to the original information.

6.5 AI-Powered Website Administration

AI can also assist with website configuration and administrative activities.

Potential use cases include:

  • Suggesting content types and fields.
  • Generating taxonomy suggestions.
  • Helping editors configure content workflows.
  • Assisting with website documentation.
  • Summarizing configuration changes.
  • Supporting administrators through natural-language assistance.

Drupal CMS’s longer-term product strategy is especially relevant here. Its direction is to make workflows AI-enabled, including site setup, content structure and editorial processes.

The intention is to allow AI to assist with tasks while keeping humans responsible for important structural and editorial decisions.

6.6 AI for Drupal Development and Maintenance

AI tools are changing how developers build and maintain Drupal applications.

Development teams can use AI coding assistants to help with:

  • Generating custom module scaffolding.
  • Writing boilerplate PHP code.
  • Creating JavaScript components.
  • Understanding existing codebases.
  • Identifying potential bugs.
  • Preparing unit tests.
  • Explaining unfamiliar Drupal APIs.
  • Reviewing code changes.
  • Supporting migration planning.

For example, a developer maintaining an older Drupal 9 or Drupal 10 application can use AI-assisted tools to identify deprecated functions and prepare possible code updates.

However, AI-generated code must be reviewed and tested. Drupal-specific APIs, security permissions, database queries and cache behaviour require technical validation.

7. Drupal AI: What Can Businesses Build?

The combination of Drupal and AI opens opportunities for applications beyond conventional websites.

Here are some practical examples.

AI-Powered Enterprise Knowledge Portal

An enterprise website can store internal documents, articles, policies and technical information in Drupal.

An AI assistant can help employees search the knowledge base using natural language.

AI-Enabled E-commerce Platform

Drupal Commerce can be extended with AI capabilities such as:

  • Intelligent product recommendations.
  • Product description generation.
  • Natural-language product search.
  • Customer support assistants.
  • Automated catalogue classification.
  • Product information extraction.

AI-Powered Government Website

Government websites often contain large amounts of information and complex service documentation.

An AI assistant can help citizens locate relevant services, understand application procedures and find official documentation.

AI-Enabled Education Platform

Educational institutions can integrate AI assistants to help students search courses, understand admission requirements and locate learning resources.

AI-Powered Content Publishing Platform

Publishing organizations can use AI for content classification, summaries, editorial assistance, metadata generation and multilingual content workflows.

8. Drupal 12 and Headless CMS Development

Headless Drupal is another important development direction.

In a traditional Drupal website, Drupal manages both content and the frontend presentation.

In a headless or decoupled architecture, Drupal manages the content and backend functionality while a separate frontend application displays the website.

A common architecture includes:

  • Drupal as the content management backend.
  • React or Next.js as the frontend.
  • JSON or GraphQL for content delivery.
  • PostgreSQL or MySQL for database management.
  • CDN and caching services.
  • External AI services where required.

Benefits of Headless Drupal

Frontend flexibility: Developers can use modern JavaScript frameworks to build customized user experiences.

Content reuse: The same content can be delivered to websites, mobile applications and other digital channels.

Independent development: Backend and frontend teams can work separately.

Integration flexibility: Drupal can connect with external business applications and services.

AI integration: AI services can be connected to the backend or frontend depending on the use case.

Headless Drupal is particularly useful for large organizations that need multiple digital channels and complex content delivery requirements.

However, it is not automatically the best choice for every website. Traditional Drupal can be more practical when the project depends heavily on Drupal’s built-in rendering, editorial workflows and administrative capabilities.

9. Drupal 12 Migration: What Existing Website Owners Should Know

Businesses currently running Drupal 10 or Drupal 11 should begin evaluating their upgrade requirements.

A Drupal major-version upgrade is not simply a matter of replacing the core files.

Custom modules, themes, contributed extensions, Composer dependencies and integrations all need to be reviewed.

Drupal 10 to Drupal 12

Drupal 10 is scheduled to reach end of life on December 9, 2026.

Businesses operating Drupal 10 websites should prioritize a migration assessment.

A direct upgrade from older Drupal 10 versions should not be assumed to be available.

The recommended route is to update to a supported Drupal 11 release first and then prepare for Drupal 12.

Drupal 11 to Drupal 12

Drupal 11 websites will generally have a more straightforward upgrade path, provided they meet the required platform and code compatibility conditions.

The recommended preparation includes:

  1. Update the Drupal 11 installation to the latest suitable release.
  2. Review contributed modules and themes.
  3. Check compatibility using Upgrade Status.
  4. Identify deprecated APIs in custom code.
  5. Replace or migrate removed core extensions.
  6. Verify PHP and database requirements.
  7. Update Composer dependencies.
  8. Test the upgrade in a staging environment.
  9. Run database updates and automated tests.
  10. Deploy after successful validation.

Drupal’s upgrade documentation recommends preparing on the latest supported Drupal 11 releases before upgrading to Drupal 12.

Important Migration Considerations

Before upgrading, review:

  • Custom modules.
  • Custom themes.
  • Contributed modules.
  • Composer packages.
  • Database compatibility.
  • PHP version.
  • External APIs.
  • Search integrations.
  • E-commerce functionality.
  • User roles and permissions.
  • Content migration requirements.
  • Automated tests.

For complex websites, a complete technical audit should be completed before deciding the upgrade timeline.

10. Drupal 12 Development: Challenges for Developers

Although Drupal 12 provides a more modern development foundation, the upgrade process may introduce challenges.

Contributed Module Compatibility

Not every contributed module will immediately have a stable Drupal 12-compatible release.

Development teams may need to identify alternatives, update custom code or contribute compatibility fixes.

Custom Code Modernization

Older modules may use deprecated APIs, legacy hooks or outdated dependencies.

These implementations should be reviewed and modernized.

PHP Environment Updates

The PHP 8.5 requirement means hosting environments and local development tools must be updated.

Third-Party Dependencies

Some Composer packages may require newer versions or replacement libraries.

Regression Testing

Changes to core APIs and dependencies can affect existing functionality.

A thorough testing strategy is particularly important for websites with custom workflows, integrations and e-commerce functionality.

11. Should Businesses Upgrade to Drupal 12 Immediately?

The right decision depends on the current Drupal version, website complexity, module compatibility and business requirements.

For Drupal 10 website owners: Begin migration planning now. With Drupal 10 reaching end of life in December 2026, remaining on an unsupported version after that date creates security and maintenance risks.

For Drupal 11 website owners: Review compatibility and plan the upgrade after the stable Drupal 12 release. There is no need to rush a production upgrade before the contributed module ecosystem is ready.

For businesses planning a new Drupal project: Evaluate Drupal 12’s stable release and ecosystem maturity before selecting the platform. If the project must launch before December 2026, Drupal 11 may be the more practical starting point, with an upgrade path planned.

For enterprise websites: Conduct a technical assessment first. Large websites should prioritize module compatibility, integrations, testing and deployment planning rather than upgrading simply to use the newest major version.

12. How Xenixsoft Can Help With Drupal 12 Development and Migration

Upgrading to a new Drupal version requires a clear understanding of the existing website architecture, custom functionality, third-party integrations and business requirements.

Xenixsoft provides Drupal development, migration, custom module development and ongoing website maintenance services.

Our approach can include:

  1. Drupal technical audit: Review the current Drupal version, custom modules, themes, Composer dependencies and hosting environment.
  2. Compatibility assessment: Identify deprecated APIs, removed core extensions and contributed module compatibility issues.
  3. Migration planning: Prepare a practical upgrade roadmap based on the website’s architecture and business priorities.
  4. Custom module modernization: Update custom implementations to work with the new Drupal platform and current development standards.
  5. Drupal 12 development: Build new functionality, custom workflows, integrations and enterprise website features.
  6. AI integration: Implement AI-powered content assistance, chatbots, semantic search, document processing and business-specific automation.
  7. Testing and deployment: Validate functionality, security, performance and integrations before production deployment.
  8. Ongoing support: Provide maintenance, security updates, technical improvements and future version upgrade assistance.

For organizations that want to modernize their existing Drupal websites, the objective should be more than completing a version upgrade. It should be to create a stable, maintainable platform that supports future business requirements.

13. Final Thoughts: The Future of Drupal Development

Drupal 12 represents another step in the platform’s technical modernization.

Its updated PHP requirements, newer dependencies, removal of deprecated code and continued development improvements provide a stronger foundation for future Drupal projects.

However, the bigger opportunity extends beyond the core release itself.

AI integration, headless architecture, intelligent search, automated content workflows and modern digital experiences are changing how organizations use content management systems.

For businesses running older Drupal installations, the upcoming release is a good opportunity to review their technical architecture and prepare a migration strategy.

For organizations planning new projects, Drupal remains a strong option for complex content management, enterprise integrations and customized digital platforms.

The most effective approach is to combine Drupal’s structured content and extensibility with modern frontend technologies, well-designed integrations and AI capabilities that solve genuine business problems.

HAVE A PROJECT IN MIND?

Let's Find the Right Approach.

Start a Conversation