The What & How of CSS Theming: Common Concerns & Helpful Tools

When CSS was first introduced, it was straightforward. There weren’t any CSS variables, there were no preprocessors. The world was simple, and we were so young! Developers added colors to a site with a hex code (or rgba if they were very lucky and cutting edge!), and those colors were what they were. If a developer wanted to implement a dark and light mode — they often needed to create two completely separate stylesheets and swap the site’s body classes out with JavaScript. Implementing multiple themes on a single site was cumbersome, hefty, and required a lot of additional maintenance.

With the introduction of CSS variables and other color and theme-related CSS features, custom CSS theming has become much easier. When we talk about CSS theming, we’re talking about changing a site based on a user-provided context that lets us still fully control the experience. There is still some element of JavaScript required to swap out the body classes when using a toggle to allow the user to use their preferred theme on your site, but no longer do you have to maintain two separate stylesheets. Native CSS variables make theme swapping much easier than it once was. CSS theming is an excellent way to allow users and developers to dictate website settings easily.

Ways to Use CSS Theming

Dark/Light Mode

Dark and light modes are one awesome, commonplace way to use CSS theming. Users can set their preferred dark or light mode via system settings, browser settings, or even special applications to modify user settings. You can make your entire website respect the user’s settings — which is always nice! 

Branding

Say you’re working on a website that features a few similar products, like breakfast cereals. Each product uses the same overarching information for its brand — just with different colors and fonts. Without rewriting huge swathes of CSS for each different product, you can use CSS theming and perhaps a body class in your HTML to provide totally different branded looks for your products. 

Accessibility

A combination of prefers-contrast or forced-colors media queries with CSS theming can help make your website more accessible. You can make your site look even better and more accessible to users with these preferences.

Common Considerations Introduced by CSS Theming

CSS theming is a valuable tool to have in your developer toolkit, but it does add some complexities you’ll need to consider during implementation.

Respecting User Settings

As mentioned elsewhere, it’s important to respect user settings where possible. It burns the eyes a bit when you’ve got everything set to shades of black (charcoal, onyx, obsidian, jet), and you suddenly land on a page in blinding, brilliant white — or vice versa.

Images

Images are important when theming. Whether it’s an icon where the font color is adjustable, an SVG where the fill color is adjustable, or a regular old JPG, PNG, or WEBP image — you will have to adjust all of the images on your website. A common example is a client logo reel — you’ll have to store two copies (a dark mode compatible and a light mode compatible) in most instances. If you’re lucky enough to have a client logo reel consisting entirely of SVGs, you’ll be able to use CSS to swap the fill. Most of us aren’t so blessed, however. On a site with tons of images — duplication of image files can even become a storage concern if the images are poorly optimized.

Increased QA Time

When you implement CSS theming, the time required to perform quality assurance checks on the work increases. The same pages must be checked multiple times when using dark and light modes. Instructions for swapping dark and light mode must be written so that less-technical QA agents understand the necessary steps and how to perform them. It’s important to bake these increases into the budget and turnaround time when working with CSS theming.

FART

Haha, right? Not so much. The “Flash of inAccurate coloR Theme,” or FART for short, occurs when you have improperly digested your CSS selectors a momentary flash of the incorrect color scheme. For example, say your user prefers to use a dark theme — but your website defaults to a light theme before detecting and swapping to the user-specified preference. FART can be handled in several different ways and is an important consideration when theming. Properly-handled rendering makes your site look that much more polished and awesome.

Tools to Help You Theme

CSS Variables (+ JavaScript)

CSS variables are key to effectively theming with CSS. CSS variables enable you to swap out various CSS properties throughout your custom theme. Variables have been widely supported in modern browsers since approximately 2017, so 2023 is a great (and safe) time to start using them. 

Variables enable flexibility in your theme and stylesheet. They function similarly to preprocessor-based variables, with a slightly different syntax and a key difference: CSS variables can be updated live. Preprocessors compile your variables, so once you’ve set a variable — that’s that; it can’t be updated or changed within the stylesheet. Native CSS variables can be scoped to different CSS classes, and function more like CSS properties.

Some examples of CSS variable syntax:

Declare a variable:

--brand-color: #c4d600

Use a variable:

font-color: var(--brand-color)

It is also possible to scope a variable:

.brand-light {
    --brand-color: #c4d600;
}

.brand-dark {
    --brand-color: #153e35;
}

With a little extra JavaScript toggle magic, the brand-light and brand-dark colors can be added to any part of the page. For a global theme, those brand classes can be added to the html tag or the CSS :root selector. For more specific parts of the page, those classes can be added to individual parts and components.

Media Features & CSS Properties

prefers-color-scheme is a CSS media feature “used to detect if a user has requested light or dark color themes” (MDN). prefers-contrast is similar, used to “detect whether the user has requested the web content to be presented with a lower or higher contrast.” These color scheme preferences work like any standard @media query used to target browsers by screen size — they’re just working off of color and contrast preferences instead of size.

Color scheme is the user setting engaged either in system settings or occasionally the browser settings. This allows you to make your CSS more specific when the user prefers a light or a dark mode, or a high-contrast theme. 

These media features are important for accessibility work, which helps users with low or no sight when browsing your website. When you make your site look even better for these users, you’re going the extra mile in terms of accessibility – always a worthwhile endeavor!

When drilling down to specific elements, the color-scheme property can assist. This property allows an element to indicate which color schemes it can be rendered in. This property is especially useful when styling default form controls; custom form controls such as select or radio buttons can be a bit of a tangle under normal circumstances. The color-scheme property and default form elements make that process slightly less painful.

Theming Specific Libraries, Tools, and Practices

  • https://toggles.dev/ provides some amazing premade animated toggles for light and dark modes. Lightbulbs, suns and moons, and other cute icons galore!
  • Various front-end libraries have implemented theming-specific tools. It’s always a good idea to check out what the big players are implementing. Bootstrap and Tailwind both have some great ideas and inspiration for CSS theming, with the benefit of widespread usage. It’s great when someone else runs into your problem before you do!
  • For testing and QA purposes, you can swap between dark and light modes in various ways. Your computer’s global system settings will allow easy swapping between dark and light modes. However, if you don’t want to go that far — the developer tools in various browsers often also allow you to switch between light and dark modes. Here’s a screenshot showing how to do this in Firefox. 
Firefox interface shows how to switch between light and dark modes.
Firefox interface shows how to switch between light and dark modes.

Summing Up CSS Theming

CSS theming is a new paradigm, with new concerns and considerations. However, there is a lot of power and flexibility that comes along with CSS theming. It’s a worthwhile endeavor to get familiar with CSS theming and the associated new CSS features such as variables, media features, and theming-specific CSS properties. There are plenty of new tools and libraries out there to help you gain fast proficiency with CSS theming.

What You Need to Know about the Drupal 9 to 10 Migration

If you’re current on your Drupal news, you’re probably aware that Drupal 10 was released in December 2022. As a current Drupal 9 user, you may be strategizing your website’s Drupal 9 to 10 migration. 

Luckily, the Drupal 9 to 10 migration is being heralded as the easiest upgrade in Drupal’s history. That’s because Drupal 10 is backward-compatible with Drupal 9, and it’s not a major overhaul of the core system. But the planning and development process will still require time and attention to ensure the migration goes smoothly. 

Let’s take a deep dive into the Drupal migration process and how your organization’s marketing team can provide support along the way. 

Fast Facts about the Drupal 9 to 10 Migration

Brush up on your Drupal release history with these fast facts: 

  • Drupal 9 was released in June 2020. At the time of its release, Drupal 9 offered an easier upgrade than ever before as it built on features released for Drupal 8. 
  • Support for Drupal 9 will end in November 2023. That means after this time, there won’t be many new security releases, and no new functionality will be added. 
  • Drupal 10 was released on December 14, 2022. New features will only be added to Drupal 10 from now on, so if you’re looking to start using Drupal for the first time, it’s recommended to start with Drupal 10
This timeline shows relevant dates related to the Drupal 9 to 10 migration process.

What’s New in Drupal 10?

As mentioned, Drupal 10 builds on innovations released as part of Drupal 9. When switching to Drupal 10, you won’t be confronted with an entirely new structure and system to get used to. 

That being said, Drupal 10 offers the following updated features to improve the user experience:

  • A new default administrative theme and frontend theme. The default Claro administration theme and the Olivero frontend theme offer an accessible, user-friendly, modern experience for website administrators and visitors alike. 
  • Updates to CKEditor from V4 to V5. This change facilitates a more modern editing experience and more intuitive authoring.
  • Upgrade from Symfony 4 to Symfony 6. Symfony 6 and the switch to PHP 8.1 as the minimum version result in a more secure, performant PHP framework.  
  • Modernization of JavaScript. Drupal 10 switches out the large JQuery library with smaller, better-performing solutions.

Drupal 10 is focused on accessibility, modernization, and user-friendliness for website visitors and editors alike.

Steps to Upgrade From Drupal 9 to 10

If you upgraded your site from Drupal 7 to 9 in the past, you know that migration required transferring all of your data to a brand new Drupal 9 website. The Drupal 9 to 10 migration is similar to the upgrade from Drupal 8 to 9, so it won’t be such a significant undertaking. 

However, you can still take a few measures to set your website up for success. Follow these steps to prepare your Drupal 9 site for the migration: 

  • Upgrade to at least Drupal 9.4.4 or later. Core updates made before 9.4 have been eliminated, so you must be on at least Drupal 9.4.4 to use the data upgrade path from CKEditor 4 to CKEditor 5.
  • Run Drupal Rector on custom modules and themes. Drupal Rector scans code to look for deprecated functions and helps guide developers to upgrade them.
  • Upgrade to CKEditor 5. CKEditor 4 will reach its end-of-life at the end of 2023. Check out Drupal’s step-by-step instructions for upgrading to CKEditor 5 to stay up to date. 
  • Check your version of PHP. Drupal 10 requires PHP 8.1 or higher. Log into your website’s hosting account and check the settings in your control panel to verify which version of PHP you’re using. 
  • Check your modules and themes. Not all modules and themes from Drupal 9 will be compatible with Drupal 10. If your site uses a module or theme that was removed from Drupal core, download the contributed project version before migrating to Drupal 10.
  • Update to Drupal 10 and test your site. Run automated code tests using tools like Drupal Rector or PHPStan. Also, conduct manual testing to ensure that everything is working as expected. Check your forms, links, page navigation, and other site elements to note any user-experience issues. 

You can either take these steps yourself if you have a web developer on your team, or work with an external Drupal developer. 

Working with a Drupal Development Expert

Although the Drupal 9 to 10 migration is a more straightforward upgrade, it’s still typically recommended to work with a Drupal web developer to help oversee the process. This can ensure a smooth transition and help maintain data integrity and security. 

Look for a Drupal web development firm that offers services such as: 

  • Overseeing the migration process from start to finish 
  • Custom module development depending on your organization’s needs
  • An accessibility-focused approach to ensure your website is usable for all audiences
  • Third-party and custom API integrations to integrate tools like your payment gateway or security portal seamlessly with your Drupal website
  • Mobile responsive design to create a positive mobile user experience
  • Search engine optimization (SEO) recommendations to maintain or enhance your website’s search results rankings
  • Ongoing support to implement module upgrades and security patches as needed and to help with other aspects like content strategy and performance enhancements

If you’re looking for an experienced Drupal partner, Kanopi Studios is a great choice. Our Drupal team members have an average of 11 years of Drupal experience each. We are also a supporting partner to the Drupal Association, a founding sponsor of Discover Drupal, and regular contributors to the Drupal Project.


Upgrading your website from Drupal 9 to 10 shouldn’t be a hassle. With these tips, you can make the already simple process even easier.

Looking for more Drupal tips and resources? Start here: 

The Ultimate Drupal 7 to 10 Migration Guide for Marketers

This post was last updated in June 2023 to align with Drupal 7’s most recent end-of-life date of January 2025.

Kanopi is a certified Drupal migration partner and can help with your migration needs.

The latest version of Drupal, Drupal 10, is now available. As a Drupal 7 user, you may be wondering what this means for your website. 

With Drupal 10’s arrival comes many improvements and changes to the platform. Keeping up with new Drupal releases ensures that your site is secure and that it benefits from the latest advanced functionality. Ultimately, this allows you to serve your website’s audience more effectively. 

As a marketing manager or CMO for your organization, it’s important to understand the steps of the Drupal migration process so you can effectively work with your developer while they upgrade your site. This guide covers what you need to know to prepare for a Drupal 7 to 10 migration. 

FAQs about the Drupal 7 to 10 Migration

Let’s start with a few fast facts and frequently asked questions about Drupal 7 and 10. 

When was Drupal 7 released?

Drupal 7 was released on January 5, 2011. 

How long will Drupal 7 be supported? 

Drupal 7’s end-of-life date is set for January 2025. After this time, Drupal 7 will no longer receive many bug fixes or security patches. By staying on Drupal 7, you could also risk having faulty modules. Plus, you won’t be able to take full advantage of the new features available in Drupal 10. 

When was Drupal 10 released?

Drupal 10 was released on December 14, 2022. 

What new features are included in Drupal 10?

Drupal 10’s updates reflect ongoing efforts to modernize the back-end editing experience and provide a streamlined front-end user experience. Specifically, Drupal 10 offers these upgrades and new features: 

  • New default administrative theme. The Claro administrative theme is modern, mobile-friendly, and optimized for accessibility. 
  • New default frontend theme. The new Olivero front-end theme also prioritizes accessibility and modernity alongside a streamlined and elegant color palette, form builder, and typography. 
  • Upgrade from CKEditor 4 to CKEditor 5. CKEditor 5 facilitates a streamlined author experience with the ability to track editing histories, collaborate in real-time, and easily import content from Word. 
  • More modern JavaScript elements. Drupal 10 swaps large jQuery elements with more performant solutions. 
  • Upgrade from Symfony 4 to 6 and upgrade to PHP 8. This represents a significant improvement to the PHP scripting language. 

When should I switch to Drupal 10? 

You should consider switching to Drupal 10 as soon as possible to take advantage of the updated features. After January 2025, Drupal 7 will no longer be supported, so it’s a good idea to plan your migration before then. 

Steps of the Drupal 7 to 10 Migration

So, what will the Drupal 7 to 10 migration actually look like? It’s recommended to work with a web developer during this stage. This may either be your organization’s internal web developer or a third-party web development firm.

As a marketing professional, you will mainly play a supporting role in the Drupal 10 migration process. You can help ensure that your site’s SEO rankings are maintained, check that your site’s themes and modules are updated regularly, and run regular tests to ensure a high level of performance. The developer will handle the more complex technical aspects of the migration process. 

However, it’s still helpful to understand what exactly goes into a migration and how you can support the development team every step of the way. 

With that in mind, here are the steps you and the developer will take throughout the upgrade process:

1. Audit your Drupal 7 site. 

A site audit allows you to optimize your Drupal website for performance and security as well as identify data and content types to migrate to your new site. 

During an audit, a developer will identify the following elements to prepare them for the migration:  

  • The content types and structure of your current site. In this stage, you’ll define all of the data that will migrate to the new site and eliminate any broken or unnecessary code. 
  • The functionality of the Drupal 7 site that needs to be recreated in your new Drupal 10 site. The developer will note any features that will have to be manually redeveloped. 

2. Identify necessary redirects for content you’re removing from your site to maintain SEO rankings.

Identify top-performing content and determine whether you’ll need to implement a redirect to maintain SEO performance. 

3. Create a backup site copy.

This copy will serve as a migration source and provide a resource for you to reference after your new Drupal 10 site goes live. You can compare your Drupal 10 site to the copy to ensure that everything is in the right place and make adjustments as needed. 

4. Review hosting for technical requirements needed for Drupal 10.

Ensure your website host can support the minimum technical requirement of PHP 8.1. You can also take this time to review your host for performance elements such as speed, security, and reliability. 

In addition, your developer will ensure that your host provides options for development workflows and site testing. This allows you to stage your site and test new elements and features without affecting the live production environment. 

5. Migrate your site’s content. 

Content migration informs the structure of the new site, making it the first step in the migration process. Plan your content strategy by determining which content types you’d like to maintain or alter. Then, your developer will initiate the process of migrating your data to your new Drupal 10 site. 

6. Upgrade your themes and modules.

Modules are foundational elements of your Drupal website that extend its functionality. Your developer will take the following steps to upgrade your modules and themes in Drupal 10: 

  • Replace contributed modules with their modern counterparts.
  • Identify custom modules and code, verify the functionality required in the new site, and rebuild them.
  • Rebuild the theme using the more modern Twig framework.

7. Finalize migration, deploy, and run tests. 

Run both automated and manual tests to check your new site. For example, the Kanopi team uses automated code-checking tools like PHPstan and Drupal Rector. These tools allow you to see if your code is functioning as expected. 

We also recommend performing manual tests that replicate the user experience. Test your forms, links, navigation, and other site elements to catch any issues and correct them before promoting your new site to audience members. 

How a Drupal development expert can help

As mentioned, working with a Drupal developer will make your migration experience smooth and painless. When finding a Drupal development partner to work with, seek experts that can: 

  • Facilitate a smooth migration process, taking care of the technical details and maintaining data integrity. 
  • Prioritize accessibility, ensuring all aspects of your Drupal 10 site comply with the Web Content Accessibility Guidelines (WCAG). 
  • Develop custom modules to ensure that your Drupal website has all the features it needs to serve your audience members effectively. 
  • Craft a search-engine-optimized website that helps your content appeal to search engines and visitors. 
  • Implement third-party integrations such as payment processors, security portals, and other tools your organization uses. 
  • Construct a mobile-responsive theme that ensures your website looks and works great on mobile devices. 
  • Provide ongoing support, updating content, implementing security updates, and managing performance upgrades as needed. 

When searching for the right Drupal partner, it’s helpful to find an organization with experienced developers who contribute to the Drupal project on an ongoing basis. For example, Kanopi Studios offers Drupal development services for all types of organizations, including nonprofits, corporations, healthcare organizations, and higher education institutions. 

Each of our Kanopi team members has an average of 11 years of Drupal development experience and several of them are Acquia-certified. We also are a supporting partner to the Drupal Association and regularly contribute to the Drupal Project.


By following these steps and providing your developer with context and insight into your website strategy, you can make the Drupal 7 to 10 migration a simple, painless process. Contact the Kanopi team today if you’re ready to launch the migration process. 

Looking for more Drupal development and migration resources? Check out these Drupal guides:

Drupal 7 End of Life: A Guide to Next Steps

This post was last updated in June 2023 to align with Drupal 7’s most recent end-of-life date of January 2025.

Kanopi is a certified Drupal migration partner and can help with your migration needs.

Launched a decade ago, Drupal 7 (D7) has allowed many organizations to create awesome websites powered by over 11,000 contributed modules, 600 themes, and 200 distributions. 

But as they say, all good things must come to an end. According to a recent Drupal PSA, Drupal 7 will reach its end of life in January 2025, and its farewell leaves many organizations considering their next steps.

D7’s end-of-life (EOL) was originally planned for November 2023, but with the impact of COVID-19 on so many website owners and their budgets, the maintainers of Drupal decided to extend the timeline to 2023. Now, a final extension has been made, pushing the timeline again by two years.

Even with this extension, the impending EOL date has a lot of organizations that are dependent on Drupal 7 weighing their options. These organizations can either:

  • Stay on D7 using a long-term support provider 
  • Upgrade to Drupal 10
  • Switch to a new CMS

Every website and organization is different. There’s no catch-all answer when it comes to deciding when and how to upgrade your Drupal system. However, it’s highly recommended that organizations still using Drupal 7 consider moving to Drupal 10. This gives you the greatest access to new features and functionality to ensure your website is at the top of its game. 

In this blog post, we’ll outline the pros and cons of each option and describe the process of switching to Drupal 10. 

Drupal 7 End of Life: Frequently Asked Questions

This image shows the Drupal 7 end-of-life timeline and the Drupal 10 release date.

What does Drupal end of life mean?

When a piece of software reaches its end-of-life date, it will no longer receive bug fixes or security updates from the Drupal community and security team. This also includes the modules that are used, as well!

How long will Drupal 7 be supported?

Previously, Drupal 7’s end-of-life was scheduled for November 2023. In June of 2023, Drupal extended the deadline to January 5, 2025. Even though the deadline has been extended, the Drupal Security Team will adjust the level of support provided

Is Drupal 7 still supported?

Yes. Drupal 7 will still be supported until January 5, 2025. And even though this version is a decade-old, end of life does not mean the end of your site. 

Once the community stops supporting Drupal 7 after EOL, a group of approved and vetted vendors can continue to provide security updates for Drupal 7 core and certain contrib modules under the Drupal 7 Vendor Extended Support program.

What is the difference between Drupal 7, Drupal 8, and Drupal 9?

Currently, Drupal 7, 9, and 10 are supported.

Drupal 8 added a complete rework of the underlying architecture and a new set of powerful features, making it an extreme rework from Drupal 7.

This is important to note, as the transition from D8 to D9 or 10 is not as big of a leap as the transition from D7 to 8. Because D9 is the next step in the evolution after D8, it can actually be updated as part of a global Drupal release cycle rather than needing to be a large website overhaul. In comparison, the D7 to D9 or 10 transition requires more work.

When did Drupal 9 launch?

Drupal 9 was released on June 3, 2020, alongside Drupal 8.9, a long-term support (LTS) minor release of Drupal 8. Check out Drupal’s official site for the release cycle overview with more details

With Drupal 9’s launch, organizations gained access to the following features:

  • Easy author editing with a WYSIWYG editor 
  • Smart language translation
  • Responsive to touchscreens, tablets, and mobile readers
  • Improved Compliance
  • Universal configuration storage

When was Drupal 10 released? 

Drupal released D10 in December 2022. Drupal 10 is billed as a “refined version of Drupal 9.” Upgrading from Drupal 9 to 10 is intended to be a similarly smooth process as the upgrade from Drupal 8 to 9. 

What do you need to do to prepare to get out of Drupal 7?

If you’re ready to transition away from Drupal 7, you’ll need to ensure your team is aligned and ready to take on the next steps. To prepare for an upgrade, you should:

  • Conduct technical mapping. When picking new modules or new features, keep in mind that you’re planning for the future. Do you have a clear update path for when you upgrade to D10 (and beyond)? Check out Kanopi’s Drupal 7 to 10 migration guide for a full sequence of steps to follow. 
  • Conduct a content audit. No matter which option you take, it’s a good idea to start a content audit to determine what should stay and what should go. This is especially true when it comes time to migrate to a new site. 
  • Identify stakeholders. You’ll likely have several members of your team involved in the steps needed to update your site. Make note of who will be responsible for what, and how you’ll start the process. 
  • Determine your budget. Whether you migrate to D10 or move to an entirely new CMS, you’ll need to set a realistic budget to ensure you can complete the project.

Drupal 7 End of Life Options

To upgrade or not to upgrade. That is the question…

The path after Drupal 7 is not a one-size-fits-all process. However, there’s one choice you can rule out completely: moving to Drupal 9. It isn’t worth it to transition to D9 since its EOL is later this year. 

Nevertheless, you do have several other paths to choose from regarding the next steps to take. Here are the options to consider:

1. Continue using Drupal 7

Your website won’t cease to exist after Drupal 7’s EOL date, so you can still remain on the system for an extended period. This choice is recommended for organizations that need a bit more time to gather the resources and budget needed to switch to D10 or a new CMS.

Pros

  • Thanks to its open-source code, Drupal 7 has tons of great modules.
  • There’s ample support from other professionals in the D7 community.
  • Drupal 7 community developers have been working on it for a long time (nearly a decade!) so they’re very familiar with the code.
  • Drupal 7 is still highly secure.

Cons

  • There won’t be many security fixes. 
  • Your modules and integrations may stop working.
  • You may miss out on innovative new features.

2. Upgrade from Drupal 7 to 10

For organizations that are ready to upgrade their site and take advantage of new functionality and security features, migrating to Drupal 10 is the way to go.

Pros

  • The powerful migrate module has many tools to help developers migrate even the most complex Drupal 7 website to Drupal 10.
  • If you’re already considering a website redesign, you can start fresh on Drupal 10, and have time to plan.

Cons

  • It could be costly, depending on the complexity of your site. An upgrade to Drupal 10 from Drupal 7 will require a developer to create a migration, meaning a brand new website needs to be built in Drupal 10. All content from your current Drupal 7 will be migrated to the new site or rebuilt.

3. Move to an entirely new CMS

This option only makes sense if you have the funds to carry out an extreme rebuild. But, if your site is very simple (for example, a blog) that doesn’t require a lot of features or functionality, moving your legacy Drupal 7 to a CMS like WordPress can be a very cost-effective solution.

Pros

  • Moving to a new CMS can be a cost and time-effective solution if your site is simple.
  • You can use the transition as an opportunity to launch a full brand refresh.

Cons

  • If your site is more advanced, it can be costly and time-consuming to rebuild it on an entirely new platform.

To help decide which path to take, consider your organization’s:

  • Budget: If your D7 site is complex, do you have the funds needed to upgrade to D10 or move to a new CMS? 
  • Time constraints: Does your team have enough time on its plate to devote to a website rebuild? Will you have more or less free time in the coming months? 
  • Goals: Do you want to expand your website in the future to drive more conversions? Are you interested in modernizing your website or updating your brand? 

If you’re not ready to decide at this exact moment, there’s no rush. Some agencies and providers can keep your D7 website updates and move you to Drupal 7 long-term support.

You’ll have to rebuild eventually. But, by choosing a support package, you can take the time you need to make a strategic decision, as well as buy some time to allow funds to free up. 

Kanopi’s Drupal 7 End of Life and Support Package

We at Kanopi are here to help Drupal 7 users until you’re ready to make the jump. We offer solutions for organizations who decide to stay on Drupal 7 past its EOL as well as those ready to transition to Drupal 10. 

For those who decide to remain on Drupal 7 for the time being, there is some good news. When D7 reaches its end of life, Drupal users will not see any immediate difference from the front-end perspective. And, neither will your site visitors! In the back-end of your Drupal site, the platform and modules will begin to display as “Unsupported”, but everything else will essentially continue to work as it had previously.

By choosing a Kanopi as your long-term support provider, we patch and maximize the value of your Drupal 7 investment for as long as possible—with the lowest level of financial investment until you are ready to move to D10. 

Our Drupal 7 support services include:

  • A continuous improvement approach: Instead of large structural changes, we work on small incremental changes that support your budget. Our services include module and plugin upgrades, bug fixes and security patches, updating content types/views, and more.
  • A website growth plan: In addition to keeping your D7 site supported beyond EOL, we also work closely with you to future proof your site. We create a roadmap for exactly how you can increase conversions for your organization using your website
  • Support and security: Kanopi currently supports 150+ Drupal 7 domains. We work to keep their sites healthy until they’re ready for an upgrade.

If you’re interested in learning more about our D7 support plans, contact the Kanopi team here. We can work with you to figure out the best path forward depending on your goals. 

Transition to Drupal 10 with Kanopi

For most organizations, transitioning to Drupal 10 is the recommended path to getting the most value out of your website. Making the switch allows you to stay ahead of the curve and ensure your website takes advantage of the security tools and advanced features of D10. 

Upgrading your Drupal site from D7 to D10 is a more involved process than traditional upgrades because you’ll have to transfer all of your data to a new Drupal 10 site. 

Kanopi’s Drupal 7 to 10 migration guide describes the steps you need to follow to upgrade your site, including:

  1. Audit your Drupal 7 site. Review all types of site functionality in this audit, including your modules, content types, paragraphs, etc. This can help you determine where you stand currently and if you should conduct any maintenance before upgrading your site.
  2. Identify necessary redirects to keep your SEO rankings. Identify top-performing content and determine whether you’ll need to implement a redirect to maintain SEO performance. 
  3. Create a backup site copy. This will serve as a migration source to ensure everything is in the right place. 
  4. Review hosting for technical requirements. Ensure your website host can support the minimum technical requirement of PHP 8.1. Also, review your host for performance elements such as speed, security, and reliability. 
  5. Migrate your site’s content. Determine which content types you’d like to maintain or alter, then let your developer initiate the migration. 
  6. Upgrade your themes and modules. Choose the right theme for your organization, add in your custom features, and organize your content.
  7. Finalize migration, deploy, and run tests.. Identify any issues or areas for improvement and test your site until you get it right. 

Review the rest of the complete guide for in-depth tips on the common considerations and challenges organizations face when upgrading their Drupal 7 sites to Drupal 10. 

Making the Most of Your Site Upgrade

If you decide to make the leap to Drupal 10, congratulations! This is an exciting moment in your web design journey. 

However, you may feel apprehensive ahead of the migration process. Of course, you want your new site to be successful in driving conversions and engaging audience members, and you don’t want to lose any vital data along the way. 

Make the most of your site upgrade by:

  • Using this opportunity to launch a full brand refresh, if desired. You’re already creating a new website for your organization. Why not use this opportunity to refresh your brand? Consider the elements of your brand that could use updating, such as your logo, color palette, fonts, or imagery. Incorporate these fresh elements as you update your site to Drupal 10. 
  • Upgrading your site in multiple ways, including accessibility and user experience. Does your website incorporate the latest accessibility guidance? How about user experience best practices? As you craft your Drupal 10 site, keep in mind how you can optimize your site for accessibility and usability. For example, can you simplify your navigation menu? Can you increase text contrast to assist people with visual impairments? 
  • Taking advantage of Drupal 10’s innovative tools. D10’s innovative workflow tools, new media management system, and new layout builder make the platform much more user-friendly. Take advantage of these to give your website the design elements and innovative features that you always wanted to offer. 
  • Testing your new site every step of the way to check for issues or roadblocks. Conduct frequent tests to determine if everything is working as it should. This way, you can identify roadblocks and address them before they become detrimental to your ability to connect with audience members. 
  • Reaching out to web design professionals for help. If you feel overwhelmed by the task ahead of you when it comes to updating your Drupal site, don’t panic. Website development professionals like our team at Kanopi can help ensure your upgrade runs smoothly and you’re making the most of Drupal 10’s advanced features. 

These tips will help you make the most of your upgrade and move into the future with a more well-rounded, advanced website. 

How Kanopi has Helped D7 Clients

Kanopi offers a variety of website growth plans, allowing you to choose the path that best suits your needs and goals. These plans range from a Drupal 7 transition plan to technical SEO strategies and fully customized plans. 

If you’re ready to start the migration process, we’re happy to help. Our web design professionals at Kanopi are experts in Drupal planning and development. Each of our team members has, on average, 11 years of experience in Drupal Development, and several of them are Acquia-certified. We also are a supporting partner to the Drupal Association, regularly contribute to the Drupal Project, and are one of the main organizers of BADCamp.

Using Gutenberg to Elevate the WordPress Editing Experience

“Gutenberg” is the name given to the movable block editor adopted by WordPress back in 2018, harkening back to Johannes Gutenberg who invented one of the early European movable-type printing presses. Reusable individual letters that could be moved, and reused, eventually lead to typography and fonts as we know them.

Of course, nowadays we have printing technology that Johannes could not have even imagined, let alone believe that an entire online editing experience would be named after him. 

But what exactly is Gutenberg?

Most of us are familiar with editing experiences, such as typing in an email, Microsoft Word, or Google Docs. These experiences are mostly similar; you have a blank space to type and buttons for alignment, styles, fonts, sizes, etc. This has been a common website editing interface for decades, but it is both creatively and logistically restricting. 

If you wanted to move a section from one location to another, you’d have to copy and paste it, then delete the original. Trying to completely rearrange your content would be frustrating and time consuming. Or if you wanted some snappy responsive columns, you would have to switch to view the document code and write HTML and CSS. 

Gutenberg is WordPress’s native “drag and drop” site builder. It solves those problems by allowing you to create your content in blocks designed for the specific content you’re using. There are over 90 blocks to choose from. You can play around with all of these options on the Gutenberg demo.

This flexibility allows content editors to populate their website with more complex content, and then shuffle it around within the layout. In fact, there are many themes that lean so heavily on Gutenberg that you wouldn’t need a developer at all. With the introduction of Full Site Editing, nearly anyone could put together a working website that’s beautiful too.

Why use a web developer at all?

While there are many themes that do leverage everything Gutenberg has to offer (those 90+ blocks), that’s not the case for most of them. And for existing sites with legacy themes, there is little chance that they are able to take advantage of this newer technology. Out-of-the-box websites are useful and serve a purpose but when you need custom design, structure, and functionality, you need to call in professionals.

Another struggle with drag-and-drop sites is the global element. If you have 30 headings on your website and decide you want to change them all from green to blue, you’d need to go through and edit the color settings on all 30 headings one by one. While there are some global elements, the vast majority of your page content will require manual editing. This can be incredibly time-consuming.

Native Gutenberg blocks can be unexpectedly limiting. For example, if you desire rounded borders on all media but the block you’re using doesn’t have support for a border-radius, you’d need a developer to create and apply custom classes. Keep going down that path and suddenly you can have a site full of custom classes and blocks that never look the same from one to another. This can be an editing nightmare and require excess documentation to keep it all straight. Suddenly that easy drag-and-drop editing experience requires a higher level of skill.

There’s a better way to customize.

Kanopi approaches Gutenberg blocks from the perspective of creating consistent and branded content. One of the big advantages of Gutenberg is that we can create new blocks and apply our own styles and structure. This allows us to create blocks that can hold and display any type of content within a defined set of rules. Instead of pouring budget into styling 90+ blocks (and their hundreds of combinations) that may never be needed, our team focuses on creating custom content solutions for our clients.

This “best of both worlds” approach lets site editors continue to use the ease of Gutenberg’s drag-and-drop experience, while also creating consistent, branded content. As a website moves from its initial build into support, these blocks can be expanded upon and updated globally (and thoughtfully). Even older sites without any Gutenberg usage can be configured to allow for this type of block expansion without disrupting the existing content.

Gutenberg is here to stay.

It’s clear that WordPress is leaning in on the use of Gutenberg and the Full Site Editing implemented in the past year. Meanwhile, Advanced Custom Fields Pro (the preferred and recommended plugin for enhancing WordPress’s content management) is keeping pace to ensure custom block creation works seamlessly with every stride made. Whether using an out of the box theme, or having an agency custom building according to your organization’s needs, Gutenberg is a phenomenal solution with room to grow in many directions.

Contact us to discuss how Gutenberg can work for you

The Top WordPress & Drupal Trends for 2023

A new year means a new look at what’s on the horizon. Kanopi is always looking ahead to what is happening in the development space, so we asked our team to give their thoughts on what’s ahead for next year.

We’ve split this into three sections: 

  • The top WordPress trends for 2023
  • The top Drupal trends for 2023
  • The top website development trends (regardless of CMS) for 2023

Let’s start with WordPress …

Top WordPress trends for 2023

New WordPress, new theme, same direction

With the release of WordPress 6.1, Twenty Twenty-Three has already arrived; the new default theme is called (numerically incremented, as usual) Twenty Twenty-Three (TT3). What hasn’t changed is the focus on Full Site Editing (FSE). In fact, TT3 continues with the trend of moving towards FSE. Block patterns are prevalent and variations are implemented theme-wide to allow for a huge variety of customizations (10 theme style variations!) without having to touch any code whatsoever.

What else is new in WordPress 6.1

WordPress 6.1 released on November 2nd with many improvements with much of the focus placed on accessibility and performance. Both of these areas were Identified by developers and the community (after heavy criticism) as needing more love as the Gutenberg block editor received the lion’s share of updates in recent releases.

Happily, many needed improvements and fixes were implemented in this release. Below are links to comprehensive lists of the updates, including:

Need more of a beginner’s guide? This blog post is a great resource

  • Agencies are figuring out how to stay on top of the changes with Gutenberg, building Block themes, and Full site editing. 
  • Block Patterns will continue to be used and will become ubiquitous across any block-based theme.

Top Drupal trends for 2023

Drupal continues its rapid development pace, adding more secure and performant code releasing Drupal 10 on the backbone of Symfony 6 and PHP 8.1.

Upgrading from Drupal 9 to Drupal 10 is easy using the drupal-rector tool, which looks for deprecated code. There are also a large number of contributed modules that already have been ported. So if you’re on D9, moving to D10 should be easy.

Drupal 10 features include:

  • The new, modern Claro administration theme, which provides a better administration experience.
  • Olivero default theme, which is the new default front-end theme for Drupal with a modernized look and feel
  • CKEditor 5 which provides a much better authoring experience and more modern editing.
  • Modern JavaScript components to replace some uses of jQuery for better performance.
  • Theme Starterkit tools for bespoke theme creation.

But as the Drupal crew is ever working hard to keep evolving, the work has already begun to be included in Drupal 11. The following core initiatives are being worked on in the contrib community, and will be merged into core when they are ready:

  • Project Browser: this will allow ambitious site builders to discover and install modules and theme from their admin screens.
  • Drupal Recipes: allows site builders to install and configure groups of modules to achieve features such as an event section, or a blog.
  • Automated Updates in Core.
  • A more streamlined Core: the Great Module Migration continues moving lesser used modules from core to the contrib community for a smaller Drupal core.

General website trends

Performance and Speed

As we wrote in a blog post about Core Web Vitals earlier this year, research shows the chance of a bounce increases by 32% when a page load time takes one to three seconds, and by 90% when the page load time takes up to five seconds. Speed matters! Make sure to take a look at your Core Web Vitals. 

Accessibility

This is a drum that Kanopi beats frequently, but that’s because it’s really that critical. 26% of US adults identify as being permanently disabled in some way. If you count those with temporary disabilities like a broken wrist, or situational disabilities like being on a noisy subway, the number climbs considerably. That’s a huge percentage of people that feel alienated when a site isn’t accessible to them. There are many ways to make a site accessible, including adding captions and alt text to images and videos, ensuring proper contrast, and entering content with a correct heading structure. Make 2023 the year you decide to make your site as accessible as possible. 

Thumb-Friendly Mobile Navigation

In 2022, 60% of all website traffic came via mobile devices, so a mobile-first approach is imperative. This also means that all critical elements on a website must be within easy reach of a user’s thumbs, including the navigation. Think about what’s really necessary on each page and what can get edited. Focus on a vertical orientation rather than a landscape one, and what functions need to be done on your site with a touchscreen. 

Artificial Intelligence (AI and Machine Learning (ML)

2023 should be the year when companies will move forward with implementing both of these, if they haven’t already (and our Creative team sees this trend on the design and content side as well). On top of improving productivity and using data more efficiently, AI doesn’t have to prove its usefulness anymore. Plus, it’s become quite accessible to work with as most cloud platforms offer it as a plug-and-play service. 

AI enables machines to learn from their experiences and make decisions without human intervention. This technology can be used to automate mundane tasks such as data entry or content generation, allowing developers to spend more time focusing on more complex problems. For example, there are plugins that can help you create better content for your website by using artificial intelligence. 

ML is also being used in web development, enabling sites to better understand user intent and behavior so they can deliver personalized experiences tailored just for them. For example, think about how chatbots can deliver a personalized experience with your audiences.

Speaking of …

Personalization

It’s impossible to talk about future website trends without discussing personalization. The days of one-size-fits-all websites are quickly coming to an end as organizations look for ways to tailor their websites to individual users’ needs, wants, and interests. Consider that Gen Z has grown up with some degree of personalization and expects it, and apps such as Spotify and Netflix have already conditioned us to expect some personalized recommendations on what we hear and watch. (Personalization is also critical in content strategy and web design for 2023.)

While it initially felt uncomfortable or intrusive when platforms knew personal things about us, it’s now become a more mainstream experience that helps users get what they want or need faster. 

A few examples:

  • Geolocation: location services can help your audiences find events local to them.
  • Product recommendation: a great example of online shopping is Patagonia. After filling out a questionnaire about sizing, the site predicts what size would be best on every single product page. The algorithm bases itself on the information a user shares but also the reviews it receives from similar users who made the purchase.
  • Personalized newsletter: This is tangential to your website, but why ignore this critical marketing tool that leads readers to your website? It’s become a common practice to send a newsletter with content specific to your audience’s needs (and there’s lots of data to back up the power of personalized newsletters). Split up your newsletters by audience so you are speaking to their goals, then direct them to the content on your website so they do the conversions you want. 

Voice Interfaces & Voice Search Optimization 

Voice interfaces are becoming increasingly popular as more people turn to voice assistants such as Siri or Alexa for help with their online searches. To stay ahead of the curve, web developers need to start optimizing their sites for voice search by ensuring that all content is written in conversational language and utilizing structured data markup tools like Schema.org or Google’s Structured Data Markup Helper tool. This will ensure that your content is easily readable by search engines so that it shows up when people search via voice assistants.  

Small bites can create big wins.

With these new developments come exciting opportunities for organizations looking to stay ahead of the competition. While some of these trends might not seem achievable or even necessary for your organization to implement at a large scale, even implementing some in smaller ways can garner big results. CMOs and marketing managers should keep an eye on these emerging trends so they can capitalize on them before their competitors do!

And as always, if you need any help with your websites in 2023, Kanopi is here to assist. Contact us anytime

Drupal 10 is (almost) here!

Drupal 10 will bring with it some significant changes that could potentially affect your website. As such, it’s important to be prepared and take the necessary steps to ensure a smooth transition. There are some major benefits to upgrading to Drupal 10, including improved security, performance, and accessibility. And, because Drupal 10 uses the same overall structure as Drupal 9, the transition shouldn’t be too difficult for most developers. 

But what does this mean for CMOs and marketing managers who are using or considering using Drupal?  Let’s review what you need to do to get ready for Drupal 10 and make sure your website is up to date.

What’s New in Drupal 10?

Drupal 10 includes several major new features and improvements, including:

  • A new default administration theme called Claro that is mobile-responsive and optimized for accessibility, replacing D7 which was over 10 years old.
  • A new default frontend theme called Olivero that replaces Bartik.
  • Initial upgrades to CKEditor from version 4 to version 5, introducing more modern content editing functionality and a better author experience.
  • Ongoing modernization of the JavaScript stack, replacing the large jQuery library with smaller, more performant solutions 
  • Leveraging our technology partner’s improvements and upgrading from Symfony 4 to Symfony 6 and making the minimum version of PHP 8.1 to keep the whole stack secure and more performant.

These changes will be welcome additions that improve the overall experience for both users and administrators. 

Preparing for the Upgrade 

If you’re currently on Drupal 7 (as almost 54% of Drupal sites still are), you have some time as end of life is scheduled for November 2023. But it is recommended to upgrade to 9 as soon as possible; by upgrading, you ensure your website stays updated with the latest features and security measures. Our guide to transitioning from Drupal 7 to 9 provides additional insight into this process, or you can go straight to D10.

If you’re currently on Drupal 8, it’s time to upgrade asap. D8 was end of life in November 2021, and most Drupal sites have upgraded. You need to as well.

If you’re currently using Drupal 9, congrats! Because Drupal 10 uses the same overall structure as Drupal 9, the transition shouldn’t be too difficult for most developers. But here are a few steps to consider: 

1) Check Your Version of PHP

One of the first things you’ll need to do is check what version of PHP your website is running on. As of Drupal 10, the minimum supported version of PHP will be 8.1. You can check your website’s PHP version by logging into your hosting account and checking the settings in your control panel. If you’re not sure how to do this, contact your hosting provider for assistance.

2) Update Your Modules and Themes

It’s important to make sure that all of the modules and themes on your website are up to date. While many modules and themes are already compatible with Drupal 10, there may be some that aren’t. Checking for updates is easy enough: head over to the “Updates” page in your Drupal admin panel and install any available updates. Once you’ve done this, it’s a good idea to clear your website’s cache so that the changes can take effect.

3) Test, Test, Test

Once you’ve updated your website for Drupal 10, it’s important to test everything thoroughly before taking your site live. The Kanopi support team uses tools like PHPstan and Drupal Rector to perform automated code checks to verify your codebase works as expected on the upgraded versions on PHP, Symfony, and Drupal.

We also recommend manually testing.  This includes testing all forms, pages, links, etc. to ensure that they’re working as intended. It’s always better to catch any potential problems before they cause issues for your live website visitors.

You have time to upgrade.  

While December is fast-approaching, upgrading to Drupal 10 is a decision that should be made on a case-by-case basis. If your website or application is already running smoothly on Drupal 9 (or earlier), there may not be enough incentive to justify the time and expense to do this immediately. However, if you’re starting from scratch or looking for an excuse to make a big change, migrating to Drupal 10 could be the perfect opportunity. 


And if you need assistance, Kanopi is here to help as always.

The Ultimate Guide to Drupal Planning and Development

This post was last updated in June 2023 to align with Drupal 7’s most recent end-of-life date of January 2025.

Kanopi is a certified Drupal migration partner and can help with your migration needs.

Drupal is an open-source software content management system (CMS) that powers over 1 million websites globally. As a Drupal user, you were probably drawn to the platform because of its scalability and flexibility. You also know your site requires continual planning and updates to remain an informative, engaging online presence. 

To make sure your website continues to excel, you’ll also need to stay up-to-date with the latest changes in the Drupal world. Drupal launched its latest version—D10—in December 2022. In addition to this update, Drupal extended Drupal 7’s life to January 2025.

Now is a good time to review how these changes will impact your CMS planning. We’ve crafted this Drupal planning and development guide to help you prepare for migrations and preserve your website well into the future. Let’s get started by looking at some frequently asked questions from Drupal users regarding planning and development. 

Drupal Planning and Development FAQs

What is the difference between WordPress and Drupal? 

Both Drupal and WordPress are user-friendly, open-source platforms used to build powerful, comprehensive websites. Generally speaking, WordPress is known for its relatively simple admin user experience with many ready-made themes to choose from. By contrast, Drupal is often used by organizations looking to build complex sites, integrate with other services, and receive ongoing support from an agency or in-house developers. 

If you’re looking to switch systems or are adopting a robust CMS for the first time, compare each platform’s features to determine which one better suits your needs. Kanopi’s Drupal vs. WordPress guide can help steer your decision-making. 

I see Drupal 10 is the latest version. Should I upgrade to Drupal 10? 

Upgrading your website to Drupal 10 all depends on your current codebase and whether you have the resources and time needed to manage a migration. An audit of your existing Drupal site can help you decide if D10 is the right choice for you. 

Kanopi can help you work out the best migration path. We’ll take a deep dive into your Drupal planning and development roadmap later on in this post

How often should I make security and module updates in Drupal?

Review Drupal core security updates and contributed modules as they are released and apply them with expedience based on their Security Risk level. The higher the level, the more risk the vulnerability is to the site.

Non-security module updates are best done monthly or quarterly depending on time available or budget. Keeping your code up to date with the latest releases helps make future site upgrades easier, takes advantage of bug fixes, and can add additional functionality.

How can I get started building my Drupal planning and development strategy?

If you’re unsure where to begin with your Drupal planning, consider partnering with a Drupal development specialist. We’ve compiled a list of key support tasks you should expect to receive from an agency offering to assist you with your Drupal planning. They should:

  1. Work with you to create a Drupal strategy roadmap.
  2. Get familiar with your organization and your budget.
  3. Define the best way to curate existing content to maximize conversions.
  4. Provide module support.
  5. Offer Drupal training.

We’ll highlight additional ways a Drupal specialist can help optimize your website later on in this post

Where can I find Drupal talent? 

Drupal.org is a great place to start if you’re looking for Drupal talent. Kanopi also has a friendly team of Drupal experts ready to help you strategize your Drupal planning and development. Each of our Drupal experts has an average of 11 years of experience in Drupal development. 

Where can I find more Drupal development tools and resources?

Kanopi’s resource library can help you learn more about Drupal, stay up to date on release updates, and craft your development strategy. Drupal also has a dedicated Slack channel for users. Other resources include:

Preparing Your Drupal Planning and Development Roadmap

Have you reviewed your website users’ needs recently? What about your site’s usability, accessibility, and content quality? 

User needs change over time. That’s why it’s essential to have the most up-to-date picture of your users’ unique needs and take steps to determine whether your website content meets those demands. 

If you’re brainstorming your Drupal roadmap, we suggest carefully considering the following: 

These are the elements of a Drupal planning and development roadmap, outlined in the text below.
  • Undertaking user experience (UX) research. Use your website analytics and traffic patterns to determine how effectively different website aspects engage visitors. For instance, does your nonprofit’s online donation form have a high conversion rate? Can visitors easily find your business’s contact information and event calendar? Test site elements such as load speed, mobile-friendliness, and accessibility. 
  • Streamlining your user decision journey. The user decision journey is the steps your audience members take to learn about your organization and determine whether they want to engage with you further. This might involve purchasing one of your products or services, donating to your cause, or signing up to become a member of your group. Assess whether your website streamlines the user journey by asking questions about how visitors are likely to engage with your site. Do you have a variety of calls to action throughout the site that encourage visitors to get more involved? 
  • Fine-tuning your user personas. Is your website reaching the right people? Creating in-depth audience profiles allows you to understand your audience’s needs, goals, and interests and design your website content accordingly. Reassess your user personas to determine whether your audience has changed. Use the information in your customer or constituent relationship management system to assess your audience’s demographics, purchasing habits, and other distinctive characteristics. 

By assessing the UX and appealing to your user personas, you can deal with blockages in your customers’ decision journey and create a more valuable website experience. You can also identify any sweet spots where your site currently excels that could be built upon ahead of your site migration. 

Planning Pathways for Drupal Users

Your upgrade and maintenance process will look different depending on what version of Drupal you’re currently using. In this section, we’ll explore the various options available to Drupal users who intend to stay on the Drupal system.

These are the different Drupal planning pathways for users that want to continue using Drupal.

Exploring Drupal 10

As mentioned, Drupal 10 was released on December 14, 2022. This release date was pushed back from June 2022 to give the development community time to improve the CKEditor 5 migration path. The previous iteration, CKEditor 4, will reach its end-of-life at the end of 2023, so the CKEditor 5 is a complete rewrite. 

The December release date allowed Drupal 10 to be released alongside Symfony 6.2 and PHP 8.2 to ensure users have access to the most robust, efficient code base available. 

If you’re thinking about transitioning your Drupal site to D10, Drupal’s Project Lead Dries Buytaert has emphasized that the transition from Drupal 9 to 10 will be the easiest migration in Drupal’s history. Drupal 10 is not a complete system overhaul, and it’s backward-compatible with Drupal 9. Buytaert explains how it will work

“New functionality for Drupal 10 is actually added to Drupal 9 releases. This means module developers can start adopting any new APIs right away. 

Along the way, we deprecate old functionality but keep backwards compatibility. Once we are ready to release Drupal 10, we remove all deprecated code. 

Removing deprecated code breaks backwards compatibility, but because module developers had a chance to stay up to date with API changes, the upgrade to Drupal 10 should be easy.”

So, how can you prepare for D10? No matter what Drupal version you’re currently using, we’ve got a planning and development roadmap for you. 

Drupal Planning: 7 to 10

Drupal 7’s end-of-life date was adjusted to November 2023 because of the COVID-19 pandemic’s impact on many organizations’ budgets, meaning that this version will actually last longer than D8. Therefore, many D7 users have decided to stick with this version to give themselves more time to prepare for an eventual transition to a later version. 

Although you can remain on D7 for a while longer, now is a great time to transition to D10. You can ensure your website is fully prepared for the eventual release of D10 and even plan a website redesign if your site needs one. 

Your D7 to D10 migration roadmap should include the following tasks:

  • Make a plan for content that can be retired from your site before moving to Drupal 10.
  • Map out how redirects will be handled for any content that you are removing from the current site to ensure your SEO isn’t negatively affected.
  • Review the modules you use in Drupal 7 and investigate the upgrade path needed for those modules to be compatible with Drupal 10.
  • For modules that aren’t available for Drupal 10, identify and recommend alternative modules, tools, or third-party services.
  • Look at content types on the site and determine if anything needs to be changed or combined to meet your users’ needs and/or make the site easier to maintain. 

It’s recommended to switch to D10 before D7 reaches its end-of-life so you can continue benefiting from security team updates and fixes.

Sticking with Drupal 7

Your organization might want to stick with D7 for the time being to give yourself more time to gather the resources and funding needed to make the transition to D10. 

Here are a few benefits of sticking with D7:

  • Access to a large number of Drupal modules thanks to the open-source community
  • Support from an entire community of Drupal professionals and developers
  • Community developers who have been working with D7 for 11 years.

Use this time before you transition to a newer version of Drupal to prepare your website for the eventual switch. Keep your site healthy by implementing security updates as soon as possible. Audit your content to ensure it reflects your organization’s mission and appeals to your audience. If you have any outdated or extraneous content, remove it now so that you can launch your eventual website migration with only your strongest content. 

Drupal Planning: 8 to 10

There’s good news and bad news for Drupal 8 users. Let’s start with the bad news: D8 reached its end-of-life in November 2021. Drupal 8 is no longer supported and no more bug fixes or improvements will be released, so if your site is currently running on D8, it’s more vulnerable to cyber-attacks and other security threats. 

Here’s the good news: if you’re planning to migrate from D8 to 10, you are looking at a very simple, streamlined migration process.

Your Drupal development partners can create a roadmap with these elements:

  • Look for any deprecated code in your D8 code base that may need to be updated for D10.
  • Make sure that the modules you use in Drupal 8 are compatible with Drupal 10, or have a target date for compatibility.
  • Ensure that the site’s configuration files are tidy so that it’s easy to export/import configuration during the upgrade.

Migrating your D8 site to D10 as soon as possible will put you in a good position to maintain your site’s security and functionality.

Drupal 9 Users

If you’re currently using D9, you’re in a great position to migrate to D10. Keep in mind that support for Drupal 9 will end in November 2023 as you make your development plan. 

You can prepare for D10 by staying up-to-date with bug fixes and other security updates. If you have custom code on your site, keep an eye out for deprecation notices as well, and update that code regularly to remove them. Consider working with a web development consultant to help you stay on top of all updates. For instance, the Kanopi team offers website support services for all Drupal users. This includes:

  • Module and plugin updates
  • Bug fixes and security patches
  • Performance enhancements
  • Development modifications

Read on for a deeper look inside Kanopi’s Drupal development and support offerings. 

Exploring Kanopi’s Drupal Planning and Development Services

Kanopi can support your Drupal site until it’s ready for an upgrade, even if that means going beyond the end-of-life date of your current operating version. Instead of large structural changes, we recommend focusing on incremental changes that can be delivered with a potentially fluctuating budget, such as:

  • Improved navigation
  • Revised content strategy
  • New content curation
  • Accessibility support
  • Search engine optimization (SEO)

We can also provide a website growth plan for you, which typically includes: 

  • How to increase website conversions for your organization
  • Customization based on your unique situation
  • A breathing window to maintain your site ahead of a migration (if your site is operating on D7)

Along with our Drupal 7 maintenance package, we also have options for Drupal 8 and 9 users to help create a game plan or launch into a migration. 

Looking for more information to learn more about Drupal planning and development? These additional Kanopi resources can help:

Accessibility Overlays: Buyer Beware

Whether it’s the Americans with Disabilities Act (ADA) and Section 508, the Accessible Canada Act, or the governing legislation in your area, the reality is your site has to be compliant with WCAG 2.1 Level AA guidelines or risk legal ramifications.

What is website accessibility, also known as A11y? Accessibility is “the quality of being able to be reached,” or, basically the idea that every part of your website can be accessed and used by anyone. So how do you achieve that? Well, on one hand you can spend the time, effort, and money having your website audited and remediated, then set up an ongoing process to ensure your site stays current with accessibility needs and requirements. Or you can install an accessibility overlay and call it a day.

The question is, do you feel lucky?

First, what is an accessibility overlay?

Accessibility overlays (including widgets and toolbars) are automated software solutions that serve third-party scripts intended to resolve accessibility problems on websites and applications. 

Firstly, they usually apply a series of controls to a website that allow the user to adjust aspects of their viewing experience, such as colors, text size, and contrast.

Secondly, they use JavaScript to alter the code and content of your website on the fly to try and make up for existing accessibility errors with automated “repairs.”

Thirdly, they are really, really, really, really, really, really bad.

Wait, what? Why are accessibility overlays so bad?

Overlays may run into conflicts with user privacy.

Because users of assistive technologies often have specific settings on their devices and browsers, some overlays automatically detect those settings and attempt to utilize them for their configuration. To maintain this, it stores a cookie on the user’s machine, saving info about their disability settings without any kind of opt-in from the user. 

To make matters worse, any other website using the same overlay can access that same cookie to apply the same configuration. Information about an individual’s disability is incredibly personal, and this is essentially a privacy breach the user never opted into. Having an accessibility overlay on your site could risk noncompliance with GDPR, CCPA, and the like.

They increase your site’s security risk.

Anytime you load a third-party script onto your site, you are putting part of your site’s safety in the hands of the vendor. If their server is insecure, then you could be directly impacted.

Your website performance will suffer.

This is a tale as old as time; the longer it takes for your site to load, the more likely it is that the user is going to leave. JavaScript always increases page load, and third-party scripts are even worse because it’s the vendor’s server dictating the speed of that script. It’s a known fact that Google and other high priority search engines monitor site speed and that metric is utilized in your SEO ranking. Slowing down your site with an accessibility overlay will directly impact your search ranking with Google.

Website creators may become reliant on them.

Overlays are insufficient bandaids to problems that designers and developers will continue to make if they are not required to solve them. This gives the team a false sense of security and no motivation to create inclusive, accessible websites.

The “repairs” made by overlays may not be reflected in the source code. 

If you were to “view source” on a webpage, what’s reflected there may not match up with what you see being delivered by the overlay JavaScript. This means anyone using assistive technologies that rely on the source code would not be served the accessibility changes.

Overlays may be blocked by the intended audience.

Extensions designed to block ads are known to also block overlays, but ad blockers are a common tool users employ to ensure their assistive technologies are working properly. Instead those users will be served your existing inaccessible website without the overlay.

They actually create barriers to accessibility.

This is the big one. Most users of assistive technologies agree that overlays are ineffective at best, and detrimental at worst. These widgets often require activation via buttons or toolbars which of themselves may not be accessible to the user. Remember, not everyone is using their eyes and a mouse to navigate the page. Just because you can see and click on them doesn’t mean everyone can.

Moreover, users requiring assistive technologies already have solutions which impact the experience across their entire device and web browsers. An overlay can override or conflict with these settings, or even adapt unreliably (if at all), creating a frustrating experience for the user.

Companies using accessibility overlays are subject to brand damage.

Yeah. They are regarded that badly by the A11y community and those who use assistive technology. Companies caught using overlays have been called out for it on social media, and it is not a good look. The general feeling is that those organizations care more about their legal obligations than the actual end user.

  1. They require no actual accessibility knowledge or expertise.
  2. They provide controls that seem very helpful, like color contrast and text size.
  3. They promise fast and easy accessibility compliance.

It’s that last one that draws in companies and organizations looking to meet regulations. Accessibility overlays look like a temptingly cheap and quick fix for a big, expensive problem.

But accessibility overlays do fix accessibility problems, right?

No. A thousand times, no. 

There is currently no way for a single automated tool to detect all accessibility issues on a website. This is widely known in the A11y community. When we do accessibility audits at Kanopi, we use a minimum of four different automated tools, in addition to manually testing via keyboard and screen reader. Most automated tools can only detect up to 30% of potential problems, leaving up to 70% undetected. It takes a human user with training, additional tools, and a good chunk of time to find the remaining items. How then could an overlay possibly identify all accessibility issues on a webpage?

Unfortunately, they can’t. And therefore, they cannot meet the WCAG 2.1 Success Criteria. Conformance is defined as meeting all of the requirements of the standard; partial compliance is not sufficient. Any accessibility overlay provider claiming conformance is misrepresenting their product.

Just a few examples of issues an overlay is not going to be able to address, but are basic A11y requirements:

  • Detect / repair missing headings, or misused headings
  • Fill in missing alt text with appropriate content
  • Add missing labels on form fields or submit buttons
  • Fix missing or incorrect error management and handling
  • Provide reliable focus control on form inputs
  • Provide reliable keyboard access
  • Correct JavaScript content injected independently of the overlay
  • Enable zoom
  • Correct the usage of layout tables
  • Reliably correct focus order
  • Prevent keyboard traps

There’s more, but these are areas that are known to be big problems for users of assistive technologies and can make your site completely unusable for part of your audience.

What’s the worst that could happen?

In 2020, more than 250 lawsuits were filed against companies using overlays to solve accessibility issues on their sites. In fact, around 70% of accessibility cases are brought by the same ten law firms who are actively seeking websites using overlays. These law firms specialize in accessibility lawsuits and are looking for easy targets

Hunt Huey (PLLC) confirms this is a known strategy, stating: “The law firms who file website accessibility lawsuits and their pet clients start the process of finding a target using automated tools that scan for compliance with the technical requirements of the Web Content Accessibility Guidelines 2.0 or 2.1.”

“The conclusion is simple. If avoiding litigation is your goal, an overlay or widget won’t do the trick.” 

Hunt Huey

The reality is, if you want to avoid legal action then you need to reach WCAG 2.1 Level AA compliance.

So, back to the original question: Do you feel lucky? 

How do you become compliant?

It takes time, it takes expertise, it takes commitment. It takes caring about real people who use assistive technologies. Folks with disabilities are worthy of respect and inclusion. Design and build your website with inclusion and accessibility in mind, so that your site can be ‘reached’ by all. Dedicate resources to ongoing automated and manual A11y audits of your site, addressing issues at the root of the problem instead of applying bandaids.

Kanopi can help. If you’d like to know more about our A11y audits, or our dedication to building Level AA websites, get in touch with us.

Why do we need to make accessible websites?

Because it’s the right thing to do. 

Forget the legal ramifications. Forget the fact that there’s a strong business case for it. Consider for a moment the ethical responsibility to ensure your site is barrier free to anyone regardless of who they are. Consider that your clients and customers are people to respect, not problems to solve.

It’s time to make your website accessible.