webjoke.de

Using Colima with an SSL inspector

After Cognizant installed Zscaler on my work Mac, DDEV could no longer retrieve images from Docker Hub. It complained that it could not verify the TLS certificate. I use Colima as my Docker provider, which apparently does not yet automatically update it root certificate authorities to match the machine it runs on.

Darren Oh Fri, 03/07/2025 - 16:43 Tags

• DDEV
• Drupal

• Read more about Using Colima with an SSL inspector
• Log in or register to post comments

I've started working on maintaining Views Data Export again.

I've decided to document my work in 2 week 'sprints'. And so this article is about what I did in Sprint 4.

 

Sprint progress

At the start of the sprint in the Drupal.org issue queue there were:

• 45 open bugs
• 1 fixed issue.
• 63 other open issues

That's a total of 109 open issues.

By the end it looked like this:

• 40 open bugs
• 1 fixed issue.
• 59 other open issues

So that's a total of 100 open issues, an 8% reduction from before.

Key goals

In this sprint I wanted to:

• Go through the remaining bug reports
• Try to get Drush commands back in.

Bug reports

Didn't manage to get through these, but I did discover this fantastic website:

https://contribkanban.com/board/views_data_export

Where I can view all the tickets in a non-nasty way.

I got through some bug reports and committed one fix that closed out two tickets.

Drush commands

I couldn't bring myself to commit the code that was on the issue in this sprint, I've explained myself in the issue. It just seems like although the code works, it's not doing things in the 'right' way.

Part of the code in that issue is refactoring some code around so that it can be called from multiple places. This is making the MR look a lot more messy than it might first appear, so I might split those pieces off into their own MR and get those committed in before looping back and trying to address the Drush specific elements of the current MR in that issue.

I'm planning to tackle this next week, as part of the Sprint 5.

I'll likely do a release at the end of Sprint 5 too.

Future roadmap/goals

I'm not committing myself to doing these exactly, or any particular order, but this is my high-level list of hopes/dreams/desires, I'll copy and paste this to the next sprint summary article as I go and adjust as required.

• Update the documentation on Drupal.org
• Not have any duplicate issues on Drupal.org

Debug Academy introduces Drupito, a new SaaS platform designed to simplify Drupal CMS hosting and maintenance for small businesses, nonprofits, and individuals. Drupito provides secure, fully managed Drupal environments with automatic updates, affordable pricing, and no vendor lock-in. With the upcoming release of Drupal CMS in 2025, Drupito aims to make Drupal more accessible, offering key features like AI-powered site-building, structured content management, and enhanced security. The platform will debut at DrupalCon Atlanta, with a free trial available for early adopters.

How to Update Drupal Core, Modules & Themes with Composer and Drush bhavinhjoshi Fri, 03/07/2025 - 15:01

Updating your Drupal site is a critical task to ensure security, performance, and compatibility. With tools like Composer and Drush, the process becomes streamlined, especially when you want to stay within the same branch (e.g., updating from Drupal 10.4.x to 10.4.y).

In this tutorial, we’ll walk you through the step-by-step process of updating Drupal core, contributed modules, and themes using Composer and Drush, all while keeping everything in the same branch. Whether you're a seasoned developer or a Drupal newbie, this guide has you covered!

Prerequisites

Before we start, make sure you have the following set up:

1. A Drupal site managed by Composer: Your site should have a composer.json file in the root directory.
2. Drush installed: Drush is a command-line tool for managing Drupal. You can install it globally or as a Composer dependency in your project.
3. Git (optional but recommended): For version control and backups.
4. Access to the terminal: You’ll need to run Composer and Drush commands.
5. A backup of your site: Always back up your database and files before performing updates.

Got everything ready? Great! Let’s move on.

Step 1: Check Your Current Versions

First, let’s see what we’re working with. Open your terminal, navigate to your Drupal project’s root directory, and run:

composer outdated "drupal/*"

This command lists all outdated Drupal packages (core, modules, and themes) managed by Composer. You’ll see something like this:

drupal/core 10.3.5 10.4.4 Drupal core drupal/pathauto 1.11 1.13 Generates URL aliases drupal/token 1.10 1.15 Provides token functionality

Next, check your Drush version to ensure compatibility:

drush --version

You should see output like Drush Commandline Tool 12.5.3.0 If Drush is outdated, update it with:

composer update drush/drushStep 2: Back Up Your Site

Before making any changes, back up your database and files. Use Drush to export your database:

drush sql-dump > backup.sql

Copy your site files (including web/ and vendor/) to a safe location or commit your changes to Git:

git add . git commit -m "Pre-update backup"

Safety first!

Step 3: Update Drupal Core

To update Drupal core within the same branch (e.g., 10.3.x to 10.3.y), you have a few options depending on your setup. Here are three methods inspired by the official Drupal release notes (like those for Drupal 10.4.4), tailored for Composer-managed sites:

Option 1: Update with Composer (Recommended)

This is the standard approach for Composer-managed sites. Open your composer.json file and check the version of Drupal core under "require":

"drupal/core": "^10.3"

The ^10.3 constraint ensures Composer updates to the latest 10.3.x release without jumping to 10.4.x. 

Run:

composer update drupal/core --with-dependencies

This updates Drupal core and its dependencies (e.g., Symfony components) to the latest compatible version, such as 10.3.5. Check the output to confirm the update.

Option 2: Specify a Specific Version

If you need a specific version (e.g., 10.4.4 instead of the latest in the branch), modify composer.json to pin the version:

"drupal/core": "10.4.4"

Then run:

composer update drupal/core --with-dependencies

Alternatively, you can update directly from the command line without editing composer.json:

composer require drupal/core:10.4.4 --update-with-dependencies

This ensures you get exactly 10.4.4, which is useful for testing or aligning with a specific release.

Option 3: Manual Update with Composer Packages

For more control (or if you’re troubleshooting), you can use the separate Composer packages recommended by Drupal.org (drupal/core-recommended or drupal/core-dev). First, adjust your composer.json to use:

"drupal/core-recommended": "^10.4"

Then run:

composer update drupal/core-recommended --with-dependencies

The core-recommended package includes Drupal core plus a set of pinned dependencies for stability. This mimics the approach in Drupal’s release notes for manual tarball updates but leverages Composer’s dependency management.
 

Note: Stick with your existing setup unless you have a reason to switch (e.g., drupal/core vs. drupal/core-recommended). 

For this tutorial, Option 1 is the simplest for staying in-branch.

Step 4: Update Contributed Modules

Now, let’s update your contributed modules. To stay in the same branch (e.g., 1.x for a module), ensure your composer.json specifies compatible versions. For example:

"drupal/pathauto": "^1.11", "drupal/token": "^1.10"

Run:

composer update drupal/pathauto drupal/token --with-dependencies

Or, to update all contributed modules at once:

composer update "drupal/*" --with-dependencies

Composer will fetch the latest versions within the specified branches. Check the output to confirm the updates.

Step 5: Update Themes

Themes follow a similar process. If you’re using a contributed theme like drupal/olivero, check its version in composer.json:

"drupal/olivero": "^1.0"

Update it with:

composer update drupal/olivero --with-dependencies

Alternatively, if you used composer update -W in Step 4, your themes would already be updated along with modules, assuming no conflicts. For custom themes not managed by Composer, you’ll need to update them manually or via Git (if they’re in a repository).

Step 6: Run Database Updates with Drush

After updating files, Drupal might need to apply database updates. Use Drush to do this:

drush updatedb

This runs any pending update hooks (e.g., hook_update_N()) from core or modules. You’ll see output like:

[success] No database updates required.

Or, if updates are applied:

[success] Applied update 10101 for module 'pathauto'Step 7: Clear the Cache

Clear Drupal’s cache to ensure the updates take effect:

drush cache:rebuild

This command rebuilds the cache and ensures your site reflects the latest changes.

Step 8: Test Your Site

Visit your site in a browser and test key functionality:

• Navigate pages to check for errors.
• Test updated modules (e.g., create a Pathauto alias if you updated it).
• Verify your theme renders correctly.

If you encounter issues, check the logs with Drush:

drush watchdog:showStep 9: Commit Your Changes

If everything works, commit your updated composer.json and composer.lock files to Git:

git add composer.json composer.lock git commit -m "Updated Drupal core, modules, and themes"Troubleshooting Tips

• Composer conflicts: If you see dependency conflicts, run composer why-not drupal/core 10.4.4 to diagnose.
• Drush errors: Ensure Drush is compatible with your Drupal version (e.g., Drush 12 for Drupal 10).
• Permission issues: Adjust file permissions if Composer or Drush fails to write files.

Updating Drupal core, contributed modules, and themes within the same branch using Composer and Drush is straightforward once you get the hang of it. By following this process—checking versions, backing up, updating with Composer, and finalizing with Drush—you’ll keep your site secure and up-to-date without breaking compatibility.

Have questions or run into a snag? Drop a comment below, and we’ll help you out. 

Happy updating!

Updates Drupal Drupal Planet Drupal core Share this Copied to clipboard Add new comment

Anyone working with Drupal on a regular basis should come to DrupalCon Atlanta. The city itself is easily accessed, directly connected to innumerable cities around the country and world via its massive airport. Furthermore, the crowd of people sure to attend will be the most engaged leaders of, contributors to, and users of Drupal ready to share and improve each other's work.

Centarro will have a contingent there representing both our client services and Drupal Commerce. At an event like this, we're eager to hear the stories of people using Drupal Commerce to build their own businesses and client sites. In addition to motivating us to continuing our contribution with vigor, these conversations reveal ways our services and features could be improved to serve merchants better.

We'd love to chat at the booth (507/509, toward the center of the hall) or to see you at our session on Wednesday, Drupal Commerce's Starshot Roadmap. As the resident Commerce guys, we'll have Starshot themed coins to give away along with some stellar wristbands that are fantastic for wiping the sweat off your brow in a mosh pit or on a tennis court. (I doubt the Kraftwerk concert Sunday evening will get that rowdy, but we'll be in General Admission and hope to see you there.

Drupal CMS Docs: Should We Combine the CMS and User Guides?

When Drupal CMS launched, we built a guide to help users get started—but now we’re facing a big question: how does it relate to the existing Drupal User Guide? Should we keep them separate or merge them into a single, streamlined resource? In this post, Joe breaks down the challenges, and explores what’s next.

joe Thu, 03/06/2025 - 16:05

For Drupalists in the nonprofit sector, the Nonprofit Summit on Monday, 24 March is a must. We also invite all DrupalCon Atlanta attendees to register for the Nonprofit Summit, which promises a highly informative agenda. This is more than just another conference track—it’s an opportunity to connect with mission-driven professionals, sharpen your Drupal skills, and gain insights into how open-source technology can empower your organization. 

Nonprofits and open source share core values—collaboration, transparency, and community-driven innovation. In an era where the nonprofit sector faces increasing challenges, it’s important to remember that Drupal isn’t just a technology choice; it’s a commitment to an ecosystem that aligns with your mission. Attending the summit will reinvigorate your appreciation for the open-source community and provide a refreshing sense of camaraderie when the sector needs it most.

DrupalCon Atlanta 2025 Nonprofit Summit Agenda 09:00-09:15: Welcome 

Stephen Musgrave: Welcome and overview

09:15-11:30: Fireside Chats

• 9:15am: Cristina Chumillas and Pamela Barone: The Future of Drupal CMS
• 10:15am: Emma Horrel: User Experience in Drupal CMS
• 11:15: Tim Lehnen: Drupal for Nonprofits: nuances to bring back to your org 

11:30-11:45: Break 11:45-12:45: Breakout Sessions (Concurrent Roundtable Discussions)

• Improving the user experience on nonprofit websites
• Aspects and features of Drupal that make it the best choice for nonprofits
• When headless might make sense for your nonprofit
• How to have a conversation with technical and non-technical stakeholders 
• Accessibility & inclusive design

12:45-13:45: Lunch

A time for relaxing and networking if you feel like it.

13:45-14:45: Breakout Sessions (Concurrent Roundtable Discussions)

• Getting the most out of Drupal for nonprofit websites
• Harnessing AI for your nonprofit website
• Using Drupal at your membership organization.
• Simplifying content management for nonprofit teams
• Keeping up with advancements in technology on a nonprofit budget

14:45-15:00: Break 15:00-16:00: Recipes

Tim Lehnen: Recipes for nonprofit Drupal CMS users and Q&A

16:00-17:00pm: Optional Networking

Wrap up conversations, meet new colleagues, and explore partnership opportunities.

Here’s a glimpse of the activities and topics covered.

Drupal CMS

The morning is dedicated to Drupal CMS. We will explore how the Starshot initiative launched the first release of Drupal CMS and what the future holds. We will discuss the user experience for nonprofit users and what Drupal CMS means for nonprofit adopters. This portion of the day will be interactive and include plenty of time for discussion. 

Tim Lehnen from the Drupal Association will close out the section by summarizing the big picture Drupal CMS adventure and connecting the open source framework to nonprofit value systems and providing talking points to bring back to nonprofit orgs in support of Drupal. One of the biggest hurdles to adopting Drupal is securing leadership buy-in. The Nonprofit Summit will equip you with the tools to make the case for Drupal with confidence. 

A Lineup of Engaging Breakout Sessions

A diverse set of breakout sessions will ensure you can focus on the topics most relevant to your organization’s needs. Expect discussions on nonprofit-specific challenges, case studies from organizations that have successfully implemented Drupal, and hands-on workshops where you can troubleshoot real-world problems. 

Network with Like-Minded Changemakers

The nonprofit world thrives on collaboration, and there’s no better place to build connections than at the Nonprofit Summit. You’ll meet others who share your passion for social good and open-source technology. You’ll find a community of people eager to share experiences, offer advice, and even explore potential partnerships. Nonprofits are stronger when we work together, and the summit is a perfect chance to forge new relationships.

Join Us in Atlanta!

The nonprofit sector is constantly evolving, and technology plays a crucial role in helping organizations achieve their goals. Whether you’re looking to refine your Drupal expertise, advocate for open-source solutions, or simply find inspiration among your peers, the Nonprofit Summit at DrupalCon Atlanta is the place to be. Mark your calendar, pack your bags, and get ready to be part of a movement that empowers nonprofits through technology.

Register here: https://events.drupal.org/atlanta2025

DrupalCamp England returns! The Drupal community came together in Cambridge for a weekend. Inspiring keynotes, AI innovations and new connections proved the community is stronger than ever.

Fibers is a new feature in PHP 8.1 that brings lightweight and controlled concurrency to PHP.

PHP 8.1 Fibers introduce efficient, non-blocking execution, making Drupal faster and more responsive. Instead of waiting for sequential HTTP requests, Fibers run them simultaneously, reducing load times and enhancing user experience. This optimization is particularly useful when working with multiple cURL-based API calls or external data fetching.

Drupal Use

Real-Time Use Case of PHP Fibers in Drupal

Since Drupal is single-threaded, we can't run true asynchronous tasks like in Node.js. However, PHP Fibers can help optimize performance by allowing tasks to be executed without blocking the main script.

Experience Builder (XB) most prominent UI piece is its preview canvas, where multiple viewport widths are visible next to each other. The preview canvas is meant for placing components, modifying their inputs and moving them around. For that reason, you cannot interact with the contents of each component. What if you do want to try that?

That’s where the new Preview functionality comes in that was built by Jesse Baker, Dave “longwave” Long and Harumi “hooroomoo” Jang, which removes UI chrome and allows the content author to focus on their creation:

XB’s preview mode: interactable previews, without UI chrome other than the top navigation bar.
Issue #3486785, image by Jesse.

With the UI chrome removed, interacting with the individual components in this mode makes sense:

XB’s preview mode: interactable previews allow for example clicking links in component instances — but with some guardrails.
Issue #3486785, image by Jesse.

Then there’s the small matter of being able to actually save what you created

Many online course creators wonder how to effectively manage sales and automatically grant access to educational content. With Drupal and the available modules, we can build a fully functional online store that handles payments and automatically assigns users to purchased courses. We encourage you to read the article or watch an episode of “Nowoczesny Drupal” series (the video is in Polish).

This list highlights key Drupal contributed modules designed to enhance SEO performance. Covering URL optimization, metadata management, redirects, sitemaps, and more, these modules help improve search rankings, site navigation, and content discoverability in Drupal CMS.

The Hidden Costs of Choosing Budget Hosting for Your Drupal or WordPress Website jenna Tue, 03/04/2025 - 14:29 Drupal WordPress

When selecting a hosting provider for your Drupal or WordPress site, it’s tempting to choose the cheapest option available. After all, it looks like a cost-effective solution up front. But in reality, budget hosting can introduce hidden costs that could affect your website’s performance, security, and long-term stability.

To back up a little and provide context for non-technical website decision makers, let’s answer the question: What role does web hosting play? Web hosting is essentially the service that stores your website’s files and makes them accessible on the internet. The quality of hosting affects everything from site speed to uptime and security.

Having hosted websites since 2003 and worked with providers ranging from budget hosts like DreamHost to cloud services like Amazon Web Services (AWS), Azure, and DigitalOcean, I’ve seen how these choices impact organizations. I am going to break down why specialized hosting providers are often the smarter choice.

Why Budget Hosting Can Cost More in the Long Run

Unless your organization has a dedicated Development or DevOps team, relying on a single developer or IT professional to manage your site hosted on a platform like AWS or DigitalOcean can be risky. This developer needs to handle everything: server maintenance, security patches, and performance optimization. If that person leaves, your site could be left vulnerable, and finding a replacement with the same expertise can be challenging—and expensive.

Specialized hosting reduces reliance on individual expertise and ensures greater stability. On the other hand, specialized hosting providers like Pantheon, Acquia, Kinsta, and Platform.sh handle server management for you. This means you won’t need a developer to manage critical tasks like software updates or security patches.

Key Features of Specialized Hosting Providers

Specialized hosting providers offer features that budget and cloud hosts often don’t, including:

• Staging environments: Budget hosts typically lack staging environments, crucial for testing changes before going live. Without this, you’d need to set up a separate server for testing—an additional hassle and expense. Specialized hosts provide built-in environments where you can test updates with ease.
• Automated backups: Budget hosts often don’t include automated backups by default. With specialized providers, backups are built-in and accessible to developers, making it easier to restore your site or troubleshoot issues.
• Security and updates: Providers like Pantheon and Platform.sh handle server-level security updates automatically. This eliminates the need for a dedicated team or developer to manage these critical aspects.
• Standardized developer access: Specialized hosts follow best practices for Drupal and WordPress hosting. This includes version control systems like Git, ensuring seamless collaboration and reducing onboarding time for new developers.
• Access control for non-technical users: Many specialized hosts provide tools that allow less technical people to manage developer access to servers, reducing dependency on specific team members.
• Website speed: Specialized hosts optimize server configurations for Drupal and WordPress out of the box, ensuring faster load times and better performance without requiring manual tuning. This not only improves user experience but also boosts SEO, helping your site gain better visibility in search engines.

The Bigger Picture: Saving Time and Reducing Risk

If your organization works with multiple developers or plans to expand, specialized hosting provides a safety net. Developers spend less time managing servers and more time focusing on what matters—improving your website. By minimizing time spent on server issues, specialized hosting reduces the risk of downtime, security breaches, or costly mistakes.

While budget hosting may seem cost-effective initially, it can lead to higher costs in the long run. Opting for a specialized Drupal or WordPress hosting provider ensures your website remains secure, scalable, and manageable—saving you time, money, and headaches down the road. Investing in a specialized provider today protects your site’s future and eliminates reliance on a single developer for server management.

Are you interested in moving your website to a specialized host and don’t know where to start? Let’s talk.

 

Joel Steidl

DrupalCamp England 2025 gathered Drupal experts and enthusiasts at the University of Cambridge for a day of innovation and learning. Highlights included AI-driven advancements, the unveiling of "Swarms" for AI-powered workflows, and discussions on UX, open-source contributions, and Drupal recipes. The event concluded with Annertech announcing two fully funded scholarships for 2026.

DrupalCon is a flagship event for everyone in the Drupal community, and developers are a huge part of the action. With DrupalCon Atlanta 2025 just around the corner, let’s take a look at what’s in store for these tech-savvy minds — especially the seasoned masters of the craft: senior developers.

There’s plenty to get involved in — contributing to Drupal’s future in code sprints, showing off your knowledge at Drupal Trivia Night, or grabbing cool swag from sponsors. But at the heart of the event? Insightful and thought-provoking sessions! 

If you’ve been building Drupal sites for years, you know that learning never stops. Staying ahead means keeping up with the latest innovations, tackling tough challenges, and exchanging ideas with fellow experts. DrupalCon 2025 is your chance to do exactly that — hear from top Drupal minds, ask the hard questions, and dive into discussions that push your skills further. Here’s a handpicked selection designed to challenge, inspire, and get you excited as a senior developer for 24-27 March.

Top sessions for senior developers at DrupalCon Atlanta 2025

“The future of Drupal core in the age of Drupal CMS” — by Gábor Hojtsy

Drupal CMS has been making waves, offering a fresh, flexible approach to building with Drupal. With Drupal CMS 1.0 officially released and work on version 2.0 already in motion, big questions are emerging about the future of Drupal core.

Will Drupal 12 simply be Drupal CMS? Well… yes and no. But what does that really mean? How will Drupal continue to support essential use cases like headless architectures, social, and e-commerce? And what about developers and other personas not directly in Drupal CMS’s focus — what changes can they expect?

When there are many questions, listen to the tech-savvy person behind many of Drupal’s innovations. Gábor Hojtsy, Drupal core committer and initiative coordinator, knows the answers. He always brings fresh perspectives and shares insights you might not have heard before.

Attend his session for a deep dive into the role of Drupal CMS in the entire ecosystem and the technical evolution of Drupal core. You’ll understand how this should impact long-term development strategies and how to adapt to the changing landscape.

“The Future of Drupal Theming: AI, Experience Builder, and Beyond” — by Mike Herchel

Drupal’s theming layer has evolved significantly in recent years, with new Twig filters, theme generation tools, and Single Directory Components making front-end development smoother than ever. But the biggest changes are still ahead.

With the introduction of Experience Builder and modern AI-driven tools, theming in Drupal is about to take a giant leap forward. How will these innovations reshape the way you build and style Drupal sites?

Immerse yourself in all the details at this session with Mike Herchel (mherchel), Drupal core committer, and the creator of the Olivero front-end theme. You’ll get a practical look at what’s coming in the next era of Drupal theming. Mike will share how to develop components for Experience Builder, where AI fits into your frontend process, and what should (and shouldn’t) be a component. Plus, you’ll pick up best practices to avoid unnecessary code bloat and ensure your work stands the test of time.

As a senior developer, you’re certainly already familiar with the quirks, strengths, and challenges of Drupal theming. This knowledge should be very helpful for getting the most out of the session. 

“Leveraging GitLab CI for contributions” — by Deepak Mishra and Ankit Pathak

Having a smooth and efficient development workflow can make all the difference. Automation is key to keeping things running smoothly. Here is where GitLab CI/CD comes in — a Continuous Integration and Continuous Delivery system built into GitLab. It automates the process of testing, building, and deploying your code.

The session by Deepak Mishra (deepakkm) and Ankit Pathak (ankitv18) will show you how to harness the power of GitLab CI/CD. You’ll explore how to set up a GitLab CI pipeline, run automated quality assurance checks, manage deployments, and handle merge requests.

Say goodbye to repetitive manual tasks and deployment headaches and embrace better collaboration with other developers. With practical tips from this session, you’ll level up your workflow, making your development process faster, smoother, and more reliable.

The session will focus on using GitLab CI/CD for contributions to drupal.org, so Deepak and Ankit will demonstrate the best practices in this area. However, the knowledge you obtain will be helpful in your client projects, too.

“Creating Composer aware modules with Drupal core’s new Package Manager module” — by Ted Bowman

Have you heard about Package Manager — a new experimental module in Drupal core that provides an API for interacting with Composer? It’s the key tool behind such innovative solutions as Project Browser and Automatic Updates, running Composer behind the scenes and allowing users to rely on the admin dashboard.

If you are curious about its work or want to build a module that performs Composer operations or integrates with Project Browser or Automatic Updates, here is a can’t-miss session. Who better to guide you through this than Ted Bowman (tedbow), Drupal core committer and the maker of Automatic Updates?

Using the example modules that rely on the Package Manager API, Ted will demonstrate the steps to implementing various features:

• making a simple form for installing modules by project name or URL
• cleaning up unused packages from your codebase
• showing detailed information about Project Browser’s work
• controlling which modules can be installed with Project Browser

You’ll also learn how to build user-friendly interfaces for Composer operations, customize Composer tasks with the Package Manager’s event system, retrieve detailed package information, and much more.

“Mixing the Schema.org Blueprints module into a Drupal Recipe to bake a sweet content model” — by Jacob Rockowitz

Structured data helps search engines better understand the content of a web page, leading to richer search results. Schema.org markup is a reliable way to achieve this goal. Want to be equipped with the best tools and practices for using it? Then read on.

In this DrupalCon session, you’ll get a look at two exciting, innovative solutions for building and managing structured content:

• First, the Schema.org Blueprints module offers a great way to define content using schema.org standards. Jacob Rockowitz (jrockowitz), the speaker of the session, is the creator of the Schema.org Blueprints module, as well as of the famous Webform module.
• But what if you could take that content model and arrange it into a ready-to-use package? That’s where Drupal Recipes come in — a ground-breaking innovation in Drupal for creating pre-configured functionalities and easily adding them to any new or existing Drupal project.

This session will show you how to combine the power of both. You’ll see a demo of how to build structured content types, as well as hierarchical content and organization charts.

“Collecting Data in Drupal When Internet is Unstable: Browser Local Storage and Service Workers” — by Nia Kathoni and Daniel Cothran

Drupal Recipes deserve a dedicated session in your schedule. They have really revolutionized how feature sets are added to websites. You can now pre-package the necessary modules and configurations in flexible ways, without being locked into the constraints of a specific distribution. Recipes can be applied, mixed, matched, and updated to meet the evolving needs of your website.

Introduced as experimental in Drupal 10.3, the Recipes APIs laid the foundation for Drupal CMS. Since then, the team has been refining the code base and gathering valuable feedback. DrupalCon Atlanta 2025 is the perfect opportunity to hear exclusive insights from the team.

If you are curious about one of Drupal Recipes, join Jim Birch (thejimbirch), the architect behind this solution. In his session, Jim will update you on the progress of the phase 2 roadmap of the Drupal Recipes Initiative. He will also delve into important topics such as config actions, default content, config checkpoints, and the process of creating recipes. Plus, he’ll explore idempotency — ensuring configurations remain reliable and consistent, no matter how many times they are applied.

Or maybe you’re ready to roll up your sleeves and help shape the next chapter? This session has a strong contribution focus, bringing together maintainers and contributors. You’ll learn how you can get involved with the Drupal Recipes Initiative.

“Supply Chain Security in Drupal and Composer” — by Christopher Gervais, Tim Hestenes Lehnen, and Neil Drumm

There can never be too much talk about security — especially when it comes to securing software supply chains. A software supply chain ensures that all the necessary software elements (like libraries, modules, or tools) are in place and function properly together. 

Join this DrupalCon Atlanta 2025 session to discover more about supply chains and how to protect them from unauthorized access. You’ll be introduced to the nature of supply chain attacks and understand Drupal’s vulnerability to such threats. You will also gain insight into how Composer, along with services like packagist.org and Private Packagist, fits into the supply chain, and the crucial role PHP dependencies play in securing your project.

Next, the session will cover the Automatic Updates Initiative, one of the Drupal Association’s most impactful efforts to ensure websites stay up to date and secure. You’ll also be introduced to essential tools for bolstering security, including:

• the Update Framework (TUF), which ensures that packages are safe and have not been tampered with before download
• the PHP-TUF Composer Integration Plugin, which adds an extra layer of security by verifying modules, themes, and profiles downloaded from drupal.org
• the Rugged TUF Server, which safeguards signing keys and supports the drupal.org packaging pipeline

The session will be led by Christopher Gervais (ergonlogic), Tim Hestenes Lehnen (hestenet), and Neil Drumm (drumm). They are renowned Drupal experts and active contributors to the Drupal Security Team, Automatic Updates, Drupal core, and more. This makes them perfectly suited to guide you through supply chain security.

Driesnote by Dries Buytaert

The central keynote at DrupalCon, Driesnote, is always something to look forward to. If there’s anyone at the event who hasn’t yet heard of Dries Buytaert, it certainly won’t be you. As a senior developer, you know Dries will keep you up to date with Drupal’s latest developments, and you will never want to miss his presentation.

Your experience has already shown you how quickly technology evolves, and Driesnote is the perfect opportunity to see Drupal’s momentum in action. Dries will share what’s next for the platform, including what’s in store for developers like you. This talk will give you a clear view of where Drupal is headed — whether it’s new features, tools, or improvements in how the platform works. Furthermore, based on past Driesnotes, even the most seasoned developers might find themselves completely amazed by the demos Dries has in store.

You’ll understand how the latest changes might impact your projects moving forward and how you can make the most of them. It’s a fantastic opportunity to stay ahead of the curve and connect with the Drupal community.

Final thoughts

Make sure to grab your ticket to the biggest Drupal gathering, where these and plenty of other great sessions are waiting for you. After enjoying this adventure, you’ll leave Atlanta with fresh techniques, smart solutions, and a stronger bond with fellow Drupal enthusiasts — fueling your work long after the event ends.

Welcome back, Site builders! We've got something you'll love.

If you've been around for a while you may be aware that Drupal 7 was much more accessible to the casual tinkerer than newer versions of Drupal. You'd regularly see Drupal 7 sites built by people who sometimes refer to themselves as "Site Builders" - a term which describes people who are comfortable building sites with Drupal, but may be less comfortable creating custom modules and themes.

The dropoff in Site Builders' participation since Drupal 7 is due in no small part to Drupal's decision to adopt modern development practices such as object-oriented programming, building on top of the Symfony framework, and utilizing a package manager. These are all good things! But we, as a community, are ready to welcome the casual Site Builder back with our latest developments.

ashrafabed Tue, 03/04/2025

Those of us in the UK had a great opportunity this last weekend to get together at the new DrupalCamp England event, held at Cambridge University. Protecting my work-life balance means I don't usually get to many in-person events, but I made it to this one. It was lovely to finally put some names to faces and build better understanding together. So thank you to the organisers and sponsors who put on a great day! A couple of us from our Coventry team went along, read on as I reflect on my own experience...

I was impressed that Baddý Sonja Breidert was doing the opening session - especially when we got to share her birthday cake! She demonstrated some fun use of an AI chatbot within a Drupal site; which looked like the kind of thing our clients could use to help visitors find what information they want. Rather than interacting with websites in the traditional point-and-click manner, browsing around pages to hunt down details, we need to watch out for how users are increasingly expecting to use the internet. Younger people aren't just typing keywords into a Google search and then gathering information like a researcher might. Instead, they're increasingly using voice or chat-based experiences, expecting the information to be brought to them, often via summaries from an AI. Including this in a Drupal website keeps users engaged directly, controlling the feel of interacting with a brand, and without surrendering the journey to external agencies.

Jamie Abrahams talking on 'Why Drupal AI might take over the world'

Jamie Abrahams gave a talk a bit later about combining AI 'agents' to complete all sorts of tasks. This combined the theory of this design pattern with some clear practical examples, to leverage LLMs' strengths in a controlled and understandable way. He also announced a new service for using AI with Drupal which would manage AI configuration (including API keys), to allow site builders to use it much more easily. At the moment they have to do hard work just to be able to ask AI to then do less complex tasks! My favourite part of the day followed immediately after when I joined my former colleague James Silver in conversation with Jamie's colleague Andrew Belcher out in the lobby. Andrew took us through a much deeper look at vector search and how these agents can be orchestrated together (as a 'swarm') within the Drupal UI, without writing any code! I challenged him on how this still needs the skills of a developer - as it requires architecting a solution, breaking work down into parts, etc - even if no code has to be written. I suppose coders and architects could be different personas; the term 'developer' might just describe the overlap. Now I wonder: could we treat each more helpfully, according to their strengths and interests?

Before long, even Baddý joined our table chat - she wanted to show off her team's efforts with AI and collaborate on using AI with Drupal. It was ace to see the authentic desire from these community figureheads to work together without egos, and to find myself actively participating in bouncing dreams together of what the internet might look like before long! Why invest in web pages when an AI can provide our content, or even build designs for us? How can we influence the window that people look through to our online presence? Going beyond well-structured content, could we provide structured brand metadata to shape how it is presented by AIs? For me, these conversations were the most valuable part of the day - putting our brains together as a community as we inspire and challenge each other. (Thanks to everyone for letting me chat with you!)

Emma Horrell: All aboard the UX express – how we can all apply user-centred ideas to make a Drupal to be proud of

Thankfully the day wasn't entirely dominated by AI ;-) I learnt plenty from Emma Horrell's session on incorporating UX Design expertise into the way we build with Drupal. It provoked me to thinking how we facilitate individual achievement, and wide collaboration between developers, but it's not so easy to build cross-disciplinary work. Core changes are reviewed by experts in specialist fields but it's not so common to incorporate that elsewhere, and early enough in plans. I'll remember her point that the challenge to think of other users’ experiences is what can make us grow. Gareth Alexander's dive into how Drupal CMS uses Recipes gave me a list to investigate this week (e.g. easy_email_express, Simple Add More and the Recipe generator

Find out how RESTful web services work and how Drupal simplifies API-driven development with the RESTful web services module. Simplified, practical, and ready to implement!

In the evolving landscape of web development, delivering seamless and engaging user experiences is paramount. Progressive Web Apps (PWAs) have emerged as a solution that combines the best of web and mobile applications. Integrating PWAs with Drupal can significantly enhance website performance and user satisfaction.

Understanding Progressive Web Apps:

PWAs are web applications that utilize modern web technologies to offer experiences similar to native mobile apps. They are designed to be reliable, fast, and engaging, providing functionalities such as offline access, push notifications, and home screen installation.

For a comprehensive guide, refer to the Progressive Web App (PWA) module documentation.
In this guide, we’ll cover everything you need to know about implementing PWAs in Drupal, from setup to optimization.

Happy March!

DDEV v1.24.3 was released earlier than planned for two major reasons: the new generic web server type allows Node.js and other interesting possibilities, and an upcoming Docker engine release was going to be incompatible with current Mutagen version. We encourage you all to upgrade because of this upcoming incompatibility, thanks!

Open-Source For The Win: See the details about how a future incompatibility with the Docker engine was pre-emptively caught and fixed, Open Source for the Win!

Web-based DDEV Add-on Registry is now live! Try it out at https://addons.ddev.com and check out the introduction blog.

TYPO3 Community Budget Ideas: Please vote!: We applied for the Q2 approval process to fund a great feature for DDEV, supporting mDNS as a domain-name resolution technique. If you're a member of the TYPO3 Association, you should have received an email to vote on this. We'd appreciate your vote!

Platform.sh has transferred domain names to DDEV: Thanks again to Platform.sh for their ongoing support. As a part of the process in change of their support, they have transferred control of the ddev.com and ddev.site domain names to the DDEV Foundation.

DDEV Notes and News

• The DDEV Advisory Group Annual Review and Planning Meeting is on Wednesday, March 5 (tomorrow!), and all are invited. The Zoom link is in the agenda link. We'll be looking at 2025 ambitions and 2024 review, we'd love to have you there!
• A review of DDEV's year 2024 has been added to the 2025 Plans and 2024 Review blog post. We'd love your feedback about both 2024 and the 2025 plans!
• The Drop Times rolled out an amazing promotion for DDEV, showing the current funding status against our goals. Now we need a community member to do the same thing for us in our website!
• The promotion done by The Drop Times consumes DDEV's current sponsorship information from the sponsorship-data repository, which has lots of potential for communicating about DDEV's funding status. Today's situation and totals are in all-sponsorships.json.
• Randy presented on Divide and conquer: A systematic approach to troubleshooting issues at Florida Drupalcamp. The full recording is on the link.
• Blog: Installing Drupal CMS with DDEV
• Blog from Matthias Andrasch: Vite suddenly not working due to CORS errors?