Planning a Drupal site launch before year end means starting on Drupal 11 and confirming hosting, security, and go-live checks first. Drupal is an open-source content management system for building and managing websites. That starting point matters because timing is tight. Drupal.org's core release schedule says Drupal 10 reaches end of life on December 9, 2026, with Drupal 12 arriving the same week, so a new December launch has no margin for an older foundation Drupal.org core release schedule.
Table of Contents
- Start on Drupal 11, not Drupal 10
- Does your hosting meet Drupal 11 minimums?
- Who handles updates after launch?
- What should the final go-live review cover?
- What if the site is still on Drupal 10?
Start on Drupal 11, not Drupal 10
A new site launched now should begin on Drupal 11. Drupal 10 will receive no further releases after its end-of-life date, including security fixes.
That cutoff affects planning, budgeting, and support. Choosing Drupal 11 avoids launching a site that needs a major upgrade within days.
Does your hosting meet Drupal 11 minimums?
Check PHP first. Drupal.org's PHP requirements guide says Drupal 11 requires PHP 8.3 or later, so servers still on PHP 8.1 or 8.2 must be upgraded before launch Drupal.org PHP requirements guide. Then check the database and build tools.
Teams must verify MySQL 8.0, MariaDB 10.6 or PostgreSQL 16, plus Composer 2.7 or newer, during environment setup, according to the Eway Corp checklist citing Drupal.org requirements Eway Corp Drupal 11 upgrade checklist. Run these checks in staging before moving content or DNS. A host that cannot provide the required versions is not ready for a year-end launch.
Who handles updates after launch?
Core updates alone do not secure a launch. The Drupal Security Team states in its October 2026 advisory that site owners remain responsible for monitoring and maintaining hosting-platform security, including PHP and third-party libraries Drupal Security Team advisory. That means assigning ownership before go-live.
Name who patches the server, who updates Drupal core and modules, and how often each task happens. Also plan for faster minor-release cycles in 2027. Ordinary minors will receive only eight months of security coverage, with six months of bug and security support followed by two months of security-only support.
What should the final go-live review cover?
Drupal.org's launch checklist directs teams to complete security review, permissions checks, backups, monitoring, performance testing, and SEO and accessibility review before go-live. Treat each item as a gate, not a suggestion.
Use a short pass in launch week: Fix problems found in staging, then retest. Launch only when each check passes.
- review user roles, permissions, and admin accounts
- confirm automated backups and test a restore
- enable maintenance alerts, logs, and uptime monitoring
- test page speed and behavior under expected traffic
- check titles, metadata, redirects, forms, and keyboard access
What if the site is still on Drupal 10?
Do not launch fresh on Drupal 10. For an existing project, patch first, then upgrade.
Existing Drupal 10 sites must already run Drupal 10.3.0 or later to move directly to Drupal 11. The practical path is to update to a supported 10.6 release now, confirm contributed modules work, then upgrade to Drupal 11.
