Drupal Upgrade or Rebuild: Choosing the Right Path

I'm going to say something that will upset a few Drupal agencies. Most Drupal websites don't need a custom theme. "We need a fully custom design. From scratch. Built to our brand." I've heard this 100 times this year. Here's what they don't tell you: A custom Drupal theme costs $8,000–$25,000 to build. Takes 6–10 weeks. And in 18 months, nobody on your team knows how to update it. A well-configured base theme — Olivero, Gin, or a contrib starter — costs a fraction of that. Looks just as good. Your team can actually maintain it. Custom themes make sense when: → You're a national brand with strict design guidelines → You have a dedicated frontend team → Your UX requirements are genuinely unique For everyone else — you're paying for complexity you don't need. The best Drupal site isn't the most custom one. It's the one your team can actually own two years from now. Agree or disagree? Drop it below. 👇 #Drupal #DrupalDevelopment #WebDevelopment #DrupalTheme #CMS

Most website owners don't know something is wrong until users start complaining. • Emails stop sending. • Cron quietly dies. • Errors pile up in a file nobody opens. • The status check says everything is fine. After years of working with HashiCorp Vault at scale (European Commission, Scotiabank, Dun & Bradstreet, and others), I kept seeing the same pattern in WordPress and Drupal environments. The difference is that most WordPress and Drupal sites don't have the same level of observability that enterprise platforms do. That's why I decided to build 𝐋𝐨𝐠𝐲𝐬𝐭𝐞𝐫𝐚. Logystera reads the activity already coming out of your site and tells you when behavior changes, along with the evidence that triggered the alert. Over the last few weeks, a small group of early users has been helping test the platform and shape the product. I'm now opening the next batch and looking for a few more WordPress or Drupal site owners, agencies, or administrators who would like to participate. I'm not selling anything. I want honest feedback on installation, dashboards, alerts, weekly reports, and whether the insights are actually useful in practice. If you manage WordPress or Drupal sites and want to try it, send me a message. If you know someone who'd benefit, tag them or share this post. That's the fastest way for it to reach the right people.

A lot of people still think Drupal development has to feel slow, clunky, and painful. It doesn’t. Back in December, Blue Drop Labs partnered with Portland Webworks to deliver a new Drupal 11 platform for a state agency in Illinois. PWW led the design. Our team handled the implementation. This project was a great example of what modern Drupal development can look like when the architecture is done right. We built the bespoke theme using: - Drupal's Single Directory Components - Storybook - TailwindCSS - Paragraphs - Modern frontend workflows - AI-assisted development using the Figma MCP server Because the component architecture was clean and structured, our frontend team was able to move incredibly fast while maintaining consistency across the platform. Storybook also gave us a huge advantage during QA and stakeholder reviews. Instead of waiting for fully assembled pages, teams could review and refine components in real time while development was still happening. That feedback loop dramatically accelerated delivery. We also leveraged Drupal Paragraphs to give content editors flexible page-building capabilities while keeping everything aligned to a governed design system. That balance matters. Editors get flexibility. Organizations get governance. Developers get scalability. Everybody wins. We’re incredibly proud of the work our team delivered and grateful for our long-term partnership with the talented folks at Portland Webworks. Modern Drupal done correctly is still one of the best enterprise CMS solutions available today.

Managing multiple websites? Discover how #Drupal10 helps organizations centralize content, reduce maintenance costs, and deploy scalable enterprise platforms faster. 📖 Read our latest blog post: https://lnkd.in/eSQSEqzd 🎓 Want to become a Drupal expert? Our upcoming Drupal training will help developers and companies master: ✅ Drupal development ✅ Multisite architecture ✅ Security & performance ✅ Enterprise CMS best practices 📩 Contact us today to join the training (sales@qtatech.com) or discuss your Drupal project. https://lnkd.in/gaWerrAF #Drupal #Drupal10 #WebDevelopment #CMS #Multisite #OpenSource #TechTraining #DigitalTransformation

Drupal Doesn't Suck. The algorithm has guided me into a bit of an opinion-sharing mood. I've seen a few posts about mis-understanding what Drupal does or is capable of. I also want to shout it from the rooftop that Drupal is way better than people give it credit for. I'll try to stay away from the reasons I think people ignorantly tarnish the reputation. Drupal can be built to be as simple or as complicated as you want. If you want the 'backend' to look and feel like Wordpress, that can in fact be done. (Why? I'm not sure). Drupal can score 100's on the ever-elusive Lighthouse/Page Speed Insights scores. It really can. Drupal has a powerful commerce platform that can literally be made to handle a super small shop, or a million user subscription site. Drupal can be the backend to an app of any sort. Drupal can be lightweight and handle the data for restaurant menus, street signs, news tickers, and so much more. Drupal is secure. (as secure as the developer wants it to be). The Drupal community is based around open-source, and an overall 'sharing' mentality. Sans a few out there that try to monetize their own modules, most every Drupal module has been vetted and scrutinized by a plethora of developers. (Some of which will dig deeper into your code than even your code understands). Sure, there are situations where a security issue has been found, but the fixes come quick and the transparency is unmatched. Drupal may be intimidating, but so is riding a motorcycle or swimming in open water. You'll be ok if you just take a breath and not panic. Yes, those 'vibe-coded' whatever-you-call-them are great too... but don't knock one of the OGs unless you've lived and breathed it for at least one paycheck worth of time. #drupal #drupaldoesntsuck #drupalrocks #vibecodingisforthebirds

⚡ Drupal 11 Performance Showdown: Preprocess Hooks vs Views 🚀 Which approach delivers better speed, cleaner rendering, and improved website performance in Drupal 11? This blog explores the real difference between Preprocess Hooks and Views, helping developers choose the right solution for scalable and high-performing Drupal websites. If you’re working on Drupal optimization, theming, or performance tuning, this one is worth reading 👇 Read the blog here - https://bit.ly/4wLIoLM #Drupal11 #DrupalDevelopment #WebPerformance #Drupal #PHP #WebsiteOptimization #OpenSource #WebDev #DrupalPerformance

Most complex Drupal projects don't fail because of the technology. They fail because of the agency. Specifically: an agency that rushed to development without blueprinting architecture first. A team that delivered something nobody internally can manage. A scoping process that missed integration dependencies entirely and only discovered them mid-sprint. And in 2026, the stakes of getting this wrong are higher than they have ever been. Drupal 7 is end-of-life. Drupal 11 requires modern architectural thinking. The agency you choose right now shapes your platform for the next decade. Here's what enterprise and institutional web teams consistently get wrong when evaluating Drupal agencies: 🔴 Checking headcount instead of senior architect depth on the actual project team 🔴 Reviewing a portfolio without asking what went wrong and how it was fixed 🔴 Skipping post-launch support conversations entirely during procurement 🔴 Treating discovery as a billable formality instead of a risk reduction mechanism A Drupal build qualifies as complex when it involves any of these: 💡 Decoupled or headless architecture with React, Next.js, or Vue 💡 Multisite deployment across multiple domains from a single Drupal instance 💡 Deep enterprise integrations: Salesforce, SAP, Marketo, custom APIs 💡 Large-scale content migration of 5,000+ nodes from legacy CMS platforms 💡 Federal or institutional compliance: FISMA, WCAG 2.1 AA, HIPAA 💡 High-traffic performance architecture requiring CDN strategy and load testing If your project touches even one of these, you need a different conversation with a different set of agencies. We evaluated the 12 best Drupal development agencies in North America for complex web projects: ✅ BinaryWorks ✅ Phase2 Technology ✅ Bounteous ✅ Third and Grove (TAG) ✅ Forum One ✅ Kanopi Studios ✅ Urban Insight ✅ Portland Webworks ✅ Eastern Standard ✅ Electric Citizen ✅ Kalamuna ✅ Redfin Solutions Each evaluated on architectural depth, Drupal Association membership, Acquia certification depth on actual project teams, complex project delivery track record, and structured post-launch support. Not agency marketing claims. Actual delivery criteria. If your organization is beginning a complex Drupal initiative in 2026, picking the right agency at the start costs nothing. Picking the wrong one and fixing it halfway through costs everything. Full breakdown in the comments. 👇 #Drupal #DrupalDevelopment #CMS #EnterpriseWeb #WebStrategy #Drupal11 #DigitalTransformation

More about HTMX and Drupal! This is now 5 articles on using HTMX and Drupal, so I might take a little break on HTMX posts for a bit.

Drupal 11: Node Display Mode Preview Form This is part five of a series of articles looking at HTMX in Drupal. In this article we will look at creating a simple form that allows users to enter a node ID and a view mode and see the node rendered in that view mode. The article is a detailed look at how the HTMX is used to generate this effect in Drupal. https://lnkd.in/e6cC7y3c #drupal #drupal11 #drupalHtmx

Your Drupal site scored fine at launch. That was three years ago. Since then: more modules installed. Content volumes tripled. Third-party scripts stacked up. Cache configurations nobody touched since go-live. Now PageSpeed is flagging you. Core Web Vitals are slipping. And nobody can tell you exactly why. Here's the problem with running a PageSpeed report on an enterprise Drupal site. It shows you that performance is degrading. It does not tell you where the bottleneck actually lives. On Drupal, the root cause almost always sits across four layers at once: 📉 Infrastructure and server response time 📉 Application cache misconfiguration 📉 Database query performance under real content volumes 📉 Front-end asset bloat from modules and third-party scripts Fixing one layer while the other three stay broken produces short-lived gains. That's exactly why most Drupal performance fixes don't hold. Here's what the numbers look like when performance optimization is done right: 📈 87% reduction in application response time (london.gov.uk) 📈 3,000% increase in donation capacity under traffic surge (ACLU) 📈 100%+ site performance improvement on a full Drupal 10 rebuild (Museum of Science, Boston) These aren't outliers. They're what structured, four-layer performance audits produce. We evaluated 7 agencies that deliver enterprise Drupal performance optimization at that standard: ✅ BinaryWorks ✅ Tag1 Consulting ✅ Palantir.net ✅ Lullabot ✅ Velir ✅ Chromatic ✅ Eastern Standard Each evaluated on audit depth, caching architecture, database profiling, CDN configuration, and post-launch monitoring, not PageSpeed screenshots. If your Drupal platform has 3+ years of accumulated module debt and a performance score that has been quietly declining, the right first step is a root-cause audit across all four layers. Not a front-end fix. Not a new caching plugin. An audit. Full breakdown in the comments. 👇 #Drupal #CoreWebVitals #WebPerformance #DrupalDevelopment #CMS #DigitalStrategy #PageSpeed