TDT September Townhall Discusses Drupal Jobs, AI Visibility and Community Participation
During its September Open Townhall on 22 September 2026, The DropTimes moved from its monthly review into a wider community discussion about Drupal jobs, advocacy, AI visibility and participation. Updates from the editorial and community teams led into exchanges with a Drupal Association representative and other participants about how current Drupal work can reach audiences beyond those already following established community channels.
The discussion connected several problems that are often treated separately. Drupal jobs need to be found where employers already publish them, newer Drupal capabilities need credible examples that can reach both people and AI systems, and community knowledge needs channels through which it can travel further. The DropTimes also presented proposals intended to involve community members more directly in event reporting, knowledge sessions and editorial planning.
Ben Peter Mathew reported that The DropTimes published 215 social posts during August and 100 Drupal-related job opportunities. He also said the organisation was connected with 384 organisations across the ecosystem and was exploring automated methods, including feeds, to strengthen its jobs pipeline.
That jobs update prompted Tim Hestenes Lehnen of the Drupal Association to raise the future of Drupal job discovery. Tim said employers had shown little recent use of dedicated destinations such as jobs.drupal.org and described the Association's current jobs offering as having been shut down while another approach is considered. He said aggregating vacancies from external sources was one possibility and asked whether the Association and The DropTimes could compare approaches. Ben proposed continuing the discussion after DrupalCon Rotterdam, leaving the exchange as a possible collaboration rather than an agreed partnership.
Sebin A. Jacob, Editor-in-Chief at The DropTimes, framed the editorial update around trust in code, automation, security processes, institutions and published information. Recent coverage of AI systems, security advisories, Drupal 12 readiness, digital sovereignty and open-source sustainability was used to illustrate a broader editorial principle: reporting should distinguish demonstrated capabilities from experimental work and make uncertainty and limitations visible rather than strengthen claims beyond the available evidence.
Tarun Udayaraj then presented several community-facing proposals under consideration. Event organisers and attendees, he said, often have limited capacity to document parallel sessions while also running or participating in an event. One possible model would involve students from universities near Drupal events or interns supported by participating organisations helping with reporting and documentation. Tarun described the idea as exploratory and invited feedback on how it might work at future events.
Another proposal would establish recurring online knowledge sessions for a global audience, with different Drupal user groups contributing speakers over time. Tarun described a rotating model in which one user group could lead a session before another took responsibility the following month, while The DropTimes supported coordination and promotion. He said the intention was for the programme to operate through community participation rather than solely as a TDT initiative.
The same approach is being explored through the Editorial Working Group. Tarun said community members would be invited to suggest one or two topics each month and participate in feedback and decisions around them. Digital sovereignty had already been identified as one discussion area, while the broader objective was to bring more community expertise into editorial planning.
Tim later previewed an advocacy approach that he said the Drupal Association plans to discuss at DrupalCon Rotterdam. He described an awareness and education problem around Drupal's current capabilities, with some audiences still basing their understanding on versions encountered years ago. One proposal discussed during the Townhall was to organise community communication around quarterly themes, with AI capabilities, Drupal Canvas and easier upgrades among the examples.
Rather than requiring contributors to create everything from scratch, Tim said existing conference sessions, demonstrations, webinars, articles and other material could be adapted and redistributed. He described useful material as “proof points”: concrete demonstrations, case studies, use cases and code examples rather than promotional claims. Such material, he said, could help human audiences understand current Drupal capabilities while also giving large language models more reliable information to encounter.
The discussion also aligned with changes under way at The DropTimes. Tarun said older material was being reviewed with an emphasis on retaining useful and informative content. Sebin said routine external blog summaries had been substantially reduced in favour of fewer original stories involving research, contributor input and stronger evidence. The newsroom was also reconsidering how temporary event-announcement content is handled after events so short-lived material does not outweigh more durable reporting.
Thiemo Müller of Content Sync then shared an update on an AI visibility study being prepared for the Drupal Association. He described the work as examining how AI systems recommend and describe Drupal when users ask about different CMS requirements. According to Thiemo, preliminary analysis showed stronger Drupal visibility in areas such as regulated industries, higher education and government, while visibility was weaker for categories including headless CMS and page builders.
The complete methodology and report were not presented during the Townhall, so those findings remain preliminary and attributed to the study. Thiemo said the project also aims to make community participation easier by providing topic choices, background information and content guidance for people who want to contribute material. Further discussion was planned around DrupalCon Rotterdam.
Taken together, the exchanges shifted the Townhall beyond a monthly performance review. Jobs aggregation, community-led knowledge sessions, editorial participation, evidence-based advocacy and AI visibility repeatedly returned to the same question: how can accurate and useful Drupal information reach the people and systems that increasingly shape technology choices?
Tarun closed the meeting by inviting participants to continue contributing suggestions and taking part in discussions around The DropTimes. He said the Townhall was intended in part to make TDT's work more transparent and bring community input further into decision-making. Several ideas discussed during the session remain at proposal stage, including the jobs collaboration, event-reporting model and recurring knowledge sessions.
Image Attribution Disclaimer: At The Drop Times (TDT), we are committed to properly crediting photographers whose images appear in our content. Many of the images we use come from event organizers, interviewees, or publicly shared galleries under CC BY-SA licenses. However, some images may come from personal collections where metadata is lost, making proper attribution challenging.
Our purpose in using these images is to highlight Drupal, its events, and its contributors—not for commercial gain. If you recognize an image on our platform that is uncredited or incorrectly attributed, we encourage you to reach out to us at #thedroptimes channel on Drupal Slack.
We value the work of visual storytellers and appreciate your help in ensuring fair attribution. Thank you for supporting open-source collaboration!
ASK: Drupal Community Needs Your Support
View all →
Disclosure: This content is produced with the assistance of AI.
Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.
