fidzu : cms

Today we are talking about Test Driven Development, ebooks, and Drupal with guest Oliver Davies. We'll also cover Juicer Social Feed as our module of the week.

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

Topics

• What Is Test Driven Drupal
• Why Automated Tests Matter
• How TDD Works
• AI and Test Quality
• Balancing Test Coverage
• When to Write Tests
• Why Write the Book
• Why Write an Ebook
• From Email Course to Ebook
• Ebook vs Print Tradeoffs
• Who the Book Helps
• What You Will Learn
• Keeping Content Updated
• Publishing Tools Workflow
• Lessons and Drupal Changes
• Podcast and Future Books
• Mob Programming Explained
• Free Ebook and Wrap Up

Resources

• Juicer io
• Drupal 11: The Upgrade Experience I've Been Waiting For
• codethatships
• Test-Driven Drupal
• Sculpin

Guests

Oliver Davies - oliverdavies.uk opdavies

Hosts

Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Scott Falconer - managing-ai.com scott-falconer

MOTW Correspondent

Martin Anderson-Clutz - mandclu.com mandclu

• Brief description:
  • Have you ever wanted to embed social feeds into your Drupal website? There's a module for that.
• Module name/project name:
  • Juicer Social Feed
• Brief history
  • How old: created in Mar 2026 by Denis Omerović (drupalchille)
  • Versions available: 1.0.2, that works with Drupal 10.3 or 11
• Maintainership
  • Actively maintained (version released today!)
  • No open issues
• Usage stats:
  • 4 sites
• Module features and usage
  • This module embeds an aggregated social media feed from Juicer.io directly into Drupal as a configurable block. It natively supports content from Instagram, LinkedIn, Facebook, X (Twitter), TikTok, Bluesky, YouTube, and more.
  • Traditionally, displaying feeds from platforms like Facebook, X, or Instagram requires creating developer accounts, managing rotating OAuth tokens, and keeping up with constantly shifting API restrictions. Juicer handles all API authentication on its platform, shielding your website from sudden breaking changes by individual social networks.
  • To use this module, you will need an active account on Juicer.io. They offer both free and paid tiers depending on how many sources you want to aggregate and how frequently you need the feed to sync.
  • The module is created and maintained by the official Juicer.io team. That should ensure that the module is closely aligned with the product's features and any potential API changes over time.
  • The embedded feed is made available as a Drupal block, to make it easy to control where it should appear on your site.
  • When placing the Juicer block, the UI exposes several user-friendly settings:
  • Feed Slug: Just paste your unique Juicer feed ID to establish the connection.
  • Post Limit: Control exactly how many items populate initially.
  • Source Filtering: If your Juicer account aggregates five networks, but you only want to show LinkedIn posts on a specific page, you can filter down to a single network right inside the block settings.
  • SEO/Semantic Control: You can set titles/subtitles and choose the exact heading level hierarchy ( through ) to ensure your pages remain semantically correct and accessible.
  • I did get a chance to test out the module and the service today, and I can tell you from experience, it's a huge improvement on having to create and pull in feeds directly. I did notice that the block didn't show up in the Drupal Canvas component library, but I was able to determine that two lines of code to declare the block as FullyValidatable were all that was needed. So I opened a Feature Request to add that, and it was merged in and a new release cut in less than an hour. So it's now Drupal Canvas compatible too!
  • It's worth pointing out that the standard Juicer's embed script loads HTMX, which conflicts with the version of HTMX included in Drupal 11 core. As a result, the module fetches feed HTML directly from the Juicer API and includes a minimal HTMX shim to prevent errors.
  • John, you nominated this module, why don't you start us off by telling us about how you got started using it?

15 Jun 2026 6:00pm GMT

Europe's digital sovereignty debate did not begin with AI or cloud procurement. It developed through surveillance disclosures, privacy law, cybersecurity regulation, platform rules, data governance, and sovereign cloud policy. For open-source platforms such as Drupal, the result is a more demanding environment shaped by hosting choices, supplier dependence, interoperability, compliance, and long-term control.

15 Jun 2026 11:38am GMT

Europe's open source conversation has shifted from principle to infrastructure. The EU Open Source Strategy situates open technologies within a wider digital sovereignty agenda, with a practical question at its centre: whether Europe can reduce its dependence on closed systems while building software that public institutions can reuse, maintain, and trust.

The useful part is also the uncomfortable part. The European Commission identifies familiar weaknesses in the open source ecosystem, including limited long-term funding, difficulty scaling projects, fragmented visibility, limited access to public procurement, and the risk that value created by European contributors is captured elsewhere. That diagnosis moves the discussion beyond code availability and into maintenance, governance, procurement, and business models.

The editorial test is practical rather than rhetorical. Open source becomes strategic only when institutions fund maintainers, accept open-source bids fairly, publish reusable public assets, map dependency risk, and contribute back to the projects they rely on. Without that, sovereignty remains a policy label attached to the same dependency patterns.

Euro-Office shows why the test is hard. The project has reached a first stable release as a web-based office suite, with integrations planned through platforms such as Nextcloud, IONOS Managed Nextcloud, and XWiki. Its practical weight will depend on partner rollouts, production use, format compatibility, governance, and the unresolved licensing dispute with ONLYOFFICE.

For Drupal, the impact is indirect but important. Public-sector and institutional buyers are likely to ask sharper questions about openness, dependency risk, security baselines, procurement fit, and long-term stewardship. Drupal's opportunity is not to claim automatic alignment with European sovereignty goals, but to show evidence through maintained modules, transparent roadmaps, security practices, reusable distributions, open standards support, and credible service ecosystems.

The curated story list for this edition follows the editor's note. Readers can also follow The Drop Times on LinkedIn, Twitter, Bluesky, and Facebook, or join the publication's Drupal Slack channel at #thedroptimes.

Kazima Abbas
Sub-editor
The Drop Times

15 Jun 2026 11:35am GMT