Insights

Let's be honest: the AI conversation in tech has become exhausting. Every agency claims to be "AI-powered," every platform promises "revolutionary AI features," and somehow everyone's suddenly an AI expert.

Upgrading from Drupal 8 or Drupal 9 to Drupal 11 requires a methodical, step-by-step approach through intermediate versions rather than a direct migration path. This comprehensive guide walks you through the entire upgrade journey, covering critical architectural changes including the CKEditor 5 migration, admin theme transitions from Seven to Claro and potentially GIN, and the Path Alias module introduction. You'll learn how to handle incompatible modules using custom repositories, prepare your codebase by auditing and removing unused dependencies, and modernize your custom code using tools like Upgrade Status and Rector. The article provides practical implementation strategies including using git branches for each upgrade milestone and Makefile automation to ensure repeatable, reliable upgrades. Whether you're starting from an early Drupal 8 version or a recent Drupal 9 release, this guide equips you with the knowledge to navigate version-specific considerations and avoid common pitfalls. For sites with large databases, the guide also covers optimization techniques like creating slimmed-down testing databases to speed up your iteration cycles. With over a decade of Drupal upgrade experience and official Drupal.org partnership credentials, iTech4Web shares battle-tested strategies that have successfully guided dozens of projects through these complex migration paths.

At iTech4Web, we build and maintain complex Drupal websites for media publishers, nonprofits, and enterprise clients. In doing so, we often rely on Drupal’s powerful built-in responsive image handling system to deliver optimized images for different screen sizes and resolutions. But when something goes wrong—like the wrong image style loading, breakpoints behaving unexpectedly, or performance bottlenecks from oversized images—debugging can be a frustrating, time-consuming process.

Technical Debt: How Nonprofits Can Stay Debt-Free and Impactful Technical debt refers to the hidden costs of shortcuts and hasty technology decisions, including outdated software, poor data management, and inadequate security. For nonprofits, ignoring technical debt can severely hinder mission delivery and community impact. To combat this, organizations should prioritize strategic planning, regular code reviews, quality infrastructure investments, and routine maintenance. Embracing automation streamlines donor management, volunteer coordination, and reporting, while AI-powered documentation ensures accuracy and reduces debt accumulation. Staff training, thoughtful scaling through cloud-based solutions, and partnerships with tech experts further strengthen technological resilience. Transparency, accountability, and a culture of continuous improvement are essential for sustainable growth. By proactively addressing technical debt, nonprofits can build robust technological foundations, maximize resources, and ensure long-term effectiveness in fulfilling their missions.

As we approach the extended end-of-life (EOL) deadline for Drupal 7 in January 2025, many organizations are facing pivotal decisions about their digital future. The discontinuation of support for Drupal 7 and PHP 7.4 presents both challenges and opportunities for businesses reliant on this technology. With the digital landscape evolving rapidly, transitioning from Drupal 7 to a more advanced and secure platform is essential for maintaining and enhancing online presence.

Continuous Deployment (CD) is a software development practice in which every change to the code base goes through a pipeline of automated tests, resulting in an automatic deployment on each successful test. This is extremely useful for small teams that want to get features out as fast as possible without having to worry about an entire release cycle.