drupal

Talking Drupal: Talking Drupal #509 - A WordPresser @ DrupalCon

Today we are talking about DrupalCon, Wordpress, and what a wordpress guy can learn at a Drupal Event with guest Chris Reynolds. We’ll also cover Shortcode as our module of the week.

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

Topics
  • The Pros and Cons of Short Codes
  • Chris Reynolds' Journey to DrupalCon
  • Comparing DrupalCon and WordCamp
  • Funding and Organization of WordPress Events
  • The Collaborative Spirit of the Drupal Community
  • Wishlist for WordPress Features
  • Composer Support in WordPress and Drupal
  • Backward Compatibility in WordPress
  • Challenges with Composer in Drupal
  • Config Management in WordPress vs. Drupal
  • Responsive Image Management
  • User Experience in Drupal
  • Community Collaboration Between WordPress and Drupal
Resources Guests

Chris Reynolds - jazzsequence.com jazzsequence

Hosts

Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi JD Leonard - jdleonard

MOTW Correspondent

Martin Anderson-Clutz - mandclu.com mandclu

  • Brief description:
    • Have you ever wanted your Drupal site to support WordPress-style shortcodes, macros to be used within content? There’s a module for that.
  • Module name/project name:
  • Brief history
    • How old: created in Sep 2010 by Dénes Szabó (denes.szabo) of Tag1
    • Versions available: 2.0.3, which supports ^9.3 ^10 ^11
  • Maintainership
    • Security coverage
    • Test coverage
    • Number of open issues: 30 open issues, 3 of which are bugs against the current branch
  • Usage stats:
    • 13,260 sites (almost 70% are D7 however)
  • Module features and usage
    • For anyone not familiar with WordPress short codes, the documentation describes them as macros, and most often they are used for inserting elements into content such as image galleries, videos, playlists, and more. Shortcodes can also wrap content, however, and it’s possible to nest shortcodes as well.
    • Drupal typically solves the problems addressed by shortcodes using custom HTML elements, as implemented in the media ecosystem, or with the Entity Embed module. I think that shortcodes may also be useful in places where Drupal might also rely on tokens, albeit with an additional module like Token Filter.
    • Gutenberg includes a Shortcode block that can be used as a flexible way to add a variety of elements into a post’s content.
    • I think Shortcodes are an interesting paradigm because they’re really a tool for power users. Instead of providing a UI to browse and choose elements for something like an image gallery, they allow a savvy editor to quickly write a tag that will construct a gallery using numerical ID values.
    • I don’t think this is a tool that most Drupal sites will need, but it could be a really good way for experienced WordPress teams to feel more at home when starting to work with Drupal.

The Drop Times: Belonging by Design

Dear Readers,

Drupal’s strength rests on more than code quality or feature sets. The project’s true resilience comes from the choices it makes about who belongs. As Pride Month closes, the maxim “what you permit, you promote” takes on new urgency. By embedding inclusion into every pull request review, event guideline and policy decision, Drupal lays the groundwork for a community where diverse voices shape its future.

Concrete steps turn that principle into reality. Fei Lauren recalls that “seeing people like me and feeling seen felt so transformative,” a shift driven by initiatives such as hidden-disability sunflower lanyards, family-friendly meet-ups and dedicated channels for neurodivergent contributors. These grassroots practices have sparked regional working groups in Latin America and Africa and transformed the Drupal Diversity and Inclusion Slack space into a hub of shared resources and real-time support.

Sustaining momentum beyond a single month requires ongoing action. Community members can audit site accessibility, propose new support channels and volunteer to host meet-ups that center diverse needs. As Fei urges, “find your people,” because every inclusive choice today becomes the culture Drupal promotes tomorrow.

INTERVIEW

DISCOVER DRUPAL

ORGANIZATION NEWS

EVENT

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 
Alka Elizabeth 
Sub-editor, The DropTimes.

DDEV Blog: How to Downgrade Terminus in DDEV's Web Container and Customize Other Bundled Tools

Image removed.

This guest post is by DDEV community member and Drupal contributor Bill Seremetis and sponsored by Annertech.

DDEV comes bundled with a predefined set of tools, Pantheon's terminus being one of them. The latest releases of terminus are not compatible with older PHP versions like PHP 8.1, though, so we needed to downgrade it inside DDEV's ddev-webserver Docker image.

This guide covers how to downgrade terminus and will also explain how to use the same technique to install additional custom tools.

Please note there are many ways to install packages in a container. We will cover extra Dockerfiles here, but also check webimage_extra_packages and dbimage_extra_packages in your config.yamlfor more details).

Case study: Manually Downgrading Terminus

Terminus dropped support for PHP 8.1 in recent versions, but some of our projects still use PHP 8.1. We had to downgrade the DDEV-bundled version of terminus for those projects by using a custom Dockerfile:

# .ddev/web-build/Dockerfile.terminus # Terminus 4 drops support for PHP 8.1 which we still need ARG TERMINUS_VERSION="3.6.2" RUN curl -L --fail -o /usr/local/bin/terminus https://github.com/pantheon-systems/terminus/releases/download/${TERMINUS_VERSION}/terminus.phar && chmod +x /usr/local/bin/terminus

terminus is just an example here, it could be any command you wish, either because you are running an older PHP version or the bundled version has a bug that ruins things for you.

Installing custom tools

You can obviously use the same techniques to install a variety of custom tools:

# .ddev/web-build/Dockerfile.fzf # fooscript relies on fzf # fooscript lists all your Pantheon projects using a fuzzy finder list ARG FZF_VERSION="0.62.0" RUN curl -s -L https://github.com/junegunn/fzf/releases/download/v${FZF_VERSION}/fzf-${FZF_VERSION}-linux_amd64.tar.gz | tar xvz -C /usr/local/bin/ && chmod +x /usr/local/bin/fzf

Resources

Contribute to DDEV

If you like DDEV then you are welcome to contribute! You can join the Discord channel, create a new DDEV Add-on, or blog about how you use DDEV in your daily workflow. We’re always happy to hear from you on any of our support channels.

Drupal Starshot blog: Marketplace Share Out #7: The MVP Proposal Is Here - What We’re Testing and How to Shape It

The Drupal Site Template Marketplace MVP proposal is now live for community review through 13 July 2025 in the Innovation Issue Queue.

After hundreds of community voices contributed through surveys, Slack, and Real-Time Collaboration sessions, this MVP reflects what we’ve heard: a trusted, flexible, and contributor-friendly ecosystem is possible—if we design it thoughtfully.

What’s in the MVP?

This Minimum Valuable Product (MVP) is a structured experiment targeted for launch at DrupalCon Chicago 2026. Key features include:

  • Up to 15 curated DrupalCMS Site Templates (free and paid), listed on Drupal.org
  • Initial participation limited to Drupal Certified Partners (DCPs) to streamline quality and feedback (expansion beyond DCPs may occur post-MVP)
  • Makers set their own prices and sell directly to users (off-platform)
  • A 10% revenue share from paid template sales and upsell services is directed to the Drupal Association
  • Submission fee: $395 per new listing, with a $250 annual review fee
  • Baseline standards for all templates include:
    • Accessibility (WCAG 2.2 AA)
    • Security and licensing compliance
    • Self-certified GDPR readiness (if applicable)
    • Documentation, maintenance commitments, and user support expectations
    • Regular feedback collection
    • Discoverability features including tags, badges, and demo previews
  • Templates must be built for DrupalCMS, using the Recipes schema, demo content, and XB-compatible themes
  • Templates will undergo automated and manual reviews, conducted by DA Staff (or contractors), with badges and trust indicators displayed where applicable
  • Governance and policy oversight by Drupal Association staff during the MVP; future transitions to community-hybrid models are planned

What the MVP Is Designed to Test

This isn’t just a launch—it’s a test-and-learn cycle designed to validate whether a Site Template Marketplace is desirable, feasible, and sustainable. The MVP will help us understand:

  • What types of templates people adopt—and what makes them valuable
  • Whether direct sales by makers are viable, and what pricing models emerge
  • What kinds of support, trust signals, and governance policies matter most
  • Whether the DA can sustainably operate and review templates at scale
  • How to balance monetization with fairness, contributor credit, and open source values

We’ll use this data to decide whether to expand, adapt, or stop the Marketplace after a 3-6 month MVP.

Submission Fee and Revenue Model

To help fund reviews and platform operations, the MVP includes:

  • $395 USD per new site template listing
  • $250 USD for annual review and revalidation

Site Template Makers:

  • Set their own pricing for paid templates
  • Transact directly with users (outside of Drupal.org infrastructure)
  • Report anonymized data quarterly (downloads, revenue, support volumes)
  • Keep 90% of revenue, while contributing 10% to the Drupal Association based on completed transactions quarterly

Why This MVP Matters

We’ve heard the same call again and again: make it easier to get started with Drupal—without compromising quality or community values. This MVP is a first attempt to meet that need, grounded in clear standards, shared incentives, and real-world feedback.

Let’s test it together—with care, clarity, and Drupal’s best interests at heart.

What’s Next?

  • Public comment period is open through 13 July 2025
  • Marketplace Working Group meets 15 July 2025 to review input and finalize its recommendation
  • The Drupal Association Board will vote 24 July on whether to move forward with implementation

How You Can Help

Your voice is essential to shaping a Marketplace that works for the community. Here’s how to get involved:

Let’s build something that’s good for contributors, great for users, and unmistakably Drupal.

Drupal Starshot blog: Share Out #6: Preparing for the MVP Proposal

We’re excited to announce that a draft Drupal Site Template MVP Marketplace proposal will be released next week for public comment. This version outlines a clear Minimum Valuable Product (MVP) focused on early value, sustainability, and trust.

But first — here’s a look at what’s been shaping the direction of this proposal.

The Business Model Canvas: A Snapshot

To help align on strategy and priorities for the Site Template Marketplace, the Working Group created a Business Model Canvas—a simple tool that breaks down the core elements of how the Marketplace can deliver value and remain sustainable. The Working Group landed on an MVP  model that centers:

  • Primary Users: Low-code/no-code marketers and freelancer agencies
  • Key Value: Trusted, flexible site templates that reduce time-to-launch and lower adoption barriers
  • Revenue Stream: application and referral fees on sales and upsell opportunities to support Drupal Association infrastructure
  • Cost Structure: Low-overhead pilot with both automated and staff-supported review

What We Heard: Shared Priorities Across Surveys and Slack

More than 500 people have shared their perspectives across four surveys—and others have weighed in through Slack discussions, real-time collaboration, and open conversations.

This community and end-user input has been honest, nuanced, and incredibly generous. It has revealed clear patterns, thoughtful tensions, and strong signals of where the community wants to go. So as in advance of the MVP proposal’s release, let’s reflect back what we’ve heard so far.

1. Trust Starts with Quality, Transparency, and Previews

Both in survey responses and in Slack, the message was the same: don’t launch unless people can trust what they’re getting.

Top trust signals:

  • A live demo or preview (most consistently requested signal across all channels)
  • Clear documentation of dependencies and limitations
  • Visible signals of quality (badges, reviews, contributor reputation)

In Slack, people emphasized that even a great theme becomes untrustworthy if it’s hardcoded, inaccessible, or unclear about what it installs.

Show me a demo. Let me see the code. If it’s a mystery box, I won’t touch it.”

2. People Want a Marketplace That Reflects Drupal’s Open Source Values

From contributors and module maintainers to end users and evaluators, we heard a common theme: this effort should feel like Drupal.

  • Governance should be fair, transparent, and enforceable—not performative.
  • Monetization is okay—but must support the whole ecosystem, not just those selling templates.
  • Attribution matters. Contributors want to be credited, not cloned.

If someone else is profiting off my work, I need to at least be recognized.”

Slack also raised the importance of review pathways that aren’t vulnerable to sabotage or bias—suggesting a need for a mix of automation and paid staff to ensure fairness.

3. There’s Real Enthusiasm—for the Right Version of This

End users want this. Freelancers want this. Agencies want this.

  • 85% of end-user survey respondents said vetted templates would increase their likelihood of recommending Drupal.
  • Agencies see templates as a powerful tool for demos, pre-sales, and fast-start projects.
  • Contributors are eager to participate—if it’s worth their time.

Key Tensions: Where We’ll Need to Find Balance

Pricing Expectations Don’t Match (Yet)

  • Users: Many want free or low-cost templates, especially smaller orgs and nonprofits.
  • Contributors: Cite $300–$1,000 as reasonable price points for a complete, maintained, accessible, and documented product.

Slack conversations added nuance: Some contributors are fine with lower prices if the marketplace generates leads or recognition. Others say without fair compensation, they simply won’t participate.

Certification: Signal or Gate?

  • Users want badges that help them sort and trust.
  • Contributors fear certification could slow things down or create an unfair playing field.

Slack participants suggested offering optional badges or tiers, not mandatory certification at launch. A common theme: start lightweight, evolve with real usage.

Monetization: Supportive or Distracting?

There’s broad support for monetization—but only if it’s done with intention.

  • Contributors want clear, fair revenue splits—and protection against cloned or stripped-down copies.
  • Users don’t want to encounter bait-and-switch upsells or gated features.
  • Slack conversations reinforced a desire to avoid WordPress-style chaos, emphasizing community moderation, ranking hygiene, and a meaningful DA role.

This has to feel like Drupal, not like a spammy plugin store.”

What’s Next: Your Turn

The Community public comment period will be open from 27 June 2025 through 13 July 2025. The Marketplace Working Group will meet on 15 July 2025 to review feedback and draft its final recommendation to the board for their go/no-go decision on 24 July 2025.

You will be able to share your thoughts by:

  • Anonymous feedback form
  • Issue queue
  • In Drupal Slack in #drupal-cms-marketplace

Thank You

Thank you to everyone who contributed through surveys, Slack, working sessions, and feedback. Your ideas, critiques, hopes, and flags are shaping this from the inside out. All of this feedback has resulted in a proposal that’s practical, community-aligned, and intentionally minimal.

This Marketplace effort is grounded in community—not just as a value, but as a working method. We’re exploring the Marketplace potential together — ideally, to create something not just to reduce friction for new users, but to grow a stronger, more sustainable Drupal ecosystem for all.

Stay tuned.