After a shorter than expected time in the core issue queue the HTMX integration in now usable in Drupal Core, Let's see how we can use it!
HTMX has a respectable pool of examples to choose from, today we'll focus on forms. How can we make an equivalent of the cascading select HTMX example in Drupal?
theodore September 13, 2025
Article body
TL;DR: After a job rejection for lacking hands-on experience with specific tools, I decided to test my learning approach with Kubernetes. Built an enterprise-grade platform in 17 hours over 6 days using my "black box" learning method. Results included production infrastructure with monitoring, real applications, security patterns, and a community module contribution. The key: focus on solving immediate problems while implementing professional patterns from day one.
About a month ago, I was turned down for a role at Confluent. The reason? No hands-on experience with their tools. Fair enough. But it got me thinking about something I've been doing for decades: can I still learn complex technology stacks quickly using my "black box" approach?
I decided to find out. I picked Kubernetes - something I'd never practiced before - and gave myself a simple challenge: demonstrate that systematic learning beats months of theoretical study.
Six days and 17 hours of focused learning later, I had an enterprise-grade Kubernetes platform running real applications with monitoring. The module contribution came after that, taking additional time to properly research and build. Here's how the black box methodology made it possible.
Instead of trying to master everything at once, I focus only on what solves my immediate problem. I know other parts exist, but I don't let them distract me until I need to "open that box."
Think about learning Drupal development. I started with CSS for the longest time because it solved everything I needed. When a more complex problem presented itself, I knew my next step was to open templates. When I needed something more, I knew preprocess functions existed, but I chose not to get distracted by them until needed.
Same thing happened at Acquia. I never looked hard at Site Factory until my customer bought it. Then I attended the 2-day seminar and became an internally recognized subject matter expert.
The key is strategic focus: know what exists, but only dive deep into what solves your immediate problem. Everything else stays closed until needed.
Rather than diving into theoretical concepts, I approached each day with a specific problem to solve. The progression shows how systematic learning works in practice.
Day 1 (3.5 hours): Foundation and Tool Selection Started by mapping Kubernetes concepts to familiar web hosting architecture. Research with Claude as a partner, followed by basic implementation: kubectl, Kind, simple cluster. Key decision: chose HAProxy for Ingress because friends work there and I knew I could get help. Installed better tools (Helm, Freelens) based on research. Real learning meant real infrastructure, so I reinstalled an old laptop with Ubuntu.
Day 2 (3.5 hours): Professional Patterns from Day One Each solved problem revealed what to learn next. Built proper team separation using Kustomize with base configurations plus development/production overlays. No toy examples. Professional deployment patterns with Infrastructure as Code from the start. This is where 30 years of infrastructure experience accelerated learning. I knew the organizational problems even if I didn't know these specific tools.
Day 3 (3 hours 40 minutes): Production Infrastructure External access via MetalLB for bare metal LoadBalancer services. Took a detour looking at HAProxy replacement, but discovered commercial licensing requirements. Practical decision-making: chose appropriate tools for the situation. Implemented NFS shared storage for persistent content across multiple pods. Result: production-ready infrastructure with external access.
Days 4-6 (9+ hours): Real Applications and Enterprise Monitoring Deployed Drupal 11 with multi-container architecture, external database integration, and proper networking. Here's where black box discipline showed its value: I started planning Kafka integration for user events, then realized I was opening too many boxes at once. Stepped back to build monitoring foundation first (RBAC, Prometheus, Grafana). Enterprise patterns: authentication, security, observability with persistent storage.
Key Learning Principles That Emerged:
Professional implementation from day one. No learning with toys, everything built for production use.
Sequential problem solving. Each solution enabled the next logical challenge.
Strategic stepping back. Recognize proper sequencing instead of jumping to exciting features.
Experience acceleration. Map new concepts to existing knowledge (30 years Linux experience).
Research partnerships. Accelerate implementation without getting stuck in documentation rabbit holes.
After completing the enterprise platform, I was ready to implement that Kafka integration I'd planned. But when I researched how to send events from Drupal to Kafka, I discovered a problem: there was no integration between ECA (Event-Condition-Action) and Kafka message streaming.
I could have worked around it with custom solutions, but that seemed like missing the point. If I needed this, other people probably did too. This is where the black box approach revealed something unexpected: sometimes learning leads to contributing.
Using systematic development methodology with Claude, I built the ECA Kafka Integration module. The module bridges ECA with Apache Kafka, enabling automated message publishing based on Drupal events. It essentially turns Drupal into a smart Kafka producer for any site activity.
At this point, I considered the exercise complete. The platform was enterprise-ready, and I'd contributed something valuable to the community.
Time Efficiency: 17 hours total resulted in enterprise platform with monitoring plus community contribution. Companies need people who can build systematically without over-engineering.
Rapid Adaptation: The ability to acquire hands-on experience quickly might matter more than existing experience with specific tools. Each solved problem revealed exactly what to learn next, with no wasted time on concepts not yet needed.
Professional Standards: Infrastructure as Code, security patterns, team separation from day one. No learning with toy examples - everything built for production use from the start.
Problem-Solving Methodology: Systematic building where each solution enabled the next challenge. Black box discipline meant recognizing when to step back and build proper foundations before jumping to exciting features.
Community Engagement: Moving from consumer to contributor. Learning led to identifying and filling a genuine gap in the Drupal ecosystem.
This isn't just about personal learning. It's about what companies actually need: the ability to adapt quickly to new tools without months of study, the capacity to build professional solutions while learning the technology, and the judgment to know when to step back and build proper foundations.
The Confluent rejection that started this journey highlighted something important: hands-on experience matters, but the ability to acquire that experience rapidly might matter more.
Six days later, I had enterprise Kubernetes experience and had contributed something valuable to the community I care about. The black box approach didn't just help me learn Kubernetes - it led me to make Kubernetes work better with the tools I already knew.
Each solved problem reveals exactly what you need to learn next, not what you think you need to learn. No wasted time on concepts you don't need yet. No getting overwhelmed by the scope of what you don't know.
Companies need people who build systematically without over-engineering. This systematic approach works for any technology stack.
The work isn't finished. There are more black boxes to open, more problems to solve, and more ways to contribute to the communities and technologies that matter.
What's your approach to learning complex tech? Do you plan everything upfront, or do you solve problems as you go?
The complete Kubernetes learning platform code is available on GitHub, and the ECA Kafka Integration module can be found on Drupal.org.
Author Carlos Ospina Abstract After a job rejection for lacking hands-on experience with specific tools, I demonstrated that systematic "black box" learning methodology can produce enterprise-grade results. Built complete Kubernetes platform with monitoring, security, and real applications in 17 hours over 6 days, leading to community contribution. Tags Drupal Drupal Planet Career Development Professional Growth Best practices Devops Development Contribution kubernetes rapid-learning Rating Select ratingGive From Job Rejection to Enterprise Kubernetes Platform in 6 Days 1/5Give From Job Rejection to Enterprise Kubernetes Platform in 6 Days 2/5Give From Job Rejection to Enterprise Kubernetes Platform in 6 Days 3/5Give From Job Rejection to Enterprise Kubernetes Platform in 6 Days 4/5Give From Job Rejection to Enterprise Kubernetes Platform in 6 Days 5/5Cancel rating No votes yet Leave this field blank
In this episode, we are joined by special guests Mike Herchel and Andy Giles, founders of Dripyard. Dripyard is a premium Drupal theme designed to reduce the cost of ownership and enhance the developer experience for modern Drupal projects. Mike and Andy share insights into their motivation behind launching Dripyard, the detailed work that goes into creating accessible, high-quality themes, and how their themes will integrate with upcoming Drupal features like Canvas. We also discuss the module of the week, Content First, and a crucial public service announcement about a supply chain attack impacting NPM tools.
For show notes visit: https://www.talkingDrupal.com/520
Topicswith Martin Anderson-Clutz - mandclu.com mandclu
Content First - The Content First module provides a simple tool for viewing the plain text content of any node without design, media, or layout distractions. It helps content teams, editors, and designers focus on what matters most: the content itself.
Whether you're drafting, reviewing, or rethinking your site’s messaging, this module supports a true “content-first” approach by giving you a clean, layout-free version of your page.
ResourcesDripyard Supply Side Attack - Also this link grep -r --binary-files=text _0x112fa81 to diagnose if you’ve been impacted Should I Use a Carousel?
GuestsMike Herchel mherchel Andy Giles andyg5000 dripyard.com
HostsJohn Picozzi - epam.com johnpicozzi Martin Anderson-Clutz - mandclu.com mandclu James Sansbury - tugboatqa.com q0rban
The Early Bird registration is now open for the largest Drupal event in North America, DrupalCon Chicago 2026, happening March 23–26, 2026 in Chicago, Illinois. Don’t miss your chance to connect, learn, and celebrate with the global Drupal community.
For a limited time, secure your DrupalCon Chicago registration for just $575—the lowest price available!
Learn more and register now to get your ticket at the lowest price!
Don’t miss your chance to connect, learn, and celebrate with the global Drupal community.
When you buy a conference ticket, you’ll get access to:
View the program at a glance now.
Make the most of your DrupalCon experience by staying at the Hilton Chicago, the official DrupalCon hotel.
DrupalCon is more than just sessions. The real magic happens in hallway track conversations, late-night discussions, and spontaneous coffee meetups. Book the conference hotel to stay close to it all.
Book your room at Hilton Chicago!!
The Drupal Association is dedicated to creating an event that is welcoming and inclusive to everyone. The Call for Speakers for DrupalCon Chicago 2026 submission deadline is almost here!
Submitters may edit their submissions until 26 September 2025, 11:59 pm Central Time.
We’re thrilled to introduce Glenn Hilton, one of the newest members elected to the Drupal Association Board, with her term beginning 1 November 2025.
Glenn is the Founder and CEO of ImageX, a Drupal agency that he established in 2001. Over more than two decades of leadership, Glenn has combined creativity with community to guide both his company and his career. His passion for open source and collaboration has made him an active participant in the Drupal community for more than ten years.
Beyond his role as CEO, Glenn is deeply committed to building strong teams and helping people reach their full potential. He believes that lasting success comes from relationships and from creating environments where individuals and communities can thrive.
We are thrilled to have Glenn bring this perspective to the Board. Here are his thoughts as he begins this new chapter:
What are you most excited about when it comes to joining the Drupal Association Board?
I'm excited to help shape the business strategy that ensures the long-term sustainability of the Drupal ecosystem. It is a unique opportunity to bridge the gap between agencies, contributors, and end clients while keeping Drupal both innovative and commercially viable.
What do you hope to accomplish during your time on the board?
I want to strengthen feedback loops with agencies and enterprise users so that we have stronger data to help us better understand and support the needs of those investing in Drupal. I also hope to help expand Drupal’s reach by improving how we communicate its value and create new paths for commercial growth.
What specific skill or perspective do you contribute to the board?
As CEO of a long-standing Drupal agency, I bring a business-first perspective rooted in delivery, growth strategy, and client expectations. With more than 20 years in leadership, I focus on scalable teams, efficient operations, and long-term partnerships.
How has Drupal impacted your life or career?
Drupal changed the trajectory of my agency and gave me a career grounded in purpose, global collaboration, and community. It is more than a platform, it is a values-driven ecosystem where even competitors work together with integrity and a shared mission.
Tell us something that the Drupal community might not know about you.
Outside of work, I am a real estate and architecture enthusiast and probably spend too much time analyzing floor plans. I have four amazing kids, one grandchild, a wonderful wife, and a deep passion for my faith in Jesus Christ.
Share a favorite quote or piece of advice that has inspired you.
“Leadership is not about being in charge. It is about taking care of those in your charge.” — Simon Sinek
We look forward to the contributions Glenn will make during her time on the Drupal Association Board. Thank you, Glenn, for sharing your time and expertise with the Drupal community. You can connect with Glenn on LinkedIn.
The Drupal Association Board of Directors comprises 13 members with nine nominated for staggered three-year terms, two elected by Drupal Association members, and one seat is reserved for the Drupal Project Founder, Dries Buytaert. One seat is reserved for the immediate past chair as a non-voting member. All Board terms start on 1 November of each year.
The Board meets twice in person for weekend retreat and about 5 times virtually each year. The Board provides strategic guidance to the Drupal Association and oversight of the Association’s management, policy development, management, budget, and fundraising efforts.