The DropTimes Townhall Explores Reaching Audiences Beyond Drupal

Audience Research, Broader Technology Reporting and Publishing Partnerships
The DropTimes Townhall Report graphic titled "What Makes a Technology Story Worth Reading?" features a screenshot of an online meeting with Drupal community members alongside an illustrated network of connected people and technology. The text reads "Reporting that begins with practical problems, tests assumptions and examines difficult evidence took centre stage in The DropTimes' November Townhall."

Community members proposed leading with broader technology problems rather than Drupal branding during The DropTimes' Open Townhall on 17 November 2026. The online meeting, scheduled for 15:30 UTC (21:00 IST), brought together editorial and marketing updates, Drupal advocacy plans and suggestions for reaching audiences outside the existing Drupal community.

Alex Moreno, Paul Johnson and Norah Schrum discussed how coverage of AI governance, content management and digital experience could introduce Drupal to professionals who are not actively searching for the platform. Their proposals included using website traffic data to identify relevant subjects, publishing in established technology outlets and collaborating with contributors working across the wider open-source ecosystem.

Community Members Propose Problem-Led Reporting

Alex Moreno suggested that The DropTimes share statistics on where its website traffic originates and what readers are searching for. He argued that these findings could help the publication identify subjects with relevance beyond the Drupal community.

Rather than repeatedly leading with Drupal, Alex suggested reporting on problems people are trying to solve, including challenges involving artificial intelligence and editorial workflows. Drupal could then be introduced where its capabilities offer a relevant response.

Paul Johnson supported the proposal, describing work within the Drupal AI Initiative to develop what its participants call "Drupal-adjacent" content. He cited an AI governance white paper co-authored by Aidan Foster of Foster Interactive and plans for a webinar intended to attract people interested in the subject rather than Drupal specifically.

Paul also discussed the Drupal AI Summit in Paris, explaining that some session titles and content had been adjusted to appeal to attendees interested in wider technology questions. He suggested that The DropTimes experiment with coverage of content governance, usability and user experience, subjects relevant to professionals delivering digital experiences across different platforms.

Norah Schrum encouraged community members to contribute to publications outside the Drupal ecosystem. She reported that her application to contribute to CMSWire had been accepted and that she was developing her first article for the publication.

Norah said the opportunity was particularly relevant to broader open-source commentary and encouraged others to explore similar outlets. During the meeting chat, she identified Smashing Magazine, The New Stack, LogRocket Blog, DEV Community and HackerNoon as potential publishing channels.

Her proposal focused on contributing useful articles about industry problems, with Drupal introduced only where relevant, rather than using external publications primarily to promote the platform.

Another participant, Shibin Das, highlighted an earlier The DropTimes article about a module Vimal Joseph developed to solve an internal image-display problem. Shibin suggested that practical accounts of how a problem was solved could offer a useful alternative to articles organised around a module's feature list.

Tarun Udayaraj, who hosted the meeting, welcomed the suggestions. He agreed that audience statistics could help inform future reporting and proposed further discussions with Alex, Paul, Norah, Shibin and other interested community members. The ideas remain proposals for further development rather than an adopted editorial policy.

Newsroom Update Focuses on Research and Accountability

Allen Jason delivered prepared remarks on behalf of Sebin A. Jacob, Editor-in-Chief of The DropTimes. The update continued the discussion about the publication's change in editorial approach, first outlined at the October Townhall on 28 October 2026.

The remarks explained that The DropTimes had moved away from producing approximately 13 to 15 stories a day towards fewer articles supported by more research, source checking and editorial attention. The presentation examined what that change had meant during the three weeks since the previous meeting.

One example was the publication's investigation into Drupal's CMS market share. Using W3Techs figures for websites with an identifiable content management system, the investigation examined a decline from 5.1% in 2015 to 0.9% in November 2026. The prepared remarks emphasised that the figures should not be treated as a complete explanation of Drupal's position.

According to the prepared newsroom presentation, an internal analysis of the dataset examined found that listed maintainers accounted for 66.9% of recorded Drupal core credit. This is a result from the cited analysis, not a general measurement of all Drupal contribution. The central questions concerned how maintenance work, individual contributions, employer recognition and sponsorship are represented.

Further examples included Drupal's planned reduction in standard minor-release security support to eight months beginning in 2027 and the difficulties of turning Drupal 11 compatibility patches into official contributed-module releases. The presentation distinguished technical defects, unsupported projects and missing release permissions rather than treating every delay as maintainer neglect.

The newsroom also reviewed its reporting on Drupal AI tools, Drupal Canvas and migrations. Sebin's remarks stressed the value of practical testing, citing work by Vimal Joseph and Emily Mathew that documented implementation steps and actual software behaviour.

Additional reporting covered AI-generated code, government use of open source, security incidents and the consequences of funding uncertainty for nonprofit organisations. The update also described a more selective approach to release announcements, with original research prioritised when a second article would add information beyond the primary source.

October Reporting and Community Outreach

Ben Peter Mathew presented the October social media and marketing report. The DropTimes ended the month with 9,965 followers, adding 104 during the reporting period. Its content generated 105,353 impressions and 11,662 engagements, according to the figures in the presentation.

According to Ben’s report, the team published 233 social media posts during October. Its DrupalCon Rotterdam coverage accounted for 50 articles and 123 social media posts, which generated approximately 50,000 impressions.

Four community members contributed written articles, while 12 others supported the Rotterdam coverage by sharing photographs, conference updates and information about the Driesnote, Women in Drupal Awards and Splash Awards.

Ben reported that The DropTimes was collaborating with 391 organisations across the Drupal ecosystem, including three added during the month. The team provided direct marketing and branding support to 20 organisations and assisted another ten in promoting community-focused initiatives.

According to the October presentation, the publication also listed 80 Drupal-related job opportunities, promoted 13 events and partnered with two event organisers. Its event promotion activities included highlighting 20 speakers and ten sponsoring organisations.

Ben said the team planned to continue its module spotlight series, work more closely with maintainers and make it easier for organisations to share Drupal job openings. Media outreach would also focus on technology publishers and local news organisations capable of introducing Drupal-related stories to wider audiences.

Kazima Abbas presented the editorial team's October activity. Her subject-category report included 55 pieces covering Drupal modules, security updates and associated platforms and tools. She also reviewed event coverage, external contributions, case studies and interviews.

For November, Kazima identified improving editorial quality, expanding contributor outreach and covering Drupal Canvas, the Drupal AI Initiative and Drupal Advocacy as priorities. The team also plans more interviews with maintainers and contributors, alongside follow-up coverage of NEDCamp and BADCamp and reporting on DrupalCamp Spain and Evolve Digital.

Drupal Advocacy and Wikipedia Updates

Tarun presented updates on The DropTimes' participation in the Drupal Advocacy Program. He discussed opportunities for external writers and media partners to apply for advocacy credits for qualifying contributions, subject to the programme's review requirements.

He also revisited an initiative to review outdated Drupal-related information on Wikipedia. The team has prepared an open document listing existing topics and possible areas requiring attention, but limited staffing has slowed coordination.

Responding to a question from Norah, Tarun clarified that the initiative concerns Wikipedia.org rather than the Drupal.org wiki. He reported that a local Wikimedia user group had offered to train community members in editing and maintaining Wikipedia content.

The proposed work would require contributors to follow Wikipedia's sourcing, neutrality and conflict-of-interest requirements. The discussion did not establish a completed editorial programme or a timetable for updating individual articles.

Tarun also discussed efforts to reach government, nonprofit and media audiences and connect with broader open-source communities. He said discussions had begun with Drupal Association representatives Ryan and Tim about coordinating advocacy-related content. Ryan had agreed to share information about monthly advocacy themes to support further planning.

Norah offered to participate in those discussions and help identify possible connections with external publishers. Tarun also invited additional community members to contribute to the planning process.

The meeting concluded with participants agreeing to explore the suggestions further, particularly the use of audience data, reporting on broader technology problems and collaboration with publishers outside the Drupal ecosystem. The discussion left implementation details open for subsequent planning.

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.

Upcoming Events