drupal
Nonprofit Drupal posts: May Drupal for Nonprofits Chat
Join us THURSDAY, May 15 at 1pm ET / 10am PT, for our regularly scheduled call to chat about all things Drupal and nonprofits. (Convert to your local time zone.)
We don't have anything specific on the agenda this month, so we'll have plenty of time to discuss anything that's on our minds at the intersection of Drupal and nonprofits. Got something specific you want to talk about? Feel free to share ahead of time in our collaborative Google doc: https://nten.org/drupal/notes!
All nonprofit Drupal devs and users, regardless of experience level, are always welcome on this call.
This free call is sponsored by NTEN.org and open to everyone.
-
Join the call: https://us02web.zoom.us/j/81817469653
-
Meeting ID: 818 1746 9653
Passcode: 551681 -
One tap mobile:
+16699006833,,81817469653# US (San Jose)
+13462487799,,81817469653# US (Houston) -
Dial by your location:
+1 669 900 6833 US (San Jose)
+1 346 248 7799 US (Houston)
+1 253 215 8782 US (Tacoma)
+1 929 205 6099 US (New York)
+1 301 715 8592 US (Washington DC)
+1 312 626 6799 US (Chicago) -
Find your local number: https://us02web.zoom.us/u/kpV1o65N
-
- Follow along on Google Docs: https://nten.org/drupal/notes
The Drop Times: How Kanopi Rebuilt the Hamilton Education Site for Better Access and Engagement
Golems GABB: AI framework in Drupal
Today, Drupal is truly one of the top and most powerful CMS. The introduction of AI and the new features to Drupal reveal its capabilities and incredible prospects for business owners. All these advancements also significantly change the approach to web development and website optimization on the already popular Drupal platform. That is why today, we will discuss the topic of the AI framework in Drupal together.
Specbee: Exposing your API in Drupal - A brief tutorial
PreviousNext: Three features for creating a great website experience
Over the past few years of working on large-scale Drupal projects for government and higher education, I have noticed how successful these new platforms are when developers include three key features in shaping the tech stack.
by ana.beltran / 13 May 2025Rather than diving into the technical details, I want to share my thoughts on why these are essential tools for end-users and editors who manage content daily.
1. Storybook – Uplifting Documentation
As a Delivery Manager, I’ve experienced the importance of having clear and accessible documentation in a project. Storybook is an open-source feature that allows teams to build and showcase components in isolation, making it easier to document and test for stakeholders. From my perspective, it is an excellent tool for stakeholders for the following reasons:
- Component Library - It works like an always-up-to-date document. Each component is documented separately, and its behaviour and variations are well explained. This makes it easier for content editors to browse and understand the behaviours of different components.
- Trial before use (Experimenting) - Developers and stakeholders can interact with each component in isolation, allowing content editors to select the right component to fit the content, which is ideal for the end-user experience. Storybook also enables content editors to test how components display on various screen sizes, facilitating the testing process of multiple devices.
2. Layout Builder – Flexibility and Future-Proofing
Layout Builder is a game-changer for content editors. It works like building blocks. Editors drag and drop component blocks in the design system to fit with the content on a page. This feature allows editors to create and customise page layouts in the website without being locked to just a few pre-built templates. From my experience, it is a useful tool for organisations and users because it is:
- Flexible - It gives content editors and admins more control over how content looks without needing a developer, so content management is faster. Users also benefit as content is better structured, which leads to more engagement and a better experience.
- Future proof - It supports scalability by allowing new components and features to be added over time. It ensures the website stays fresh without requiring a full redesign. In large organisations like universities and government departments, where content is constantly evolving, this level of control is unique and necessary.
Check out the work we’ve done for Cancer Australia using Layout Builder, Storybook and OpenSearch.
3. OpenSearch – Smart Search
Search is a critical feature for any large-scale website. It helps organisations give users the best experience by ensuring they can quickly find the right information. So, what is the difference between an out-of-the-box search and OpenSearch? Think of an out-of-the-box search as looking for a book in a bookstore. You might easily find it if you have the title and author, so simple queries will lead you to the source. However, trying to find the best cycling route in a new town is an entirely different task. You’re not just after a title ‘keyword’ but a few additional parameters or ‘filters’ like distance, elevation and terrain. That type of customisation is exactly what OpenSearch offers. It understands the website’s content structure and the users’ queries, and returns the best content match. It's a powerful tool from a stakeholder perspective, because it:
- Organises information - Organisations can customise search results based on their needs. For example, they can rank articles higher than factsheets to prioritise the most critical content to appear first.
- Understands how people search - No two users search for information in the same way. Some use keywords, while others use complete sentences. OpenSearch supports these various behaviours by providing functionality such as autocomplete, synonyms, and spell check. This will ensure users find what they are looking for, even if they use misspelled words or incomplete sentences.
While these are only a few key tools for elevating the user experience, I hope this blog has helped you understand more about some of the tools we use and why I consider them to be the backbone of all new projects. If you have any questions or would like a demonstration of how we can use them in your new website, please feel free to reach out!
The Drop Times: Sowing Opportunity, Reaping Innovation: George DeMet on the Power of Inclusive Drupal Development
Drupal Starshot blog: Marketplace Share Out #4: Building Trust, Governance, and Real-World Value
In our previous share out, we focused on why contributors might engage in a Marketplace and the kinds of value they’re looking for. Since then, we’ve turned our attention to something even more foundational—trust.
If we want the Marketplace to succeed, contributors, agencies, and end users must believe:
- Templates are high-quality and secure
- Contributors are treated fairly and transparently
- There are clear, enforceable standards for what gets listed
That’s the work we’re deep in now.
What Builds Trust?
Across our first two surveys, last week’s Slack prompt, and the Hopes & Fears Jam conducted at the Quarterly Drupal Certified Partner Webinar, three critical trust signals have emerged:
1. Clear Quality Standards—Published and Enforced
Templates must meet defined standards for code quality, security, accessibility, and UX. Contributors want to know what “good” looks like before they invest time; end users want confidence before they adopt.
If the Marketplace becomes a dumping ground for mediocre or insecure templates, it will actually hurt Drupal.”
"Templates should be clearly rated on accessibility, code quality, and what modules they’re pre-styled for.”
The Week #5 prompt in #drupal-cms-marketplace dives directly into this question:
“What accessibility, security, or coding standards should be required for free and/or paid site template listings—and how should they be verified?”
We’d love to hear your thoughts!
2. Trustworthy Governance and Accountability
Policy alone doesn’t build trust—clear enforcement and transparency do. People want to know someone is actively ensuring fairness and protecting the ecosystem.
Governance modeled after the Security Team would give me confidence someone’s watching the store.”
"What’s the dispute process if I think something’s plagiarized or violates guidelines?”
The Marketplace Working Group met last week to begin shaping a draft governance model grounded in your feedback. While still early, this work is focusing on:
- Who might set and enforce Marketplace rules
- How listings might be reviewed and approved
- How disputes and appeals may be handled
-
What may be required to maintain a listing over time
3. Transparency Around Recognition and Revenue
The Marketplace must offer both recognition and a fair value exchange. Contributors want clear attribution, visibility for upstream maintainers, and thoughtful revenue models that strengthen—rather than undermine—Drupal’s open-source values.
I don’t mind people making money—but I want to know how it flows back to the people maintaining the ecosystem.”
Progress on Governance: Turning Feedback into Structure
The Marketplace Working Group’s emergent governance framework is designed to create a Marketplace that is socially, technically, and financially responsible—and deeply aligned with Drupal’s open-source mission.
The scope of the framework includes:
- Submission and Review Guidelines: Clear public standards for what qualifies as a free, certified, and/or paid template—including accessibility, security, and code quality.
- Monetization and Revenue Sharing Models: Exploring how paid listings can fairly compensate contributors while also supporting module maintainers, the DA, and the ecosystem as a whole.
- Security and Quality Assurance: Establishing review processes to certify templates and flag those that are outdated or poorly maintained—ensuring users can clearly see the trust signals they need.
- Dispute Resolution and Appeals: Drafting a lightweight, transparent approach to handling conflicts fairly and consistently.
- Transparency and Community Feedback: Creating a clear process for proposing and reviewing policy changes with full community input.
This work is just beginning, and ongoing feedback will help shape what comes next.
How You Can Get Involved
Your input is critical to shaping a Marketplace that reflects Drupal’s values and strengthens our ecosystem. Here’s how to get involved this week:
- Take Survey #3: Marketplace Governance and Community Values.
Help us understand your expectations for fairness, openness, and revenue models. - Join the Slack Discussion – Share your views on Slack in #drupal-cms-marketplace:
“What accessibility, security, or coding standards should be required for free and/or paid site template listings—and how should they be verified?” - Participate in the Ecosystem Roundtable – Participate in the Drupal Certified Partner and Agency Roundtable to share your perspective directly: 15 May 2025 | 15:30 UTC Register now.
Talking Drupal: Talking Drupal #502 - TD Cafe #001 Martin and Jake
Welcome to the first episode of Talking Drupal Cafe.
Join Martin and Jake as they delve into an insightful conversation exploring the challenges and responsibilities associated with being a module maintainer. Discussing project types, the significance of sandbox modules, the impact of Drupal CMS, and the role of AI tools, they highlight issues around burnout, sustainability, and community support. Discover how the Drupal community can better support maintainers and the importance of continued contributions. This episode also touches on upcoming conferences and the significance of face-to-face interactions in the Drupal community.
Martin Anderson-ClutzMartin is a highly respected figure in the Drupal community, known for his extensive contributions as a developer, speaker, and advocate for open-source innovation. Based in London, Ontario, Canada, Martin began his career as a graphic designer before transitioning into web development. His journey with Drupal started in late 2005 when he was seeking a robust multilingual CMS solution, leading him to embrace Drupal's capabilities. (mandclu.com)
Martin holds the distinction of being the world's first Triple Drupal Grand Master, certified across Drupal 7, 8, and 9 as a Developer, Front-End Specialist, and Back-End Specialist. (TheDropTimes) He also possesses certifications in various Acquia products and is UX certified by the Nielsen Norman Group. (mandclu.com)
Currently serving as a Senior Solutions Engineer at Acquia, Martin has been instrumental in advancing Drupal's ecosystem. He has developed and maintains several contributed modules, including Smart Date and Search Overrides, and has been actively involved in the Drupal Recipes initiative, particularly focusing on event management solutions. (mandclu.com) His current work on the Event Platform aims to streamline the creation and management of event-based websites within Drupal. (TheDropTimes)
Beyond development, Martin is a prominent speaker and educator, having presented at numerous Drupal events such as DrupalCon Barcelona and EvolveDrupal. He is also a co-host of the "Talking Drupal" podcast, where he leads the "Module of the Week" segment, sharing insights on various Drupal modules. (mandclu.com) Martin's dedication to the Drupal community is evident through his continuous efforts to mentor, innovate, and promote best practices within the open-source landscape.(TheDropTimes)
Jacob RockowitzJacob is a prominent figure in the Drupal community, best known for developing and maintaining the Webform module—one of the most widely used and feature-rich form-building tools in the Drupal ecosystem. His work has significantly enhanced Drupal's capabilities in form creation, data collection, and user interaction.
Rockowitz began his Drupal journey while working as a consultant for Memorial Sloan Kettering Cancer Center (MSK), where he spent over 18 years. Facing the need for robust form functionality during MSK's early adoption of Drupal 8, he created YAML Form, which later evolved into the Webform module for Drupal 8 . This module has since become integral to many Drupal sites, offering extensive features for form management.(design4drupal.org)
Beyond Webform, Jacob has contributed to other projects like the Schema.org Blueprints module, aiming to improve structured content modeling in Drupal. He is also an advocate for open-source sustainability, often discussing the importance of community involvement and the challenges of maintaining large-scale open-source projects .(talkingdrupal.com, jrockowitz.com)
As an active member of the Drupal community, Rockowitz frequently speaks at events such as DrupalCon and New England Drupal Camp, sharing his insights on module development and community engagement . He maintains a personal blog at jrockowitz.com, where he writes about his experiences and thoughts on Drupal development.(Drupal)
For show notes visit: https://www.talkingDrupal.com/502
Topics- Introduction to Project Maintenance
- Types of Projects and Their Significance
- Sandbox Modules and Work Projects
- Passion Projects and Inherited Projects
- Challenges in Managing Multiple Modules
- The Role of Recipes in Project Management
- AI and Automation in Project Maintenance
- The Future of Project Maintenance and Contributions
- Evolving Drupal and Community Contributions
- Enterprise Features and the Trash Module
- Marketplace and Site Templates
- AI and the Future of Web Development
- Contribution Credits and Bounties
- Guiding Users and Module Selection
- Drupal Adjacent Solutions
- Sustainability of Contribution
- The Importance of Community Engagement
Martin Anderson-Clutz - mandclu.com mandclu Jacob Rockowitz - jrockowitz.com jrockowitz
mandclu: Smart Menu Links: Drupal navigation with the power of Views
In my recent work on the Drupal Event Platform, one of the most ambitious changes has been changing the architecture to support multiple events. That means that an annual Drupal camp can retain the content of previous years while collecting session submissions for an upcoming event. It also means that the platform can support multiple events per year if needed, similar to events.drupal.org.
mandclu May 12, 2025 - 11:32amTags
Pagination
- Previous page
- Page 23
- Next page