In this episode, Ivan Stegic and Randy Oest discuss the impact of AI on junior developers and other roles, debating whether AI will be a disruptive force in the job market. They delve into the complexities of using LinkedIn for job hunting and effective networking strategies. The conversation shifts to new features in Figma, the potential of AI-driven coding tools like Cursor, and the importance of investing in junior developers. They also explore higher education design systems, innovative business strategies, and reflect on the balance between tactical and digital controls in modern cars. The episode wraps up with a light-hearted chat about slang, parental roles, and mentorship.
For show notes visit: https://www.talkingDrupal.com/cafe004
Topics Ivan StegicIvan is a prominent leader in the Drupal community and the founder of TEN7, a Minneapolis-based technology studio specializing in Drupal development, strategy, and digital transformation. With a background in physics and a passion for problem-solving, Ivan transitioned from science to tech, ultimately finding a perfect fit in the open-source world of Drupal. Since founding TEN7 in 2007, Ivan has championed Drupal as a powerful, scalable platform for mission-driven organizations, nonprofits, and enterprises. Under his leadership, TEN7 has delivered impactful Drupal solutions for clients across education, healthcare, and government sectors. Ivan is also known for fostering a people-first company culture grounded in trust, transparency, and continuous improvement. Beyond his work at TEN7, Ivan is an active contributor to the Drupal project, frequently speaking at DrupalCons and camps, hosting the ONE OF 8 BILLION podcast (formerly the TEN7 Podcast), and mentoring others in the community. His advocacy for open source and ethical tech underscores his commitment to using Drupal to make the internet—and the world—a better place.
Randy OestRandy is a design strategist, creative director, and accessibility advocate helping mission-driven organizations craft inclusive, user-centered digital experiences. With a background that spans visual design, front-end development, and content strategy, Randy specializes in building scalable design systems and digital platforms—particularly within the Drupal ecosystem. As the former Creative Director at Four Kitchens, Randy led cross-functional teams in developing cohesive design strategies, architecting front-end systems, and aligning user experience with organizational goals. He’s known for bridging the gap between high-level vision and implementation, ensuring that every project is both beautiful and deeply usable. Beyond his client work, Randy is a frequent speaker at DrupalCon, regional camps, and virtual events, where he shares insights on accessibility, usability, and design systems. A passionate advocate for open-source collaboration and digital equity, he is committed to making the web a more inclusive and empowering space for everyone.
Ivan Stegic - TEN7 ivanstegic Randy Oest - amazingrando.com amazingrando
The Modeler API is a new module that has been created by the Drupal community to address the requirement of existing modules and ecosystems with complex configurations, providing modern and easy-to-use UIs for non-technical users so they can independently create, modify, and maintain their own sites. Examples of such ecosystems are ECA (Events, Conditions, Actions - Drupal's modern rules engine), AI Agents, and Migrations.
With privacy regulations like GDPR, CCPA, and ePrivacy directives tightening globally, implementing a robust cookie consent solution on your Drupal site is essential. Drupal offers several cookie consent modules to help website owners comply with these laws while enhancing user trust. In this blog post, we’ll compare the most prominent Drupal cookie consent modules, including Klaro Cookie & Consent Management, to help you choose the best fit for your site. We’ll explore their features, ease of use, and compliance capabilities, concluding with a detailed comparison table.
Disclaimer: No liability is assumed regarding compliance with GDPR or other regulations. Always consult legal experts to ensure your site meets local privacy requirements.
Here’s a breakdown of the key Drupal cookie consent modules available as of June 2025, based on their functionality, configuration options, and compliance features:
1. Klaro Cookie & Consent ManagementWhen selecting a cookie consent module, consider the following factors:
Choosing the right Drupal cookie consent module depends on your site’s specific needs:
For most Drupal sites, Klaro or CookieYes are the top contenders due to their balance of features, compliance, and maintenance. If budget is a constraint, Klaro’s open-source nature makes it a strong choice, while CookieYes is worth the investment for automated compliance and peace of mind.
Note: Always verify compliance with legal experts, as module features may not cover all regulatory nuances.
Cookie Drupal Planet Drupal Share this Copied to clipboard Add new commentWelcome to the June 2025 DDEV Newsletter
This month: TYPO3 Community Budget Proposal (VOTE NOW), Randy is back from bikepacking, Running Old PHP versions, Vite and DDEV with WordPress, DDEV Architecture, and more.
Join us THURSDAY, June 12 at 1pm ET / 10am PT, for our call to chat about all things Drupal and nonprofits. (Convert to your local time zone.)
We don't have anything specific on the agenda this month, so we'll have plenty of time to discuss anything that's on our minds at the intersection of Drupal and nonprofits. Got something specific you want to talk about? Feel free to share ahead of time in our collaborative Google doc: https://nten.org/drupal/notes!
All nonprofit Drupal devs and users, regardless of experience level, are always welcome on this call.
This free call is sponsored by NTEN.org and open to everyone.
Please note that, since the meeting was moved a week early due to the Juneteenth holiday, the Zoom link for this month's call is different. Please use the following link for June’s call:
Join the call: https://us02web.zoom.us/j/87657453970?pwd=naknkSONquhpyIAIR5zLaHcroNbQvi.1
Meeting ID: 876 5745 3970
Passcode: 507410
This Pride Month, the Drupal Association invited community members to share their voice, story, and perspective through a short questionnaire, an open-hearted call to celebrate who we are and where we belong.
In a time when many in the queer community may not always feel seen or safe, we want to reaffirm that the Drupal Association is a space rooted in inclusion, care, and visibility. Our goal is to spotlight the strength, joy, and diversity within the LGBTQ+ community around the world. Through shared stories like the one below, we hope to reflect the beauty of our global community and remind each other: you belong here.
This is a space where all identities are respected, celebrated, and uplifted, not just in June, but always. As stated in the Open Web Manifesto, the open web thrives on inclusion: everyone in the world, regardless of background, identity, wealth, or status, has a home on the open web.
Today, we’re honored to share reflections from Fei Lauren, an inspiring human, community-elected at-large board member and a Drupal Diversity & Inclusion initiative lead. Their story explores moments of vulnerability, history, solidarity, and global connection, reminding us of the power in simply being seen.
How is Pride celebrated in your city or country?
West Coast Canada is known as one of the best places in the world to live for the LGBTQIA+ community. But it’s a very common practice here to include ‘2S’ before the other letters. 2S stands for Two-Spirit, and it goes first to acknowledge and honor that Indigenous Peoples were here first.
Otherwise, Pride celebrations in many communities are very family-oriented. Face painting is popular, and I’ve also seen things like bouncy castles.
Can you share a moment when inclusion really stood out to you, a personal story or memory?
I am genderqueer, and when I was first exploring neutral pronouns, the idea of putting pronouns in our Slack profiles came up at work. I didn’t realize it at first, but one of the managers I really liked and respected also used they/them pronouns.
We talked about it privately, and then they added their pronouns just before I did. I’ll never forget the anxiety I felt, followed by an incredible sense of relief that I wasn’t alone. I always try to be visible now. Sometimes, it just takes one person to shift that sense of vulnerability and make opening up feel safer.
What’s your favorite Pride-related fact, tradition, or symbol?
I recently learned that until the AIDS epidemic, the commonly used acronym was GLBT. Many medical professionals refused to treat patients who were HIV-positive, but the lesbian community stepped up as nurses and caregivers to provide support.
Changing the order of letters in the acronym, and the many variations used since, is done to honor this act of care and solidarity.
Is there a queer voice, an author, creator, or activist who has inspired or supported you?
I love Ivan Coyote. They have a book of letters from fans and their responses. I don’t cry easily, but some of the letters are so raw it’s impossible not to.
Pride celebrations here can sometimes feel like we’ve lost touch with our history and the ongoing struggle for respect, safety, and equality.
It feels important and powerful to tell those stories and make sure we don’t lose sight of how much work there is still to do in this world.
What’s one thing you love about the queer community you’re part of (in or outside Drupal)?
In Drupal, I love that the community is so global. I have learned a lot about what’s happening around the world. It’s easy to only see your own community and the struggles you and your friends face, the violence and heartbreak right in front of you.
But I love getting to celebrate wins and hold space for people globally. I’ve learned so much from the Drupal community. It has changed my relationship with queer activism and reminded me what I have to be grateful for. It also makes me feel like we really aren’t alone, and that gives me an incredible amount of hope.
Thank you, Fei, for your vulnerability, care, and presence in Drupal community. Your voice reminds us why representation matters and how simply showing up as yourself can make space for others to feel safe, seen, and supported.
To LGBTQ+ and queer members of our community, and to everyone reading, if you feel inspired to share your story this Pride Month, we welcome you with open arms. Every contribution helps build a more inclusive and loving web, one story at a time.
Want to share your own story? Submit your response here.
We also invite you to get involved with the Drupal Diversity & Inclusion (DD&I) initiative. Join the #diversity-inclusion channel on Drupal Slack and say hello! Learn more at drupaldiversity.com/get-involved.
Struggling with repetitive code when using Drupal's AI module for chat operations? Discover how the AI Helper module simplifies your development by streamlining common tasks, letting you focus on unique solutions instead of boilerplate.
Having written a couple of Drush scripts that utilise the Chat operation of the Drupal AI module (e.g. see part 1 in this series of Drupal AI articles) it was clear that certain operations were repeated in each task. I wrote a module, AI Helper, to provide a service that would avoid the need for repeated code.
Code StagesIt made sense to me to separate the code into three stages, each of which will be explained below:
The first stage consists of converting the input into the format required for the Chat request and obtaining the Provider and Model.
1a) Prepare inputWorking back from the parameters of the Chat request to the simplest input to the service, the logic was as follows:
Over the last nine years DDEV has grown from a tiny side project to a development environment and ecosystem that serves about 17,000 weekly developer-users and is critical to so many developers' workflows.
We love this amazing open-source world that we're a part of. It's astonishing when communities can work together and of course the fact that we all stand on the shoulders of such giants like Linux, Debian, and hundreds of other projects.
What Happens When a Community Loses its Maintainer?What happens when a great project loses a key maintainer? A couple of years ago Bram Moolenaar, the maintainer of the Vim editor, passed away unexpectedly. Every project faces unexpected transitions, whether a maintainer steps back, changes focus, or, as happened with Bram, passes away. The Vim community did step up successfully, but that's not the only outcome possible for so many small projects.
What can we learn from Vim's experience, and how is DDEV positioned in comparison?
One thing that the Vim community discovered was that Bram's work was truly a full-time job, even with their incredible and active community.
Many people may think that DDEV is just a tiny project that could carry on without its maintainers, but that might not be true. Right now support, maintenance, and improvements for DDEV use the full-time and consistent effort of two full-time maintainers. That's why you get the level of support and responsiveness you do. Both maintainers are currently paid, but perhaps not at a salary level that you would accept.
The Good StuffVim had serious challenges in all these areas, as there was only one "owner" of the GitHub project, and financial setups were very much ad-hoc. Bram was truly the "owner" of the whole project.
Areas to ImproveWe work hard to identify areas that are dependent on a single maintainer, and to resolve those. But it's a perpetual process!
As of June, 2025, DDEV's monthly support is at the $7800 USD level. Our goal is $12,000. You can see this at any time on the top of ddev.com, and a full accounting updated daily is in the sponsorship-data repository. Our current bank balance is about $19,000 USD.
Share Your Thoughts!Do you have additional ideas, suggestions, or insight into how DDEV's future could be more sustainable? We would sure love to hear from you! Or get active and join our DDEV Advisory Group.
Do you have questions or want to talk (about sponsoring or anything else)? Contact us! or join us in Discord.
Have you signed up for the monthly DDEV Newsletter? We'd love to have you.
AI is reshaping how we build websites. Instead of creating everything from scratch, we're moving toward setting goals where AI helps deliver results.
Today we're launching a coordinated effort to accelerate AI innovation in Drupal:
✓ Clear strategy and shared vision
✓ Funded delivery team with full-time contributors
✓ $120,000 in operational funding
✓ Active work tracks: AI Core, Products, Marketing, and UX
Join us: https://www.drupal.org/ai/
Blog post: https://dri.es/accelerating-ai-innovation-in-drupal
Today we are talking about Automated Testing Kit demo Recipe, Why Automated Testing is important, and How this recipe helps with guest André Angelantoni. We’ll also cover Taxonomy Views Integrator as our module of the week.
For show notes visit: https://www.talkingDrupal.com/506
TopicsAndré Angelantoni - drupal.org/project/automated_testing_kit aangel
HostsNic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Norah Medlin - tekNorah
MOTW CorrespondentMartin Anderson-Clutz - mandclu.com mandclu
Imagine a marketer opening Drupal and with a clear goal in mind: launch a campaign for an upcoming event.
They start by uploading a brand kit to Drupal CMS: logos, fonts, and color palette. They define the campaign's audience as mid-sized business owners interested in digital transformation. Then they create a creative guide that outlines the event's goals, key messages, and tone.
With this in place, AI agents within Drupal step in to assist. Drawing from existing content and media, the agents help generate landing pages, each optimized for a specific audience segment. They suggest headlines, refine copy based on the creative guide, create components based on the brand kit, insert a sign-up form, and assemble everything into cohesive, production-ready pages.
Using Drupal's built-in support for the Model Context Protocol (MCP), the AI agents connect to analytics tools and monitor performance. If a page is not converting well, the system makes overnight updates. It might adjust layout, improve clarity, or refine the calls to action.
Every change is tracked. The marketer can review, approve, revert, or adjust anything. They stay in control, even as the system takes on more of the routine work.
Why it mattersAI is changing how websites are built and managed faster than most people expected. The digital experience space is shifting from manual workflows to outcome-driven orchestration. Instead of building everything from scratch, users will set goals, and AI will help deliver results.
This future is not about replacing people. It is about empowering them. It is about freeing up time for creative and strategic work while AI handles the rest. AI will take care of routine tasks, suggest improvements, and respond to real-time feedback. People will remain in control, but supported by powerful new tools that make their work easier and faster.
The path forward won't be perfect. Change is never easy, and there are still many lessons to learn, but standing still isn't an option. If we want AI to head in the right direction, we have to help steer it. We are excited to move fast, but just as committed to doing it thoughtfully and with purpose.
The question is not whether AI will change how we build websites, but how we as a community will shape that change.
A coordinated push forwardDrupal already has a head start in AI. At DrupalCon Barcelona 2024, I showed how Drupal's AI tools help a site creator market wine tours. Since then, we have seen a growing ecosystem of AI modules, active integrations, and a vibrant community pushing boundaries. Today, about 1,000 people are sharing ideas and collaborating in the #ai channel on Drupal Slack.
At DrupalCon Atlanta in March 2025, I shared our latest AI progress. We also brought together key contributors working on AI in Drupal. Our goal was simple: get organized and accelerate progress. After the event, the group committed to align on a shared vision and move forward together.
Since then, this team has been meeting regularly, almost every day. I've been working with the team to help guide the direction. With a lot of hard work behind us, I'm excited to introduce the Drupal AI Initiative.
The Drupal AI Initiative builds on the momentum in our community by bringing structure and shared direction to the work already in progress. By aligning around a common strategy, we can accelerate innovation.
What we're launching todayThe Drupal AI Initiative is closely aligned with the broader Drupal CMS strategy, particularly in its focus on making site building both faster and easier. At the same time, this work is not limited to Drupal CMS. It is also intended to benefit people building custom solutions on Drupal Core, as well as those working with alternative distributions of Drupal.
To support this initiative, we are announcing:
For more details, read the full announcement on the Drupal AI Initiative page on Drupal.org.
Founding members and early support Some of the founding members of the Drupal AI initiative during our launch call on Google Hangouts.Over the past few months, we've invested hundreds of hours shaping our AI strategy, defining structure, and taking first steps.
I want to thank the founding members of the Drupal AI Initiative. These individuals and organizations played a key role in getting things off the ground. The list is ordered alphabetically by last name to recognize all contributors equally:
These individuals, along with the companies supporting them, have already contributed significant time, energy, and funding. I am grateful for their early commitment.
I also want to thank the staff at the Drupal Association and the Drupal CMS leadership team for their support and collaboration.
What comes nextI'm glad the Drupal AI Initiative is now underway. The Drupal AI strategy is published, the structure is in place, and multiple work tracks are open and moving forward. We'll share more details and updates in the coming weeks.
With every large initiative, we are evolving how we organize, align, and collaborate. The Drupal AI Initiative builds on that progress. As part of that, we are also exploring more ways to recognize and reward meaningful contributions.
We are creating ways for more of you to get involved with Drupal AI. Whether you are a developer, designer, strategist, or sponsor, there is a place for you in this work. If you're part of an agency, we encourage you to step forward and become a Maker. The more agencies that contribute, the more momentum we build.
Update: In addition to the initiative's founding members, Amazee.io already stepped forward with another commitment of USD $20,000 and one full-time contributor. Thank you! This brings the total operating budget to USD $120,000. Please consider joining as well.
AI is changing how websites and digital experiences are built. This is our moment to be part of the change and help define what comes next.
Join us in the #ai-initiative channel on Drupal Slack to get started.
[newsletter-blog]