Drupal 9 is set to reach its end-of-life on November 1st, 2023. This deadline is sending ripples throughout the Drupal community and has made it crucial for businesses to plan for a seamless Drupal 10 migration. 

Regardless of whether you're currently using Drupal 7, Drupal 8, or Drupal 9, this transition is not just a necessity; it's an opportunity to embrace the latest in web development and secure your digital presence for the future. Let’s have a closer look at the significance of the Drupal 9 end-of-life and explore what you need to know to prepare for a smooth transition to Drupal 10. 

Why Drupal 9 End-of-Life Matters? 

End-of-life for any software version means that the development and security support for that version will cease. 

In the context of Drupal 9, bug fixes, or security patches are provided for Drupal 9. This poses a critical concern for businesses and website owners who rely on Drupal to power their online presence. 

With any technology, there will be doomsday sayers and there will be the normal evolution of growth and decline. Knowing the power of Drupal and the character of the Drupal community, I’m optimistic that Drupal will be a viable CMS for years to come. But, where does that leave Drupal 7? Let's take a look at a brief history of Drupal 7 and beyond, and what D7 end-of-life (EOL) options are available.

• Articles

• Drupal Planet
• Drupal
• CMS
• Comparison
• Migration

• Create a static Drupal 7 site with the Quant module
• How to freeze and take static archive of your old site
• Add Quant Search to your Drupal 7 static site

In Debug Academy's Drupal 10 training course, we integrate our student projects with Pantheon's hosting environment and we use DDEV for local development.

In general, it works smoothly. However, in some instances students who use Windows (and Git Bash) receive an error upon running ddev pull pantheon . This article walks through a quick and easy workaround.

Out of the box, Drupal offers some great tools for content moderation and basic editorial workflows. It is simple and flexible by design because there is no one-size-fits-all solution for every organization and editorial team. Drupal prefers to provide the tools. Your team can figure out how best to use those tools.

Publishing workflows and strategies are complex subjects, but we'll go over the fundamental concepts of how Drupal handles these concepts.

For our first sponsored contribution time, we will be focusing on efforts to improve the usability of Drupal’s administration UI. We chose this because there are some deliverables we beleive we can achieve within six months that will make Drupal better and benefit our existing clients.

There are many good reasons for Drupal-focused organizations to contribute to Drupal, but for Lullabot, it comes down to these:

When Microsoft killed off Internet Explorer in June of 2022, front-end developers breathed a sigh of relief. IE's death meant that the development of lots of exciting features in CSS could now be fully supported across all major browsers (Chrome, Firefox, Safari, Edge) without worrying about IE compatibility.

Keeping a Drupal site up-to-date can be tricky and time consuming. Host Matt Kleve sits down with three people in the Drupal community who have been working to make that process easier and faster.

It's been in progress for awhile, but now you might be able to start using Automatic Updates on your Drupal Site.

In our previous article, we went over the basics of how Drupal handles revisions and content moderation. But one of Drupal's strengths is what we call "structured content" and its ability to implement complex content models, as opposed to a big blob of HTML in a WYSIWYG field. Entities can have lots of different fields. Those fields can refer to other entities that also have lots of other fields. It is easy to establish content relationships.