webjoke.de

Container Security in Production: Best Practices and Tools manager2 Fri, 09/26/2025 - 20:20

Container security best practices in production are a hot topic. They have changed the whole approach to web development. They make the process faster, more predictable, and easier to scale. But convenience does not eliminate risks. In a production environment where every failure can cost money, time, reputation, and security issues come to the fore. So, ignoring them means taking risks.

The top problems are well-known and include dangerous dependencies in images, weak access policies, and a lack of basic monitoring. And now add to this the human factor, and even a well-configured cluster can become vulnerable. Many people think that installing Docker and Kubernetes is enough. But attacks don`t wait for someone to finish reading the documentation.

In Part 3 of the Unmanaged Files in Drupal series, you’ll learn how to expose unmanaged file handling through a block plugin. By extending BlockBase and using dependency injection, developers can turn a custom file service into a reusable block that site builders can place anywhere. This tutorial walks through the plugin definition, constructor, factory method, and build process—complete with code examples—and shows how to enable the block in Drupal’s layout system.

Artificial intelligence is revolutionizing the way we manage content in CMS systems. Drupal is not lagging behind and offers more and more AI modules to automate editorial processes. In this article, I will present four of the latest AI-powered solutions for Drupal that can significantly improve content work and project management. This post is based on my video from the Modern Drupal channel. 

In preparation for the minor release, Drupal 11.3.x will enter the alpha phase the week of October 27, 2025. Core developers should plan to complete changes that are only allowed in minor releases prior to the alpha release.

The 11.3.0-alpha1 deadline for most core patches is October 29, 2025.

• Developers and site owners can begin testing the alpha after its release.

• Future feature and API additions will continue to be targeted against the main development branch, 11.x.

• Before 11.3.0-alpha1 is tagged, alpha experimental modules will be removed from the 11.3.x code base. Their development will continue in 11.x only.

• Following the release of Drupal 11.3.x and 10.6.x, only security issues will be fixed in Drupal 11.2.x and 10.5.x. Additionally, Drupal 11.1.x and 10.4.x will become end-of-life (EOL).

• During the alpha phase, core issues will be committed according to the following policy:

  1. Most issues that are allowed for patch releases will be committed to 11.3.x and 10.6.x. Such issues may also be committed to 11.2.x and 10.5.x until the final normal bugfix releases of 11.2.x and 10.5.x on December 10, 2025.
  2. Most issues that are only allowed in minor releases will be committed to 11.x only. (Such issues may be released in 11.4 or another future minor.). A few strategic issues may be backported to 11.3.x, but only at committer discretion after the issue is fixed in 11.x and before the beta deadline. For these issues, leave them set to 11.x unless you are a committer.
  3. Most issues that are allowed in maintenance minor releases will be committed to 11.x and 10.6.x only. A few strategic issues may be backported to 11.3.x and 10.5.x but only at committer discretion and before the beta deadline. For these issues, leave them set to 11.x unless you are a committer.

Roughly two weeks after the alpha release, the first beta release will be created. All the restrictions of the alpha release apply to beta releases as well. The release of the first beta is a firm deadline for all feature and API additions. Once the beta commit freeze begins, issues in the Reviewed & Tested by the Community (RTBC) queue will be committed to the next minor release only.

The release candidate phase will begin the week of November 26.

Security support of Drupal 10 and 11 Drupal 10.4.x and 11.1.x Security releases will be provided until December 10, 2025. Drupal 10.5.x and 11.2.x Security releases will be provided until June 15, 2026.

See the Drupal core release process overview, the Drupal core release schedule, allowed changes during the Drupal 10 and 11 release cycles, and Drupal 10 and 11 backwards compatibility and internal API policy for more information.

In July 2025, we conducted a comprehensive survey of over 200 marketing decision-makers and agency specialists to pinpoint the AI capabilities they value most.

Our analysis uncovers the key areas where organizations are concentrating their AI investments and identifies the features they consider essential for achieving long-term success. This report offers decision makers data-driven insights to help them prioritize their investments and maximize their strategic outcomes.

Download your copy today!

Key Trends from the Global AI Survey 2025 AI is no longer an experiment

Out of 216 respondents representing 199 different organizations, a significant majority indicated that their organization is already using AI. 

For the organizations that are already using AI, the applications are diverse, with a strong emphasis on general business support, marketing and content creation.

Rather than relying on staff to pick their own tools, organisations are increasingly embedding AI into established systems for example, CMS, CRM, marketing automation platforms.

Download The Global AI Report 2025

AI is a tool for automation and efficiency

Respondents were most enthusiastic about AI features that promise automation and efficiency. The most highly valued features address clear pain points and offer tangible benefits. 

Ability to deliver a market advantage is seen as significant

AI-assisted landing page builders are regarded as potential "killer apps" for their ability to shorten campaign launch times by streamlining or removing need for development skills.

A Focus on Trust and Human Control

While there is excitement about AI's potential, the survey also highlights a crucial need for features that enhance, but do not fully replace, human oversight. The report emphasizes that a focus on trust, accuracy, and the preservation of human control is paramount.

There is a clear desire for AI features that enhance human oversight – not replace it.

Respondents caution against AI taking over critical functions like permissions or autonomous actions. Many believe that certain responsibilities should remain under human oversight to prevent unintended consequences.

What stops organizations from using AI?

For the organizations that are not yet using AI, the main deterrents are varied but predominantly revolve around a lack of clear use cases, resource constraints, or concerns.

The primary reasons organizations are not using AI include concerns about data privacy and security, the ethical implications of AI, and the potential for AI to produce inaccurate or biased information.

Download the research

Equip your organisation with the knowledge to make informed AI investment decisions and stay ahead in a rapidly evolving digital landscape. Download your copy of The Global AI Report 2025 today and access the evidence-based guidance your team needs to prioritise initiatives and drive meaningful results.

Webinar recording: Key Insights from Global AI Survey and Roadmap Reveal

Our recent webinar summarised the report key findings. A recording is available to watch on The Drupal Association Youtube.

The Drop Times features a technical deep dive by Kelly Jacobs, Web Developer at Kalamuna, on Drupal’s new Config Actions API. The article explains how to use existing actions, build custom plugins or methods, and integrate them into recipes for predictable, reusable site-building workflows.

As the countdown continues for DrupalCon Vienna 2025, the global Drupal community is buzzing. This conference isn’t just another gathering, it’s shaping up to be one of the most technically rich, collaborative, and forward-looking Drupal events to date. Whether you build, design, strategize, or contribute, there are new incentives this year to make sure you’re part of it.

When & Where

DrupalCon Vienna 2025 runs from 14-17 October 2025, hosted at the Austria Center Vienna. This modern facility is well-equipped for large technical sessions, labs, workshops, and contributions, and Vienna’s efficient transit and infrastructure make it easy to get around and stay connected.

Vienna

Vienna is more than a beautiful and historic European capital. It’s also an international hub for tech innovation, design, standards, and open source culture. Attendees will be inspired not just by the sessions, but by the surroundings: cafés, museums, architectural landmarks, and a city layout that promotes walking, meeting, and exploring. There’s an energy in Vienna that pairs well with deep technical work quiet in the sessions, vibrant in the coffee-break ideas. The cosmopolitan and safe nature of the city also means it’s comfortable for international visitors.

Here, Sebastian Leu, Software Engineer, explores how AI supported his improvements to Drupal's autosave_form module. AI can accelerate test-driven development (TDD), making test-writing more practical within real project constraints.

sebastianleu@t… Wed, 09/24/2025 - 06:07

DrupalCon Vienna is not just about inspiring keynotes, networking, and workshops, it’s also a chance to experience one of Europe’s most beautiful and vibrant cities. Vienna is a place where centuries of imperial history meet cutting-edge creativity. Between conference sessions, you’ll have countless opportunities to enjoy the city’s legendary cuisine, buzzing nightlife, and unique cultural landmarks.

Here’s your curated guide to eating, drinking, and exploring Vienna like a local during DrupalCon.

Image

 

Where to eat: from Austrian Classics to Vegetarian Delights

Vienna’s food scene is incredibly diverse. Whether you want traditional Austrian comfort food or modern vegetarian gastronomy, the city has you covered.

Würstelstände (throughout Vienna)

These iconic sausage stands are part of Vienna’s cultural DNA. Try a Käsekrainer (cheese-filled sausage) or a classic Bratwurst with bread and mustard. Perfect for a late-night snack or a quick bite between events.

Traditional Austrian Dining

Pichlmaiers zum Herkner (17th District, reachable by tram)
A modern revival of a traditional Viennese “Beisl” (tavern). The atmosphere combines rustic charm with elegant design, and the menu highlights classics like Tafelspitz (boiled beef with horseradish sauce), Wiener Schnitzel, and seasonal Austrian specialties, all prepared with care.

See location on a map

Restaurant Eckel (19th District, Döbling)
A true institution of Viennese dining. For more than a century, Eckel has served traditional Austrian dishes in a refined but cozy setting. Highlights include goulash, roast meats, and the famous Viennese pastries. In summer, its leafy garden is perfect for dining al fresco.
See location on a map

Mährischer Spatz (near Austria Center Vienna)
Conveniently close to the conference venue, this restaurant serves hearty German and Austrian classics in a casual, welcoming setting. Expect generous portions of schnitzel, dumplings, and sausages, a good option when you don’t want to venture far after a long day.

See location on a map

Vegetarian & Plant-Forward Cuisine

Wrenkh (Inner City, near Stephansdom)
 Family-run and stylish yet welcoming, Wrenkh offers a modern approach to vegetarian cooking. Expect colorful plates of roasted vegetables, homemade pastas, and creative soups, often with international touches. Their open kitchen adds a sense of energy to the dining room.

See location on a map

Tewa at Naschmarkt (6th District)
Located in Vienna’s famous food market, Tewa specializes in organic dishes with Middle Eastern and Mediterranean influences. Think falafel, hummus platters, fresh salads, and hearty vegetarian bowls, all perfect for a casual lunch or dinner in a lively setting.

See location on a map

Karma Food (several locations, closest at Karmelitermarkt)
A laid-back café offering wholesome soups, curries, and Buddha bowls, often vegan. Karma Food is the place to recharge with something nourishing and healthy between busy conference days.

See location on a map

Drink: Bars, Cocktails, and Nightlife

Vienna has a vibrant but varied nightlife scene, ranging from historic cocktail bars to lively riverside hangouts.

Bermuda Triangle (Bermudadreieck, near Schwedenplatz)
A cluster of bars and pubs near the Danube Canal, known for its lively, youthful atmosphere. This is the best place if you want to hop between bars with colleagues and soak up Vienna’s social energy.

See location on a map

Neubau & Mariahilf (6th and 7th Districts)
These creative neighborhoods are home to small, independent bars with a hip vibe. Expect cozy wine bars, craft beer pubs, and stylish cocktail lounges where locals gather. Perfect if you want something less touristy.

See Neubau on a map

See Mariahilf on a map

Live Music at Gürtel (along U6 line)
The old Stadtbahn railway arches now house bars and music venues. Here you’ll find DJ sets, rock bands, and electronic beats late into the night, all in an edgy, authentic setting.

See location on a map

Explore: Vienna’s Cultural & Original Attractions

Vienna’s rich history and artistic soul make it a joy to explore. In addition to the famous palaces and museums, here are some must-sees for DrupalCon visitors.

Schönbrunn Palace
The former summer residence of the Habsburgs is a UNESCO World Heritage site. Explore the baroque palace rooms, stroll the vast gardens, and climb the Gloriette for a panoramic view of Vienna.

See location on a map

Belvedere Palace
Another historic palace complex with stunning baroque gardens and one of Austria’s most important art collections, including Gustav Klimt’s world-famous painting The Kiss.

See location on a map

St. Stephen’s Cathedral (Stephansdom)
The Gothic heart of Vienna. Climb the South Tower for breathtaking views over the city’s rooftops, or simply admire the colorful tiled roof and grand interior.

See location on a map

Naschmarkt
Vienna’s most famous market, lined with food stalls, small restaurants, and international vendors. A perfect place to sample local bites, shop for spices, or enjoy a casual meal.

See location on a map

Hundertwasserhaus
A whimsical apartment block designed by the artist Friedensreich Hundertwasser. Its colorful, irregular façade contrasts with Vienna’s imperial grandeur, a must for fans of quirky architecture.

See location on a map

Danube Canal & Donauinsel
Relax by the water, rent a bike, or grab a drink at one of the casual bars along the canal. Donauinsel (Danube Island) is especially lively in summer, with open-air bars and wide walking paths.

Hermesvilla in Lainzer Tiergarten
A hidden gem for those with extra time. Set in a forest on Vienna’s edge, this 19th-century villa was a gift from Emperor Franz Joseph to Empress Elisabeth (Sisi). Surrounded by nature trails, it’s ideal for a half-day escape.

See location on a map

Practical Tips

• The Austria Center Vienna is well connected by U-Bahn (metro line U1). Most downtown attractions are 10–15 minutes away.
• Reservations are recommended for popular restaurants, especially in the evenings.
• Don’t skip Vienna’s café culture. Spend an hour at a traditional coffee house like Café Central or Café Sperl to experience the city’s timeless atmosphere.
• Walking is the best way to explore the historic centre, pack comfortable shoes.
   

Vienna is the perfect setting for DrupalCon: inspiring, beautiful, and full of discoveries at every corner. Whether you’re here for a few days or an entire week, make sure to balance your time between the conference and the pleasures of this unforgettable city.

 

 

Nextide is excited to announce that we’re joining the Vector Institute’s FastLane program!  Our first step was enabling Maestro, our Drupal-based business process automation engine, with AI. Now, we’re taking the next step by joining the Vector Institute’s FastLane program. This reflects our commitment to Maestro, AI, and continued innovation for our Canadian built process automation engine.
 

Dripyard’s product launch webinar is coming up in less 7 days

Learn how to use the Views Data Export module in Drupal to easily export large datasets from views into CSV, JSON, or XML formats. Perfect for migrations, reporting, and analysis, without writing custom code.

This listicle from The DropTimes showcases 17 Drupal modules that extend the platform’s search and discovery capabilities using AI. From semantic search and vector-based querying to personalized recommendations and content analysis, these tools help developers build smarter, faster, and more relevant user experiences. Whether integrating with services like Pinecone and Azure or working with self-hosted solutions like Postgres and Milvus, these modules offer flexible options for modernizing how content is found and delivered in Drupal.

Managing a university’s digital presence is a complex challenge. Between faculty websites, alumni portals, departmental pages, and internal systems, it’s common for a large institution to maintain 50 or more individual sites. Each has unique needs, but all must stay on-brand and deliver a consistent user experience.

Today we are talking about Tugboat, What it does, and how it can super charge your ci/cd process with guest James Sansbury. We’ll also cover ShURLy as our module of the week.

For show notes visit: https://www.talkingDrupal.com/521

Topics

• Celebrating 20 Years with Drupal
• Introduction to Tugboat
• Comparing Tugboat with Other Solutions
• Tugboat's Unique Advantages
• Standardizing Workflows with Tugboat
• Handling Hosting and Development Delays
• Troubleshooting and Knowledge Transfer
• Client Base and Use Cases
• Agency Partnerships and Payment Structures
• Unique and Interesting Use Cases
• Challenges and Limitations of Tugboat
• Setting Up and Onboarding with Tugboat
• The Tugboat Origin Story
• Compliance and Security Considerations

Resources

• Tugboat
• Tugboat FEDRamp
• Lullabot Sells Tugboat Platform to Enable Independent Growth
• Shurly
• Talking Drupal #390 - Employee Owned Companies

Hosts

Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi James Sansbury - tugboatqa.com q0rban

MOTW Correspondent

Martin Anderson-Clutz - mandclu.com mandclu

• Brief description:
  • Have you ever wanted to use Drupal as a URL shortening service? There’s a module for that.
• Module name/project name:
  • ShURLy
• Brief history
  • How old: created in Aug 2010 by Jeff Robbins (jjeff) though recent releases are by João Ventura (jcnventura) of Portugal
  • Versions available: 8.x-1.0-beta4 which supports Drupal 9.3, 10, and 11
• Maintainership
  • Minimally maintained, maintenance fixes only. Also, the project page says that the 8.x branch is not ready for production use. So a big caveat emptor if you decide to try it
  • Number of open issues: 18 open issues, 5 of which are bugs against the current branch
• Usage stats:
  • 730 sites
• Module features and usage
  • With the ShURLly module installed, you can specify a long URL you want shortened, optionally also providing a case-sensitive short URL you want to use. If none is provided a short URL will be automatically generated
  • The module provides usage data for the short URLs, and and a user you can see a list the ones you’ve created as well as their click data
  • I was a little surprised to see that created short URLs are stored in a custom db table instead of as entities, but the module is able to avoid a full bootstrap of Drupal before issuing the intended redirects
  • The module provides blocks for creating short URLs, a bookmarklet to save a short URL, and URL history. There is also Views integration for listing the short URLs, by user or in whatever way will be useful in your site
  • There is also a submodule to provide web services for generating short URLs, or potentially expand a short URL back into its long form. The services support output as text, JSON, JSONP, XML, or PHP serialized array
  • The module allows provides a variety of permissions to allow fine-grained access to the capabilities it provides, and also has features like per-role rate limiting, APIs to alter redirection logic, and support for the Google Safe Browsing API, and Google Analytics
  • It’s worth mentioned that ShURLy is intended to run in a site on its own instead of within a Drupal site that is also serving content directly, but it will attempt to avoid collisions with existing site paths
  • Today’s guest, James, is one of the maintainers of ShURLy, but Nic, you mentioned before the show that you have a customer using this module. What can you tell us about the customer’s use case and your experience working with ShURLy?

Use Drupal Flake for PHPUnit testing Sep 22, 2025 By John Locke 0

Drupal Flake is a new way of doing local Drupal development (running a self-contained Drupal site on your desktop or laptop).

Dev Corner Read More

Use Group Purl on your Group site! Sep 22, 2025 By John Locke 0

One big missing part of the Group module is setting up friendly URLs that contain the group in the path for group content. You can't set this up in Pathauto -- the tokens are too limited to handle this correctly.

Dev Corner Read More

Easy unit testing with Drupal Flake and AI - Group PURL, a case study Sep 22, 2025 By John Locke 0

AI does not replace system engineering. Stories abound about AI running amok, deleting production databases, exposing private data, failing to deliver on promises.

Dev Corner Read More

On a recent client website, I needed to programmatically load and render 3 blocks. Plugin blocks to be precise. In modern Drupal, there are 3 types of block you can load/render: 

• Content blocks
• Config blocks
• Plugin blocks

And today we're interested in plugin blocks. 

Plugin blocks are blocks defined by the block plugin API in Drupal. They typically extend the BlockBase class and reside in a modules src/plugin/Block directory. 

Now, with that in mind, I hadn't done this sort of block load/rendering/creating for quite some time so I was kinda lost! I needed to load 2 views blocks and 1 webform block. After a little while of scratching my head, it occured to me that I need to look into the src/plugin/Block directory of the views/webform module to work what I needed. Initially I was struggling with the plugin_id value of the createInstance method on the plugin.manager.block service. 

Step 1

Looking at the plugin definition of each block type I was able to finally workout the ID needed to get an instance of each block. For views, it was views_block:<view_machine_name>-<view_display>. This was particularly tricky because the plugin definition doesn't actually tell you what the exact plugin id is. Sure, it gives you the first part e.g. views_block and for most plugin blocks that would have sufficed. But not with Views. During debugging, I noticed that I wasn't getting anything back from ->createInstance('views_block') so I had to go hunting for what wasn't working. Turns out the ID is made up in the pattern I outlined above. I found this via the deriver class within ViewsBlock (the plugin's class) and found these lines of code:

// Add a block plugin definition for each block display. if (isset($display) && !empty($display->definition['uses_hook_block'])) { $delta = $view->id() . '-' . $display->display['id'];

It was then I knew the makeup of the plugin_id. I said it before, it's tricky and this was fairly well hidden. Nowhere is this documented! 

The webform ID is thankfully quite different, it was just webform_block but required making use of the second parameter of createInstance(): $configuration. This is an array of information/settings that you can configure manually in the blocks UI. In this case, webform wanted me to pass in a webform_id key with the ID of the webform I wanted in the block. Again I found this via debugging the class for the plugin Drupal\webform\Plugin\Block and saw the webform_id key inside the defaultConfiguration() method. 

You can already see the difficulty here: no two plugin block definitions are the same. Views was quite happy for me to pass in the view I wanted in the $plugin_id parameter, whereas webform wanted the webform I wanted to use to be passed into the createInstance() method via the $configuration parameter.

Step 2

Really easy step this, once you've sorted out your plugin_id and you're happy that you get something back that resembles what you would expect, you now need to call ->build() on your new block instance. Don't worry, a full example will be shown below. 

Step 3

Now that you've (hopefully) got a render array of your block, you can now add some of the configurations you would expect to see if you were placing a block in the UI (/admin/structure/block). E.g. you can set the block level config like the label (via #configuration), the ID of the block, attributes etc plus other block_plugin related configuration.

Step 4

Render your block, simples! Assign your block to the $variables array (if you're in a preprocess for example) and then print your block out in a twig template. Done :) 

<div>{{ my_plugin_block }}</div>Code examples // A webform block example $configuration = [ 'label' => 'Contact us', 'label_display' => BlockPluginInterface::BLOCK_LABEL_VISIBLE, 'webform_id' => 'contact_us', 'provider' => 'webform', ]; $contact_form_instance = $plugin_block_manager->createInstance('webform_block', $configuration); $contact_form_render['content'] = $contact_form_instance->build(); $contact_form_render += [ '#theme' => 'block', '#id' => 'block-webform-contact-us', '#attributes' => [], '#contextual_links' => [], '#configuration' => $configuration, '#plugin_id' => $contact_form_instance->getPluginId(), '#base_plugin_id' => $contact_form_instance->getBaseId(), '#derivative_plugin_id' => $contact_form_instance->getDerivativeId(), ]; $variables['contact_form_block'] = $contact_form_render;// A view block example $related_posts_block_instance = $plugin_block_manager->createInstance('views_block:blog-related_blog_posts'); $related_posts_block_instance['content'] = $related_posts_block_instance->build(); $related_posts_block_instance += [ '#theme' => 'block', '#id' => 'block-blog-releated-blog-posts', '#attributes' => [], '#contextual_links' => [], '#configuration' => ['provider' => 'views_block'], '#plugin_id' => $related_posts_block_instance->getPluginId(), '#base_plugin_id' => $related_posts_block_instance->getBaseId(), '#derivative_plugin_id' => $related_posts_block_instance->getDerivativeId(), ]; $variables['related_posts_block'] = $related_posts_block_instance;  Tips and tricks

1. If you're still strugging to work out what your plugin_id should be, you can run this handy drush command to get a list of definitions:

drush ev "print_r(array_keys(\Drupal::service('plugin.manager.block')->getDefinitions()))";

2. After a quick win? You can make use of the twig tweak module to produce a 1 liner to render out a plugin block. See this article on how to do it.

Gotchas

As with anything these days, not all is as it seems.... there are a few things you should be aware of when loading/rendering blocks like this: 

1. Some hooks won't fire with plugin blocks that are loaded in the way outlined in this article. Blocks like (and not limited to) hook_block_view() and hook_block_build_alter() won't run for these types of blocks. And they're really common hooks, too! So just be mindful. If you're in a hook and it's not running when you expect it to (for a plugin block you've loaded) this is likely the reason why.
2. Be careful with access. Some blocks may have their own access checks and this method of loading can bypass those - whenever loading blocks like this just double check you're correctly following - or reimplementing - the access that was originally intended with that blocks.
3. Views blocks might lose the context that was originally intended for them. Contexts such as arguments etc may need to be re-set so the block can function properly.  
4. The same goes for caching. You may need to re-implement the caching that was originally set for the block you've loaded. it should be as simple as using the following code snippet:

CacheableMetadata::createFromRenderArray($build) ->merge(CacheableMetadata::createFromRenderArray($content)) ->applyTo($build);

HTMX in Drupal shifts the conversation from big architectural battles to something more practical: making the most of HTML sent directly from the server. Drupal already brings strengths like flexible content modeling, caching, and structured views. HTMX builds on that by letting site builders add interactivity with simple HTML attributes, rather than heavy front-end frameworks. As Ron Northcutt notes, the result is efficiency: the server does the work once, the response can be cached, and users get faster pages that are easier to manage. For editors, the payoff is immediate. A content preview can be swapped in with a click, a list item can update in place, and new dynamic features can be built without ever leaving the CMS. Fewer scripts in the browser also means better accessibility and less complexity for smaller teams.

Still, this is not a silver bullet. When HTML becomes the main way to deliver updates, teams must treat it carefully, just as they would an API. Without good standards, the code can get messy. Not every feature can rely on server-rendered HTML either. Personalized content, offline use, or real-time updates may still require more traditional JavaScript solutions. And while HTMX can live comfortably alongside Drupal’s existing systems, it takes planning to avoid conflicts and keep things smooth.

The real value is in balance. Ron’s efficiency argument rings true if developers approach HTMX with a server-first mindset and a focus on performance. But the bigger conversation is about knowing where to use it. HTMX in Drupal is ideal for enhancing editorial workflows and everyday site interactions, while leaving room for more advanced front-end approaches when they are truly needed. If teams treat this as a disciplined practice instead of a passing trend, Drupal can unlock new levels of speed and simplicity without losing its flexibility.

DISCOVER DRUPAL

• New Way of Writing Hooks in Drupal 11 Explained
• Unmanaged Files in Drupal: Building a Random File Handler (Part 2)
• Drupal AI Initiative Calls for Use Cases from Agencies, Developers, and End Users
• Vivek P R Releases “Views Node Title Selector” Drupal Module for Easier Node Title Filtering
• Kubernetes Platform Built in 6 Days Leads to New Drupal Kafka Module
• Glenn Hilton Prepares to Join Drupal Association Board of Directors

SECURITY

• Maintainer Account Takeover Hits NPM Packages in Supply Chain Attack

EVENT

• London Drupal Users Group Relaunches with Hybrid Meetup on September 24
• Drupal Business Dinner in Vienna Set for October 15, 2025 Ahead of DrupalCon
• Early Bird Registration Opens for DrupalCon Chicago 2026 at $575
• DrupalFit Challenge Vienna Edition Opens Ahead of DrupalCon 2025
• Acquia and Drupal Association to Host Live Session on Advanced Drupal Canvas Capabilities
• Early-bird Sponsorship Opens for DrupalCamp Italy 2025; Confirm by Sept. 29

ORGANIZATION NEWS

• Droptica Releases Open Intranet 1.5.0 with Drupal 11.2 Upgrade and Gin 5 Theme
• Pantheon Releases Public Preview of Google Docs-Based Content Publisher With Free Trial
   

We acknowledge that there are more stories to share. However, due to selection constraints, we must pause further exploration for now. To get timely updates, follow us on LinkedIn, Twitter, Bluesky, and Facebook. You can also join us on Drupal Slack at #thedroptimes.

Thank you.
Sincerely, 
Alka Elizabeth, 
Sub-editor, The DropTimes.