Feed aggregator
The Drop Times: Shifting Gears: Product Mindset Takes Center Stage at the London Drupal Meetup
The Drop Times: A Quick Dive into Driesnote 2025 from DrupalCon Atlanta
Talking Drupal: Talking Drupal #494 - AI in EDU
Today we are talking about AI in EDU, how it can provide efficiencies, and how you might start using it today with guests Brian Piper & Mike Miles . We’ll also cover External Entities as our module of the week.
For show notes visit: https://www.talkingDrupal.com/494
Topics- How are you using AI with your team at Rochester
- How are you using AI with your team at MIT
- What are the AI policies at your institutions
- On the ingestion side how do you manage consumption
- Tips and tricks to incorporate AI into your work
- Can you talk more about using AI to distribute content outside the web
- Do you have tips for managers
- How have you seen EDUs using AI other than as assistive technology
- What are your favorite tools
- Have you done adversarial testing
- How does AI in Drupal impact EDU
- Where do you see AI in EDU in the future
- Crawler rate limit
- Externalizing costs
- AI for U
- MidCamp 2024 session about YaleSites
- Tools
- Element 451
- Builder io
- Deque Axe Devtools
- Descript
- Opus clips
- Kapwing
- HeyGen
- Synthesia
- Text to video
Brian Piper - brianwpiper.com Mike Miles - Mike-miles.com mikemiles86
HostsNic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Andrew Berry - lullabot.com deviantintegral
MOTW CorrespondentMartin Anderson-Clutz - mandclu.com mandclu
- Brief description:
- Have you ever wanted to connect your Drupal website to an external data source, to include their datasets into the presentation of your Drupal-managed content? There’s a module for that
- Module name/project name:
- Brief history
- How old: created in May 2015 by attiks, though the most recent release is by Colan Schwartz (colan), a fellow Canadian
- Versions available: 8.x-2.0-beta1 and 3.0.0-beta4, the latter of which supports Drupal 10 and 11
- Maintainership
- Actively maintained, latest release was less than a month ago
- Security coverage (though technically needs a stable release
- Test coverage
- Documentation: user guide
- Number of open issues: 77 open issues, 3 of which are bugs against the 3.x branch, though one is marked fixed now
- Usage stats:
- 679 sites
- Module features and usage
- The External Entities module lets you map fields from external data sources to fields on a “virtual” entity in Drupal. This allows for external data to be used with Drupal’s powerful features like Views, Entity Queries, or Search API as well as use your local Drupal site’s theme to theme data from an external source
- The module does provide a time-based caching layer for external entities, but you can also implement a more custom cache expiration logic through custom code
- External entities can also have annotations, essentially Drupal-managed information that will be associated with the external entity, and accessed as a normal field through all Drupal field operations. This could allow you to have Drupal-based comments on information from a different website, for example
- There is a sizeable ecosystem of companion modules, to help you connect to different kinds of external storage, as to help you aggregate data from multiple sources
- In my Drupal career I’ve worked on a number of higher ed websites, and the ability to display externally-managed data is a pretty common requirement, either from an HRIS system to show staff and faculty data, or a courseware solution like Banner. I thought this would be an interesting tangent to today’s topic
The Drop Times: Pipeline Automation with GitHub Actions at DrupalCon Atlanta 2025
The Drop Times: Kicking Off DrupalCon Atlanta: Insights from the Community (Part 1)
The Drop Times: AI in CMS: Power Tool, Not Autopilot
If AI can write, design, and optimize content—what’s left for CMS platforms to do?
That’s the question Dries Buytaert tackled in How AI could reshape CMS platforms. As the founder of Drupal, he knows how content systems evolve—and he believes AI won’t replace CMS platforms but will become a core layer within them.
“I believe the future of CMS platforms is not about replacing humans, but about augmenting them with intelligent capabilities.”
In platforms like Drupal, these changes are already taking shape. The OpenAI module allows editors to generate summaries, titles, and full paragraphs right inside the CMS, speeding up content creation. AI models are also being used to scan content and generate metadata—like taxonomy terms, alt text, or suggested categories—automating tasks that once took manual effort. Large language models are beginning to improve search by understanding context, not just keywords. AI-powered personalization is helping tailor content based on user behaviour, similar to how recommendation engines work on streaming platforms.
These are powerful tools. But here’s the catch: most of these tasks can be done by humans—just not as quickly.
And sometimes, speed isn’t the point.
An AI can write a product description or suggest metadata, but it might miss nuance, voice, or the context behind a piece of content. That’s where human editors still hold the line—especially when it comes to brand consistency, editorial judgment, and ethical decision-making.
Joshua Mitchell echoed this balance in his response post, Some Thoughts About How AI Could Reshape CMS Platforms:
“AI and human editors will increasingly work in parallel, requiring more sophisticated versioning for both content and configuration.”
This is a real technical concern. If AI is generating drafts or modifying layouts, we need version control systems that treat AI edits like any other pull request: trackable, reversible, and reviewed.
Stephen Reny, President and CEO of Acquia, pointed out that the pace of this shift is fast:
“Much of this change will happen in a timeframe that will seem like warp speed compared to prior evolutions. The future is now...”
Michael Anello added another layer: governance.
“Drupal should work to position itself as a leader in AI governance. I’m only comfortable offering AI functionality to clients that keeps a human in the loop (before any 'save' happens.)”
That’s where I agree most. AI is essential—it can handle routine, repetitive tasks in a CMS. But leaning too hard on it means risking quality, trust, and control. We shouldn’t treat AI as a shortcut to replace thinking. Instead, treat it as a power tool: use it with care, skill, and oversight.
Some tasks—like idea generation, auto-tagging, or suggesting layouts—are ideal for AI support. But final content approval, editorial tone, ethical considerations, and big-picture planning? Still best left to humans.
With that, let's move on to the important stories from the past week.
InterviewDiscover DrupalAI-Powered IACK Module Automates Drupal Information Architecture
Keshav Patel Releases Entity Usage Explorer for Accurate Entity Tracking
AI, Nix, and Next-Gen Navigation: What to Expect at DrupalCon Atlanta 2025
Acquia to Host Community Bullseye Bash at DrupalCon Atlanta 2025
Drupal Dev Days 2025 Sees High Demand; Ticket Prices Increase Today
Sponsors Powering the Drupal Community at DrupalCon Atlanta 2025
amazee.io at DrupalCon Atlanta 2025: Talks, AI, and Exclusive Insights
Aten Design Group Gears Up for DrupalCon Atlanta 2025 with Talks, Tools, and Community Spirit
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.
Pages
