Of course, there’s not a simple answer to the WordPress vs. Drupal question. Many have a strong bias towards one content management system or the other, but often, staunch opinions on the subject are based on a few cursory facts or outdated information.
ARM is not a new processor architecture. Virtually every smartphone today has one inside and has since the earliest days of iOS and Android. In fact, ARM goes all the way back to 1983, when transgender woman Sophie Wilson began designing the instruction set for the Acorn RISC Machine. Despite its long history, however, it’s never been considered a serious contender for workstations or desktop machines where x86 reigns supreme. Even in the data center, ARM is a comparative newcomer, with few cloud providers supporting it.
While experimenting with Gatsby + Drupal and doing research for my previous posts here, I came across the GraphQL Twig module.
This module is beta and hasn’t had a lot of activity. I’m not sure how it addresses some deep Drupal theme issues, but it presents an interesting idea:
“The GraphQL Twig module allows you to inject data into Twig templates by simply adding a GraphQL query. No site building or pre-processing necessary.”
At their most simple, both Drupal and WordPress are open source PHP based Content Management Systems (CMS) which have evolved from simple beginnings to great prominence. In the early days of the “CMS wars” many web agencies positioned themselves on different sides of the question “which CMS is best?”
These are decoupled-only (or headless) back-ends. The only way to present your content is to create an application that consumes the API, interprets it, and renders the content in your desired format.
What’s new in Drupal 9.1.0?
The first feature release of Drupal 9 includes the new experimental Olivero frontend theme and various additions to the Claro administration theme. Installer performance is improved 20% and full Composer 2 and PHP 8 support is available. Images with known dimensions are set to lazy-load by default to improve frontend performance.
New experimental Olivero theme
A new beta experimental frontend theme has been added to Drupal core called Olivero. This is a new modern and clear theme that is planned to become the new default Drupal theme later (replacing Bartik). Subtheming Olivero is currently not supported, but formal support may be included in the future.
The theme is named after Rachel Olivero (1982-2019). She was the head of the organizational technology group at the National Federation of the Blind, a well-known accessibility expert, a Drupal community contributor, and a friend to many.
Key additions to the Claro theme
The experimental Claro administration theme introduces designs for various key pages: the extensions administration page, views administration, status report and media library received Claro styled designs.
Composer 2 and PHP 8 support
Drupal 9.1 is fully compatible with Composer 2. If you are using Composer 1, now would be a great time to update. Most plugins used on Drupal sites are compatible and/or obsolete with the new version. The memory and performance requirements reduced dramatically, which should improve your experience.
PHP 8 is also supported in Drupal 9.1, including all of Drupal’s dependencies. There may be contributed projects that are not fully compatible though. Drupal 9 is still compatible with PHP 7.3 and older. There are various exciting new features in PHP 8, but the JIT compiler and performance improvements are not likely to affect Drupal. Drupal 10 is planned to require PHP 8 in 2022. It is worth examining the support timelines of PHP versions to schedule your platform updates.
Installer performance is improved 20%, so getting a new Drupal site set up will be faster.
Images rendered by Drupal with known dimensions will be set to lazy-load automatically. This means browsers will only load them when they should appear in the viewport of the user, improving the user experience by making content appear faster.
Drupal 10 is planned for mid-2022. While Drupal 9 keeps requiring Symfony 4, Drupal 9.1 includes adjustments required to support Symfony 5 already.
What does this mean for me?
Drupal 8 site owners
Update at least to 8.9.x to continue receiving bug fixes until the end of life of Drupal 8 in November 2021. The next bug-fix release (8.9.11) is scheduled for January 6, 2021. (See the release schedule overview for more information.) As of this release, sites on Drupal 8.8 will no longer receive security coverage.
We suggest that you update from Drupal 8 to Drupal 9 though. Updating is supported directly from 8.8.x and 8.9.x. Of the top 1000 most used drupal.org projects, 85% are updated for Drupal 9, so there is a high likeliness that most of the modules and themes you rely on are compatible.
Drupal 7 site owners
Drupal 7 support was extended to November 28, 2022, and will continue to receive bug and security fixes throughout this time. From November 2022 until at least November 2025, the Drupal 7 Vendor Extended Support program will be offered by vendors.
On the other hand, the migration path for Drupal 7 sites to Drupal 9 is stable. Read more about the migration to Drupal 9.
Translation, module, and theme contributors
Minor releases like Drupal 9.1.0 include backwards-compatible API additions for developers as well as new features.
Since minor releases are backwards-compatible, modules, themes, and translations that supported Drupal 9.0.x and earlier will be compatible with 9.1.x as well. However, the new version does include some changes to strings, user interfaces, internal APIs and API deprecations. This means that some small updates may be required for your translations, modules, and themes. Read the 9.1.0 release notes for a full list of changes that may affect your modules and themes.
This release has advanced the Drupal project significantly and represents the efforts of hundreds of volunteers and contributors from various organizations. Thank you to everyone who contributed to Drupal 9.1.0!
Removing the Webform module’s dependency on jQueryUI
The most noticeable change in Drupal 9 and Webform 6.x is most jQuery UI asset libraries are deprecated and moved to contrib modules. The Webform module was using the jQueryUI’s Tabs, Tooltip, and Date picker plugins. Although I considered keeping the requirement of these plugins using Drupal’s corresponding jQueryUI modules, after some nudging from the Drupal community, I decided to replace the jQueryUI Tabs and Tooltip and make the jQueryUI Date picker an optional dependency.
The jQuery UI Tabs plugin was replaced with Tabby, a lightweight, accessible vanilla JS toggle tabs library. Since tabs only appear within the Webform module’s admin UI, I felt that Tabby was the most straightforward solution without having the Webform module provide its own tabs implementation.
Below is a screenshot of Tabby in the Webform module’s user interface.