Drupal Planet

This guest post is by DDEV community member and TYPO3 contributor Garvin Hicking.

In my daily work, I develop TYPO3-based projects and also contribute to the TYPO3 CMS OpenSource project itself.

Usually this means working with actively supported and up-to-date PHP versions as well as database systems like MySQL/PostgreSQL/MariaDB.

Just recently I had to migrate a very outdated project: TYPO3 4.5, which utilized MySQL 5.5 and PHP 5.3. When that project was initially developed, it was done with XAMPP and later Vagrant-based VMs. This has been long superseded with using Docker and specifically DDEV for ease-of-use.

So naturally I wanted to be able to use DDEV for the legacy project to get it working just as it is running on the (outdated) hosting provider's shared web servers.

I quickly faced three major issues:

• No PHP 5.3 out-of-the-box support from DDEV; it starts with 5.6 as of the time of this writing
• No MySQL 5.5 ARM64 support either; it starts with 5.7
• Additionally, I use an Apple MacBook Pro M1 with ARM-chipset, which has no "official" MySQL 5.5 support

Thanks to the outstanding DDEV support on Discord, I was quickly able to find a way with minimal effort, just by creating very small custom, additional docker-compose YAML files.

One advantage (of many) of using DDEV instead the underlying Docker Compose is that so many things are pre-configured and "just work". So I really did not want to migrate everything to Docker Compose on my own, do my custom routing, PHP-FPM integration and whatnot.

Just being able to "bait and switch" the PHP and DB container with a different base Docker image was all that was needed for me:

I created the base ~/legacyphp/.ddev/config.yaml file manually inside my ~/legacyphp project directory, setting legacyphp as the project name.

Note that I configured PHP and MySQL versions that are supported by DDEV for this first:

Next I created the very small file ~/legacyphp/.ddev/docker-compose.db.yaml in the same directory next to config.yaml:

Three things are noteworthy:

• Setting linux/amd64 as the platform will require Rosetta to be available on the macOS ARM64 platform
• The BASE_IMAGE is set to a DDEV db container of legacy Docker images that are still provided.
• Changing the entrypoint is a workaround to prevent DDEV complaining about a mismatching MySQL version after restarting the project. The small script "tricks" the DDEV inspection into believing, the version matches the one configured in .ddev/config.yaml.

Using a different PHP version is just a few lines more work, because we are not replacing the whole web container of DDEV. Instead, we add an additional PHP container which is executed from the web container via port 9000.

This is done via the file ~/legacyphp/.ddev/docker-compose.php.yaml:

Note here that we use devilbox/php-fpm with our needed version, and a bind-mount takes care the PHP container can access our main project root directory.

A special mount of ~/legacyphp/.ddev/php/ is included so that we can control the php.ini configuration, if needed. For example you could disable the OPCache+APC in case you're doing some legacy benchmarking that should not be falsified via caching, I created a very small file ~/legacyphp/.ddev/php/php.ini file with the contents:

To execute PHP with our external PHP Docker image, I created the following file in ~/legacyphp/.ddev/apache/apache-site.conf:

Note that if your document root is not htdocs you would need to adapt this name to your liking (like public or wwwroot or anything) in all occurrences of this file.

Now you can execute ddev start and then ddev launch to see your project up and running.

You could create a simple ~/legacyphp/htdocs/index.php file with <?php phpinfo(); ?> to verify the version.

Using ddev mysql will connect you to the MySQL 5.5 instance:

You can enter the PHP Docker container with a command like docker exec -it -u devilbox ddev-legacyphp-php bash if you need/want to execute PHP commands on shell-level, because the regular web container will run with the more recent PHP 8.3 version. So if you need to perform composer CLI calls, be sure to do this within the matching PHP container.

Another thing to pay attention to is that if you for example want to utilize Mailpit with TYPO3's mail configuration, you can not use localhost:1025 as an SMTP server. localhost in PHP's case will be that devilbox PHP container, and not the DDEV web container. Instead you need to setup web:1025 as the hostname.

The devilbox PHP config has pretty much all available PHP extensions set up to use, but if you need specific imagemagick or other tools, you will have to either ensure these are executed on the web container, or make them available with customization of a different base Docker container that you can build yourself.

If you want to use Xdebug with this setup, you'll need to do more internal port forwarding in the docker-compose setup, which is beyond the scope of this article.

Having shown you what is possible, I hope you will never need to use it, and you will always use well-supported and current software. :-)

Thanks so much to the DDEV project for getting me across the finish line with just very little effort!

Did you search for Drupal API documentation in the past and ended up on outdated information on api.drupal.org? I heard this story from many people before and it also happens to AI bots. This is a problem the Drupal Association wanted to fix for a while but did not get around to it with all the priorities. 

Acquia held an internal hackathon called 48Create on 15-16 May, 2025. I joined the team formed by Ben Mullins around Drupal documentation and I decided to take on this problem. 

In this episode, Mike Anello and Mike Herchel dive into a casual conversation covering a wide array of topics. They start by discussing the concept of a podcast with almost no effort required and the mystery of Stephen's involvement. The conversation then quickly shifts to Florida Drupal Camp, mentioning its impressive 16 uninterrupted years, the increase in attendees, and how fun it is. They touch upon single directory components in Drupal, their importance, and intricacies like CSS styling, schemas, and Experience Builder. The discussion also includes insights into popular Drupal events like Florida Drupal Camp, Drupal Dev Days, and the upcoming DrupalCon. They infuse humor and personal anecdotes while engaging in thoughtful technical exchanges and playful banter.

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

Mike, widely recognized by his Drupal.org username "ultimike," is a prominent figure in the Drupal community with over 15 years of experience as a developer, educator, and community leader. As the co-founder and vice president of DrupalEasy, a Florida-based training and consulting firm, he has been instrumental in shaping the careers of countless Drupal professionals through comprehensive programs like Drupal Career Online and Professional Module Development .(drupalcampnj.org, nedcamp.org) Anello's contributions extend beyond education. He has been deeply involved in the Drupal ecosystem, serving as a core contributor to the Migrate module, co-maintaining several contributed modules, and actively participating in issue queues and documentation efforts . His leadership roles include membership in the Drupal Community Working Group and the Conflict Resolution Team, as well as organizing the Florida Drupal Users' Group and Florida DrupalCamp for over a decade .(The Drop Times, nedcamp.org) As the host of the long-running DrupalEasy Podcast, Anello provides insights into Drupal development, community news, and interviews with key contributors, fostering a sense of connection and ongoing learning within the community (DrupalEasy). His dedication to mentoring and community building has made him a respected and influential voice in the Drupal world.

Mike is a seasoned front-end developer and a prominent contributor to the Drupal community, with over 15 years of experience in web development. He is best known as the lead developer of Olivero, Drupal's default front-end theme, which emphasizes accessibility, modern design, and user experience. (ImageX) In addition to his work on Olivero, Mike serves as a core CSS maintainer for Drupal and is the creator of the Quicklink module, which enhances site performance by preloading links in the user's viewport. He also has amazing calves. They're the size of small children. Rumor has it that his vertical jump is over 4.5 inches! He has also contributed to the introduction of Single Directory Components (SDC) into Drupal core, aiming to streamline component-based theming. (The Drop Times, herchel.com) Beyond his technical contributions, Mike is an active community leader. He has served on the Drupal Association Board of Directors and is a primary organizer of Florida DrupalCamp. (Drupal) As a speaker, he has presented at various events, including EvolveDrupal, discussing topics like the future of Drupal theming and the Starshot initiative, which seeks to make Drupal more accessible to site builders. (evolvedrupal.com) Professionally, Mike works as a Senior Front-End Developer at Agileana, where he continues to advocate for accessibility, performance, and the open web. (evolvedrupal.com) He shares his insights and experiences through his personal blog at herchel.com, contributing to the ongoing evolution of Drupal and its community.

Discussion Topics:

• The Best Podcast Idea Ever
• Florida Drupal Camp: A Legacy of Success
• Single Directory Components: Getting Started
• TD Cafe: The Podcast Name Debate
• Deep Dive into Single Directory Components
• Experience Builder and Component Integration
• Custom Themes and Single Directory Components
• Design Tool Integration
• CSS Variables and Component Architecture
• Template File vs Render Array
• CSS Preferences: Plain CSS vs Post CSS
• Top Drupal Events
• Concluding Remarks and Personal Plans

Mike Anello - DupalEasy ultimike

Mike Herchel - herchel.com mherchel

Jira is an incredibly popular project management and issue tracking tool and is very flexible and adaptable to project workflows and can be further enhanced with the extensive application ecosystem that surrounds the product.  In a recent project, we used Maestro AI to supercharge a Jira workflow to offload external participant feedback loops to Maestro and let Maestro AI determine which feedback loop to use.

After weeks of listening, prompting, and pattern-spotting, we’re entering a new phase. The big questions are becoming sharper. The conversation is shifting—from what might be to what must be true.

Our early exploration surfaced a wide range of motivations, risks, and hopes for a Drupal Site Template Marketplace. The signal was clear: there’s strong belief in the potential—if we build it in a way that strengthens the ecosystem, not fragments it.

As part of this shift from the breadth of exploration and to the depth of early structure, we’re moving to a biweekly share out cadence. This Share Out #5 update highlights what’s emerging from Slack Prompts #5 and #6, insights from Survey #3 on Governance and Fairness to inform first drafts of the Lean Business Model Canvas and Governance Framework—early scaffolding for what’s to come.

In design thinking, there’s a natural rhythm between divergence—where we explore widely—and convergence—where we begin to shape and prioritize. We’re now entering that second phase.

The goal is not to lock down answers prematurely, but to begin assembling the scaffolding that can support real-world testing, feedback, and evolution.

We’re asking:

• What makes a template worth trusting?
• What makes one worth paying for?
• What kinds of governance and community signals need to be in place from day one?

In response to Slack Prompt #5, contributors agreed that establishing baseline quality, accessibility, and transparency standards is essential.

Automation was broadly supported—but not blindly. There’s growing recognition that automated checks are necessary but not sufficient, especially for more nuanced requirements like semantic markup or keyboard navigation.

Most scanners will find 200 security bugs in Drupal and maybe 1 is real. Human review is still required.”

“Let’s at least show the automated results transparently and let buyers decide.”

Contributors are also thinking ahead about user expectations:

Paid listings should absolutely meet higher standards—users will expect it.”

These insights inform the governance framework’s approach to certifications, self-attestations, and recurring review cycles for paid listings.

Slack Prompt #6 helped unpack the value exchange at the heart of the Marketplace. Why would someone purchase a GPL-licensed template?

The answer: time savings, trust in the “official” source, and ease of setup.

The confidence that comes from knowing the template came from an official, trusted source like the DA is huge."

"One-click demos for themes... that’s my #1 trust signal.”

Participants also cautioned that separating the template from hosting or support could confuse non-technical buyers, especially those coming from SaaS ecosystems.

“Too many hosting choices at signup may mirror Mastodon’s ‘pick a server’ confusion.”

This feedback is pushing us to consider default hosting pathways, bundled services, and better “first-use” experiences.

Our third community survey zeroed in on values: fairness, recognition, and trust.

Contributors emphasized the importance of clear expectations and governance guardrails—especially when money enters the picture.

“Revenue must also support the ecosystem—modules, infrastructure, DA.”

Many participants supported the idea of tiered models, where certified templates provide extra confidence:

“Even free templates should meet basic accessibility and security requirements if they’re hosted on Drupal.org.”

Recognition also matters:

“Templates should be rated based on feedback… great to know why someone considers a product to be 1 or 3 stars.”

That insight is helping shape how we design review systems that are credible, transparent, and helpful—without opening the door to spam or bias.

Informed by three surveys, one RTC session, and six slack discussions worth of community research combined with competitive research and discussions with Drupal’s intellectual property attorney, the Marketplace Working Group is now in active development on two core artifacts:

• Lean Business Model Canvas
  Mapping how the Marketplace creates, delivers, and shares value—across contributors, agencies, end users, and the Drupal Association.

• Governance Framework (Draft)
  Outlining submission criteria, listing types, maintenance expectations, enforcement paths, and contributor recognition.

This scaffolding is not final—it’s a living structure meant to evolve through our continuing research, feedback and community review. Nonetheless, it does feel exciting to see it all start to take shape!

• Pilot Planning: Testing incentive and governance structures in collaboration with DCP and other agency participants in RTC #2 and beyond.

• Governance Draft: A public request for comment (RFC) on the governance framework will launch this summer.

• MVP Quality Standards: Defining a small, automatable set of checks for accessibility, security, and licensing for free templates.

💬 Join #drupal-cms-marketplace on Slack
Each week, there's a new prompt to explore a key question as we define this Marketplace.

🎧 Listen to Talking Drupal #504 
On this week's podcast, we discussed the vision, opportunities, and challenges of creating a trusted, high-quality Drupal Site Template Marketplace that supports adoption, contributor incentives, and community values without compromising open-source principles.

Thanks to all who are continuing to shape this work with insights, critiques, and care. What we build next will depend on the strength of the scaffolding—and the people who show up to co-create it.

UX as a first class citizen in Drupal core! Announcing new UX Manager role for Drupal core and Cristina Chumillas and Emma Horrell as first UX Managers: https://www.drupal.org/about/core/blog/ux-as-a-first-class-citizen-in-drupal-core

We’re excited to announce a big step forward for user experience in Drupal Core: the creation of the new UX Manager role within the core leads team. This is a foundational move toward UX-driven development, where user experience is embedded from the start, not added at the end.

Historically, UX responsibilities in Drupal Core were shared across different roles, often falling under product management. But in practice, UX input has often arrived late, focusing on small usability tweaks rather than shaping the overall experience.

By creating a dedicated UX Manager role, we’re making sure UX has a clear voice — from early feature discussions to final design decisions. This will help us build more intuitive, cohesive, and accessible experiences for everyone using Drupal. We’re also laying the groundwork for the future: supporting more UX practitioners to contribute to Drupal and from there, grow into decision-making roles, strengthening our design contributor community, establishing a stable UX testing process, and making onboarding easier for designers and researchers.

For now, this role will be co-led by Emma Horrell and myself, Cristina Chumillas.

Emma is the UX Research Lead for Drupal CMS and has shaped many aspects of the project through her work researching target audiences, testing features, and helping reduce “Drupalisms.” Her research expertise will continue to help us align Drupal with real user needs. Many thanks to the University of Edinburgh for supporting her continued contributions.

I’ve been the usability topic maintainer for years and currently serve as Product Design Lead for Drupal CMS and Drupal core Front-end Framework Manager. I’m looking forward to helping embed UX more deeply into how Drupal Core is defined, designed, and built.

This is just the beginning. If you’re interested in improving Drupal’s experience, join us in the #ux-working-group on Drupal Slack — and help us put UX at the heart of Drupal’s future.

In early April, 2025, I was a guest on the Talking Drupal podcast discussing Back-to-Basics, an idea I had to get more beginner-level presentations at Drupal events as a way to better support (and retain) our newer community members. As I am currently a bit overcommitted, this, regretfully, is not something that I have the bandwidth to lead.

I do feel that the idea, and getting it up and running as soon as possible, is a good one that can contribute greatly as one solution to the declining pool of Drupal developers that will sustain us into the future. So, here is my call: I am looking for someone inspired by the growing need to attract and retain Drupal newbies who is interested in taking the lead with the idea, adding their flair, and moving it forward.

As an incentive, know that I've talked with plenty of people who are willing to help, including the folks from the Drupal Open Curriculum Community Initiative. In addition, I'm more than willing to provide assistance, make introductions, and help where I am able to ensure success. 

The idea for Back-to-Basics came from one of our Drupal Career Online alum during our weekly office hours. It was shortly after Florida DrupalCamp 2025 that the alum asked me if "there were any good Views-related sessions" from the event that they could watch. The answer was "no," unfortunately, and over the next few days this bugged me more-and-more. How are we expected to grow the community with new developers and contributors if our events offer little-to-nothing for them?

The goal of Back-to-Basics is to make it easy for Drupal event organizers to include solid beginner content for their new-to-Drupal attendees. The strategy makes available 6-8 Drupal pre-prepped event presentations that can be delivered by a vetted pool of experienced Drupal presenters. The presentations will be readily available to any Drupal event organizers along with the names of willing presenters. 

As a developer of curriculum, I know how challenging and time-consuming it can be to not only develop, but also (and, perhaps, more importantly) maintain training materials. Creating, maintaining and then donating 6-8 45-minute Drupal event presentations is a big ask. However, It also occurred to me that finding 6-8 Drupal trainers and organizations who would be willing to create and/or donate and maintain a 45-minute presentation in exchange for some promotion makes a bit more sense. This was quickly validated by the first 4 trainers that I spoke with.

The final element is ensuring that the actual presentations serve to not just educate, but inspire. It is critical then, that every presentation should be delivered by the best presenters available at each event. As the old adage says, we have only one chance to make a first impression. The most experienced Drupal developers and presenters providing beginner content is the kind of impression we want to make to newer Drupalists whom we want to get excited about Drupal. It just feels right. Again, this idea was validated by every single one of the experienced presenters I approached. 

I have identified two main challenges that will need to be overcome:

1. Available presentation slots at Drupal events. Not many Drupal events have the luxury of open rooms or slots in their schedule. Putting some priority on these beginner sessions would need to be part of the event planners’ insights in that it would not only be in our community's long-term interest, but contribute to growth of their event in the future, if they made room for beginner content.
2. Presenter/session selection. Presenters who participate in the Back-to-Basics program (or develop their own) shouldn't be penalized for presenting beginner-level content when it comes to session selection. If the maintainer of a core subsystem wants to present beginner-level content, that shouldn't count against them if they are proposing an advanced session as well, in the normal flow of session selection for the same event. 

If you are inspired, and considering making a go of leading the charge on this, I am sure you have some ideas on how to proceed.  Some fuel for thought; here are the basics of what I envision you'll need to do:

1. Reach out to Drupal trainers to confirm their participation. (I can help with that!)
2. Determine the list of 6-8 beginner-level topics that should be covered (the Open Curriculum folks can help with this!)
3. Develop guidelines for presentation slide decks, including promotion guidelines and common slides.
4. Figure out where the presentations will be stored.
5. Develop the list of Back-to-Basics presenters.
6. Develop an informal written agreement with trainers for presentation maintenance.
7. Work with the Drupal Event Organizers working group to help spread the word.

I'm sure you have more ideas to enhance the program, (like nifty t-shirts) and there will surely be some additional tasks as well, but I think this list covers the big ones.

Finally, know that I envision my role as that of a mentor for whoever decides to take this on. I'll be more than happy to provide guidance, answer questions, and make introductions.

Interested? Have questions? Connect with me (ultimike) on the Drupal Slack workspace or use our contact form. 
 

Still on Drupal 7? You’re not alone, but it’s time to plan ahead! Thousands of websites still run on Drupal 7. And while Dropsolid offers extended support, the reality is clear: Drupal 7 is at the end of its innovation cycle. The question is no longer if you should move, but how and when.

At Dropsolid, we guide organizations in making the best choice: whether that means extending support on Drupal 7, migrating to modern Drupal (currently Drupal 11), embracing the power of Drupal AI or a combination of this.

Migrating from Drupal 7 to a modern Drupal version is a big step, and many site owners face challenges that delay that move. These are the most common migration roadblocks:

Technical Hurdles

• Complete theme redesign
• Complex content and media structure rework and data migration
• Custom modules and thrid-party integrations often require major rewrites

Organizational Barriers

• Limited development capacity
• Budget constraints
• Competing priorities across teams

We get it. These challenges don’t make migration simple. But don’t worry, there’s a solution that can bridge the gap and give you more time to prepare: Drupal 7 Extended Support (D7ES).

Drupal 7 Extended Support allows your team to maintain security and performance while planning a future-ready migration.

At Dropsolid, we provide Extended Support for your Drupal 7 website. Unlike many other firms, we have a large team of Drupal 7 experts on board with over 620 years of Drupal experience. And we are fully committed because we currently support a lot of Drupal 7 applications.

What we offer:

• Security patching and monitoring
• Infrastructure support and optimization
• Compatibility workarounds
• Time to prepare for a clean migration

We can offer you more time, which you can use to:

• Reassess your digital goals
• Inventory and audit your site components
• Explore D10 and Drupal AI

Note: At Dropsolid, we don’t consider Drupal 7 Extended Support as a permanent solution, but as a bridge to your next digital chapter. We can help you determine your Digital strategy and align this through our open DXP.

The Dropsolid Drupal 7 Extended Support Program is the perfect temporary solution for you. It allows you to consider your next steps and take away migration pressure.

As extended support is not a long-term solution, looking into migrating to modern Drupal is essential. Dropsolid offers expert Drupal migration services to bring your website up to date with modern standards and technologies, making it faster, more secure, and more scalable. We understand that every business is unique, and we tailor our migration approach to your specific needs and challenges.

Looking beyond modern Drupal? There’s an exciting future waiting with Drupal AI! This integration and automation into your CMS unlocks a new level of efficiency, personalization, and innovation.

Imagine the power of AI-assisted content generation, smart tagging, and intelligent content recommendations—all within your CMS. Drupal AI has new tools to:

• Boost content velocity by generating drafts, suggestions, and ideas based on existing content and keywords.
• Improve UX by offering intelligent recommendations tailored to user behavior, interests, and needs.
• Automate routine time-intensive tasks such as tagging, categorizing, and content updates, reducing the manual effort your team needs to put in.

For example, on a Drupal e-commerce site, AI can dynamically adjust product recommendations based on user behavior, increasing conversions and personalization. Content editors could have AI-generated suggestions ready to publish based on traffic and preferences.

As your website evolves, embracing Drupal AI can be the next logical step after migrating to modern Drupal. It gives you the ability to stay ahead of trends and deliver an exceptional, personalized experience for your users.

Not sure which path is right? You don’t have to decide alone. Whether you need more time on Drupal 7 or are ready to innovate, we help you:

• Stay secure on Drupal 7 (for now)
• Build a migration roadmap for modern Drupal
• Discover Drupal AI's potential

We also support organizations in redefining their digital strategy—integrating a full Digital Experience Platform (DXP) and even AI . This ensures your next digital chapter isn't just an upgrade, but a transformation.

Get in touch with us and have a call with our Drupal experts. We’ll assess your current setup, explore your goals, and help you choose the smartest path forward.

Contact us → https://dropsolid.com/en/contact

In this episode of Talking Drupal, we dive into the intricacies of the Drupal marketplace initiative with our guest, Tiffany Farriss, CEO and co-owner of Palantir.net and long-time board member of the Drupal Association. We explore the goals and challenges of creating a trusted Drupal marketplace, discuss how site templates can lower the barrier to entry for new users, and examine the importance of maintaining community trust and the sustainability of Drupal. This episode also includes a spotlight on the Views CSV Source module and an in-depth discussion on community feedback, the potential value and business models for site templates, and the steps needed to make a go/no-go decision on the marketplace by the upcoming Vienna event.

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

• Meet Our Guest: Tiffany Farriss
• Module of the Week: Views CSV Source
• Deep Dive into Views CSV Source
• Introduction to the Drupal Marketplace
• Goals and Challenges of the Marketplace Working Group
• Community Feedback and Sustainability
• Monetization and Fairness in the Marketplace
• Risk Mitigation and Future Plans
• Exploring the Impact of Releases and Usage
• Challenges and Successes of the Drupal Marketplace
• Defining the MVP for the Drupal Marketplace
• Addressing Community Concerns and Governance
• Engaging the Community and Next Steps
• Final Thoughts and Contact Information

Marketplace initiative

Tiffany Farriss - palantir.net farriss

Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Norah Medlin - tekNorah

Martin Anderson-Clutz - mandclu.com mandclu

• Brief description:
  • Have you ever wanted to present data within your Drupal website that comes from a CSV flat file, without having to import that data to your Drupal database? There’s a module for that.
• Module name/project name:
  • Views CSV Source
• Brief history
  • How old: created in March 2024 by Daniel Cothran (andileco) of JSI, though I met Danieal at Midcamp earlier this week and he was emphatic that his colleague and co-maintainer Nia Kathoni (nikathone) deserves significant credit
  • Versions available: 1.0.11, which works with Drupal 8.8, 9, 10, and 11
• Maintainership
  • Actively maintained, latest release was last month
  • Security coverage
  • Test coverage
  • Documentation - a robust README
  • Number of open issues: 4 open issues, none of which are bugs
• Usage stats:
  • 56 sites
• Module features and usage
  • With Views CSV Source installed, you can create a view that uses a CSV as a source instead of the Drupal site’s data. You can point to a file within your site’s filesystem, or it can be a remotely hosted CSV. If the file requires authentication for access, it is also possible to include encoded credentials in a header.
  • Now you can use CSV Fields to specify the columns you want to pull into the view, and you can use the “group by” to specify datasets to represent, for example to plot as lines in a chart
  • You can also create filters, either a CSV Field that acts a standard text filter, or a CSV Field Options filter that creates a dropdown of all the unique values in a specified column
  • Your assembled data can be shown in tables or charts, and can also be manipulated using standard view configuration, or using contributed modules like Views Simple Math Field
  • The module also comes with sort and a contextual filter plugins
  • It was impressed by a demo of Views CSV Source in a lightning talk at Midcamp yesterday, so I thought it would be fun to talk about today

Dear Readers,

Sustainability in tech often gets mentioned, rarely applied. Drupal is one of the few CMS ecosystems where it’s actually being worked into the foundation, not just as a value, but as a practice. There’s a public sustainability guide that encourages developers to write efficient code, avoid unnecessary features, and think twice about hosting choices. It's not flashy stuff—it’s small decisions that, over time, reduce environmental impact.

At DrupalCon Vienna 2025, that same thinking is being applied to the event itself. Organisers have opted for a plant-forward menu, less printed material, and a more minimal approach to swag. Nothing radical—just decisions that cut down waste without making a big show of it. Public transport is promoted, and the venue was chosen with sustainability in mind. It’s a practical shift, not a marketing stunt.

Where Drupal stands out isn’t in big claims, but in how openly it documents its process. Whether it's project pages, contributor conversations, or performance frameworks like Gander that account for server load, the effort is public and collaborative. That transparency makes it easier for others—inside or outside Drupal—to pick up and build on what’s already there.

This matters because sustainability in web development can’t be solved by one team or one platform. But it can be influenced. Drupal’s approach says: here's what we’re trying, here’s what’s working, and here’s where we still have work to do. If you’re part of this community, it’s something to keep pushing. If you’re not, maybe it’s something to learn from.

• Content Sync’s DrupalCon 2025 Debrief: What Developers Really Think of Content Cloud
• From Chennai to San Francisco, With Drupal in Between

• Drupal Public Data, Statistics & Silver Linings? An Exploration #5
• DrupalX AI v2.0 Released with OpenAI Integration and JSON Prompt Optimization
• New Drupal Module Streamlines Translation Workflow for Multilingual Sites
• Drupal Commerce Recurring Donation Widget Released with Full Customization Support
• Drupal Association Proposes International Federation to Unite Global Communities

• “And Beyond” Starts Here: How Drupaljam 2025 Is Rewriting the Rules
• amazee.io to Host Webinar on Secure AI Tools for Drupal Sites
• International Splash Awards to Be Held at DrupalCon Vienna 2025
• DrupalCon Vienna 2025 Invites Community-Led Events

• Why the University of Applied Sciences Chose Drupal—and How Attico Made It Work
• Why End-User Organisations Like Syngenta Support Drupal Events?
• amazee.ai Unveils Privacy-First AI Provider for Drupal, Open Source and Enterprise-Ready

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 and Facebook. You can also join us on Drupal Slack at #thedroptimes.

Thank you, 
Sincerely 
KAZIMA ABBAS
Sub-editor, The DropTimes.