Who are you? (biography/background)
I am Alexander Varwijk (Kingdutch on Drupal.org), born north of Amsterdam and currently living in the Dutch city of Enschede, near the German border. My programming journey began at a young age after seeing how an au-pair used Perl to maintain a Drum & Bass fan website. My first creation was a simple terminal calculator in Perl, but I quickly discovered the magic of building websites, starting with Dreamweaver before adding interactivity using PHP 4.4.
My path with Drupal began in 2012: for the new website of a local sports association I was looking for a tool that allowed me to build overviews for club members, teams, and matches. After building the first features of the website using Drupal 7 I was eager to learn more about the framework and its community, which led me to DrupalCon Prague in 2013. There, by chance, I was connected to other people from Enschede: my future colleagues at Open Social.
At the same time as getting to know Drupal I started my study of Electrical Engineering. I ended up spending more time with various committees for my study association as well as a two year board membership as president of the Vestingbar – a student run bar open 364 days of the year.
In 2016 I dropped out of my Electrical Engineering study to make room for my entrepreneurial interests: I started a craft-beer subscription service called Ontdekbier (using Drupal Commerce for the website); I started a study of Business Administration, and I joined GoalGorilla during their transition from Drupal agency to the product company now known as Open Social.
My craft-beer subscription service is no longer around. After meeting the marketing manager from Heineken at a beer sommelier course and learning of their many millions of euros of funding for BeerWulf in a bid to capture the craft-beer e-commerce market, I decided that that was not a market player I could compete with.
I'm still with Open Social, where as Technical Architect at Open Social, I help power some of the world's most impactful organizations through Drupal-based collaborative platforms, including the European Commission, World Bank, United Nations, and Greenpeace International.
In my time off I still enjoy programming, such as introducing async capabilities to Drupal. Besides that I love airplanes, poker – a source of global friendships, reading, speaking at conferences, and travelling. Interests that complement each other well. When I'm back at home I enjoy cycling with friends and I volunteer my time to help organize a local music festival every year.
Why are you running for a board seat at the Drupal Association? (mission/motivation)
Drupal is an amazing framework for modern day connected applications. Its community is vibrant and chooses the direction of the project through choosing where it decides to contribute. The Drupal Association as I understand it plays a vital role in ensuring Drupal's longevity and ensuring a healthy community by supporting the community and its contributors.
Three main aspects that excite me and motivate me to join the Drupal Association board are: Developer Advocacy and promoting Drupal outside our community; increasing attractiveness of Drupal Association sponsorship for organizations using Drupal as a tool; and the forming of a federated system of Drupal Associations to coordinate global and local tasks in supporting and growing our community.
While talking with developers at conferences outside of the Drupal community, their image of Drupal often does not seem to reflect the current state our framework offers. At the same time, developers working with Drupal seem to underestimate their options of sharing our message with people outside of our community.
As a Drupal Association board member I would like to initiate or boost a developer advocacy program that connects the amazing speakers that we have within the Drupal community to great non-Drupal conferences. Expanding our outreach efforts promotes Drupal as a technical tool and helps modernise its image while simultaneously allowing our community to learn from other technologies and tools.
The Drupal Association pitch for sponsorship is currently focused in large part around visibility within the Drupal community as a Drupal service provider. As a Drupal Association board member I want to help expand the pitch with one that appeals to companies that use Drupal as a development framework but do not resell Drupal itself, thereby growing the funding for the Drupal Association and the Drupal project.
The International Drupal Federation Initiative provides exciting opportunities. Many local associations already exist that know how to engage their local communities and grow usage and contributions within those spaces. There are also tasks that transcend national borders and can benefit from global cooperation. Developer advocacy, as well as crafting a clear and compelling story of why the individual associations and an overarching international association are important to any organization using Drupal, are prime examples.
Why should members vote for you? (qualifications)
My 13 years of experience in the Drupal ecosystem have shown me both the community's incredible strengths and the areas where we can improve. My contribution would be a combination of open source development experience – inside and outside of Drupal, a business administration background and my drive and energy to promote Drupal. I am able to evaluate the work of the Drupal Association through a strategic lens and translate the community's needs into actionable plans. My journey from building a local sports club
website to architecting platforms for organizations like the UN and European Commission has given me perspective on the broad spectrum of Drupal users and their diverse needs.
As a conference speaker and (co-)maintainer of multiple Drupal projects, I try to give back to the community that has given me so much. As a member of the board of the Drupal Association I can use my experience of turning ideas into workable solutions to further contribute to the community's growth and longevity.
I believe I can contribute meaningfully to the challenges facing Drupal and the Drupal Association. As our framework competes in an increasingly complex landscape, we need thoughtful approaches to marketing, funding and community growth. My entrepreneurial and product experience, combined with deep community involvement, gives me tools to help navigate the balance between innovation and stability, between open-source values and practical sustainability, that the Drupal Association must maintain.
After weeks of listening, prompting, and pattern-spotting, we’re entering a new phase. The big questions are becoming sharper. The conversation is shifting—from what might be to what must be.
Our early exploration surfaced a wide range of motivations, risks, and hopes for a Drupal Site Template Marketplace. The signal was clear: there’s strong belief in the potential—if we build it in a way that strengthens the ecosystem, not fragments it.
As part of this shift from the breadth of exploration and to the depth of early structure, we’re moving to a biweekly share out cadence. This Share Out #5 update highlights what’s emerging from Slack Prompts #5 and #6, insights from Survey #3 on Governance and Fairness to inform first drafts of the Lean Business Model Canvas and Governance Framework—early scaffolding for what’s to come.
From Divergence to Convergence
In design thinking, there’s a natural rhythm between divergence—where we explore widely—and convergence—where we begin to shape and prioritize. We’re now entering that second phase.
The goal is not to lock down answers prematurely, but to begin assembling the scaffolding that can support real-world testing, feedback, and evolution.
We’re asking:
What makes a template worth trusting?
What makes one worth paying for?
What kinds of governance and community signals need to be in place from day one?
What We’re Hearing: Trust, Value, and the Shape of a Marketplace
Standards Build Trust
In response to Slack Prompt #5, contributors agreed that establishing baseline quality, accessibility, and transparency standards is essential.
Automation was broadly supported—but not blindly. There’s growing recognition that automated checks are necessary but not sufficient, especially for more nuanced requirements like semantic markup or keyboard navigation.
Most scanners will find 200 security bugs in Drupal and maybe 1 is real. Human review is still required.”
“Let’s at least show the automated results transparently and let buyers decide.”
Contributors are also thinking ahead about user expectations:
Paid listings should absolutely meet higher standards—users will expect it.”
These insights inform the governance framework’s approach to certifications, self-attestations, and recurring review cycles for paid listings.
What Makes a Template Worth Paying For?
Slack Prompt #6 helped unpack the value exchange at the heart of the Marketplace. Why would someone purchase a GPL-licensed template?
The answer: time savings, trust in the “official” source, and ease of setup.
The confidence that comes from knowing the template came from an official, trusted source like the DA is huge."
"One-click demos for themes... that’s my #1 trust signal.”
Participants also cautioned that separating the template from hosting or support could confuse non-technical buyers, especially those coming from SaaS ecosystems.
“Too many hosting choices at signup may mirror Mastodon’s ‘pick a server’ confusion.”
This feedback is pushing us to consider default hosting pathways, bundled services, and better “first-use” experiences.
Fairness, Recognition, and Governance
Our third community survey zeroed in on values: fairness, recognition, and trust.
Contributors emphasized the importance of clear expectations and governance guardrails—especially when money enters the picture.
“Revenue must also support the ecosystem—modules, infrastructure, DA.”
Many participants supported the idea of tiered models, where certified templates provide extra confidence:
“Even free templates should meet basic accessibility and security requirements if they’re hosted on Drupal.org.”
Recognition also matters:
“Templates should be rated based on feedback… great to know why someone considers a product to be 1 or 3 stars.”
That insight is helping shape how we design review systems that are credible, transparent, and helpful—without opening the door to spam or bias.
Early Structures Taking Shape
Informed by three surveys, one RTC session, and six slack discussions worth of community research combined with competitive research and discussions with Drupal’s intellectual property attorney, the Marketplace Working Group is now in active development on two core artifacts:
Lean Business Model Canvas
A one-page tool that outlines the key elements of an initiative—like its users, value, and sustainability—to guide strategy and iteration. We're using it to map how the Marketplace creates, delivers, and shares value across contributors, agencies, end users, and the Drupal Association.
Governance Framework (Draft)
A foundational structure that defines how decisions are made, roles are assigned, and policies are enforced. Our draft outlines submission criteria, listing types, maintenance expectations, dispute resolution, and contributor recognition—building the rules and responsibilities needed to support a fair, trustworthy Marketplace.
This scaffolding is not final—it’s a living structure meant to evolve through our continuing research, feedback and community review. Nonetheless, it does feel exciting to see it all start to take shape!
What’s Ahead
Pilot Planning: Testing incentive and governance structures in collaboration with Drupal Certified Partners and other agency participants.
Governance Draft: A public request for comment (RFC) on the governance framework will launch this summer.
MVP Quality Standards: Defining a small, automatable set of checks for accessibility, security, and licensing for free templates.
How You Can Stay Engaged
💬 Join #drupal-cms-marketplace on Slack
Each week, there's a new prompt to explore a key question as we define this Marketplace.
🎧 Listen to Talking Drupal #504
On this week's podcast, we discussed the vision, opportunities, and challenges of creating a trusted, high-quality Drupal Site Template Marketplace that supports adoption, contributor incentives, and community values without compromising open-source principles.
Thanks to all who are continuing to shape this work with insights, critiques, and care. What we build next will depend on the strength of the scaffolding—and the people who show up to co-create it.
We’re excited to announce a big step forward for user experience in Drupal Core: the creation of the new UX Manager role within the core leads team. This is a foundational move toward UX-driven development, where user experience is embedded from the start, not added at the end.
Historically, UX responsibilities in Drupal Core were shared across different roles, often falling under product management. But in practice, UX input has often arrived late, focusing on small usability tweaks rather than shaping the overall experience.
By creating a dedicated UX Manager role, we’re making sure UX has a clear voice — from early feature discussions to final design decisions. This will help us build more intuitive, cohesive, and accessible experiences for everyone using Drupal. We’re also laying the groundwork for the future: supporting more UX practitioners to contribute to Drupal and from there, grow into decision-making roles, strengthening our design contributor community, establishing a stable UX testing process, and making onboarding easier for designers and researchers.
For now, this role will be co-led by Emma Horrell and myself, Cristina Chumillas.
Emma is the UX Research Lead for Drupal CMS and has shaped many aspects of the project through her work researching target audiences, testing features, and helping reduce “Drupalisms.” Her research expertise will continue to help us align Drupal with real user needs. Many thanks to the University of Edinburgh for supporting her continued contributions.
I’ve been the usability topic maintainer for years and currently serve as Product Design Lead for Drupal CMS and Drupal core Front-end Framework Manager. I’m looking forward to helping embed UX more deeply into how Drupal Core is defined, designed, and built.
This is just the beginning. If you’re interested in improving Drupal’s experience, join us in the #ux-working-group on Drupal Slack — and help us put UX at the heart of Drupal’s future.
Still on Drupal 7? You’re not alone, but it’s time to plan ahead! Thousands of websites still run on Drupal 7. And while Dropsolid offers extended support, the reality is clear: Drupal 7 is at the end of its innovation cycle. The question is no longer if you should move, but how and when.
At Dropsolid, we guide organizations in making the best choice: whether that means extending support on Drupal 7, migrating to modern Drupal (currently Drupal 11), embracing the power of Drupal AI or a combination of this.
1. Roadblocks of Migrating to modern Drupal
Migrating from Drupal 7 to a modern Drupal version is a big step, and many site owners face challenges that delay that move. These are the most common migration roadblocks:
Technical Hurdles
Complete theme redesign
Complex content and media structure rework and data migration
Custom modules and thrid-party integrations often require major rewrites
Organizational Barriers
Limited development capacity
Budget constraints
Competing priorities across teams
We get it. These challenges don’t make migration simple. But don’t worry, there’s a solution that can bridge the gap and give you more time to prepare: Drupal 7 Extended Support (D7ES).
2. Extend Support - The Bridge
Drupal 7 Extended Support allows your team to maintain security and performance while planning a future-ready migration.
At Dropsolid, we provide Extended Support for your Drupal 7 website. Unlike many other firms, we have a large team of Drupal 7 experts on board with over 620 years of Drupal experience. And we are fully committed because we currently support a lot of Drupal 7 applications.
What we offer:
Security patching and monitoring
Infrastructure support and optimization
Compatibility workarounds
Time to prepare for a clean migration
We can offer you more time, which you can use to:
Reassess your digital goals
Inventory and audit your site components
Explore D10 and Drupal AI
Note: At Dropsolid, we don’t consider Drupal 7 Extended Support as a permanent solution, but as a bridge to your next digital chapter. We can help you determine your Digital strategy and align this through our open DXP.
The Dropsolid Drupal 7 Extended Support Program is the perfect temporary solution for you. It allows you to consider your next steps and take away migration pressure.
3. From Drupal 7 to Drupal AI - The Future
As extended support is not a long-term solution, looking into migrating to modern Drupal is essential. Dropsolid offers expert Drupal migration services to bring your website up to date with modern standards and technologies, making it faster, more secure, and more scalable. We understand that every business is unique, and we tailor our migration approach to your specific needs and challenges.
Looking beyond modern Drupal? There’s an exciting future waiting with Drupal AI! This integration and automation into your CMS unlocks a new level of efficiency, personalization, and innovation.
What can Drupal AI do?
Imagine the power of AI-assisted content generation, smart tagging, and intelligent content recommendations—all within your CMS. Drupal AI has new tools to:
Boost content velocity by generating drafts, suggestions, and ideas based on existing content and keywords.
Improve UX by offering intelligent recommendations tailored to user behavior, interests, and needs.
Automate routine time-intensive tasks such as tagging, categorizing, and content updates, reducing the manual effort your team needs to put in.
For example, on a Drupal e-commerce site, AI can dynamically adjust product recommendations based on user behavior, increasing conversions and personalization. Content editors could have AI-generated suggestions ready to publish based on traffic and preferences.
As your website evolves, embracing Drupal AI can be the next logical step after migrating to modern Drupal. It gives you the ability to stay ahead of trends and deliver an exceptional, personalized experience for your users.
4. Ready to Take The Next Step?
Not sure which path is right? You don’t have to decide alone. Whether you need more time on Drupal 7 or are ready to innovate, we help you:
Stay secure on Drupal 7 (for now)
Build a migration roadmap for modern Drupal
Discover Drupal AI's potential
We also support organizations in redefining their digital strategy—integrating a full Digital Experience Platform (DXP) and even AI . This ensures your next digital chapter isn't just an upgrade, but a transformation.
Get in touch with us and have a call with our Drupal experts. We’ll assess your current setup, explore your goals, and help you choose the smartest path forward.
Contact us → https://dropsolid.com/en/contact
The United Nations Digital Technology Network has recently adopted a new set of Open Source Principles to promote collaboration and drive open source adoption within the UN and around the world. These principles position open source as the default approach for digital projects, encourage contributions back to the ecosystem, foster inclusion and community building, and much more.
The Drupal Association is proud to endorse these principles. As the non-profit organization that supports the Drupal project, already the standard technology platform for the United Nations’ web presence, we wholeheartedly believe that these principles will advance both digital sovereignty and the long-term sustainability of the open source ecosystem.
The UN Open Source Principles
Open by default: Making Open Source the standard approach for projects
Contribute back: Encouraging active participation in the Open Source ecosystem
Secure by design: Making security a priority in all software projects
Foster inclusive participation and community building: Enabling and facilitating diverse and inclusive contributions
Design for reusability: Designing projects to be interoperable across various platforms and ecosystems
Provide documentation: Providing thorough documentation for end-users, integrators and developers
RISE (recognize, incentivize, support and empower): Empowering individuals and communities to actively participate
Sustain and scale: Supporting the development of solutions that meet the evolving needs of the UN system and beyond.
In June 2023, the Drupal Association adopted its own Open Web Manifesto, which guides both our non-profit operations and the Drupal open source project. The manifesto is grounded in five core principles and three essential requirements.
The principles are that the open web:
is built on freedom: No permission is required to learn, build, or innovate. Anyone, anywhere, can contribute to its growth.
is defined by decentralization: No single person or entity controls the open web.
thrives on inclusion: Everyone, regardless of background, identity, ability, wealth, or status has a place on the open web as a user, creator, architect, or innovator.
requires participation: It is a shared resource and a shared responsibility, sustained through collective effort.
exists for empowerment: It is driven by humanity’s pursuit of knowledge, connection, and progress, and is strengthened by each individual’s right to choice, privacy, and security.
The requirements are that the open web must:
protect — not exploit — personal data and public discourse
enable the next generation of innovators and entrepreneurs to compete
be resilient to a changing world and not controlled by a select few.
We believe the alignment between the Drupal Association’s Open Web Manifesto and the United Nations’s Open Source Principles is both strong and significant. As open source continues to power digital transformation globally, we look forward to a future where individuals, organizations, and governments invest in our digital public spaces with the same care and commitment as our physical ones.
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
View notes of previous months' calls.
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.
Over the last few weeks, the Marketplace Initiative has been mapping assumptions, surfacing motivations, and exploring real-world expectations for a Drupal Site Template Marketplace. The initial rounds of feedback were designed to surface motivations, beliefs, unknowns, and frame what success might mean. That work has helped ground the initiative in shared purpose and direction.
Now we’re starting the work of transforming those broad ambitions into working models of value, governance, trust, and experience. We're beginning to sketch what the Marketplace does, how it creates and protects value, and what contributors and users can expect from it.
Why a Drupal Site Template Marketplace?
Across survey feedback, community prompts, and RTC themes, several consistent value propositions have emerged — answering the question: Why build a Drupal site template Marketplace?
For Contributors
A trusted, visible channel to distribute, monetize, and showcase high-quality site templates that reflect your expertise — and generate leads, recognition, and revenue.
For Agencies & DCPs
An ecosystem catalyst that drives qualified leads, lowers implementation costs, and helps you deliver faster, better Drupal experiences to more clients.
For End Users (Builders, Subject Matter Experts, Evaluators)
A library of trustworthy, ready-to-launch Drupal sites — professionally built, continuously vetted, and provided by the Drupal community.
For the Drupal Project & Drupal Association
A sustainable marketplace that strengthens the ecosystem, generates new revenue, and reflects the values of open source through governance, quality, and inclusion.
What Makes Contribution Worthwhile?
In Slack, surveys and our real-time collaboration session we asked contributors directly: “What would make it worthwhile for you to contribute a template?” Key themes emerged from the discussion:
Compensation matters. Contributors suggested price points between $300–$1,000 per site template, depending on complexity. Some see templates as a viable business; others view them as strategic loss leaders.
Lead generation is an incentive. Access to user contact info or opportunities to offer services was cited as a powerful motivator—even more than direct revenue in some cases.
Recognition and visibility also surfaced as important non-financial incentives, especially for those aiming to grow brand or project awareness.
Licensing clarity and IP protection remain concerns—contributors want guardrails to discourage cloning and unauthorized redistribution.
Marketplace features—such as demo previews, rich media listings, and clear tech specs—can enhance both contributor experience and buyer confidence.
We also heard loud and clear what gets in the way of contribution:
High (Uncompensated) Support Expectations: Ongoing maintenance, support, and clarity of lifecycle.
Lack of Clarity: Around what qualifies, what gets featured, and how disputes are handled.
Governance Gaps: Without rules, the risk is chaos — too many low-quality or misaligned submissions.
Misaligned Incentives: Contributors worry about monetization models that exclude or exploit.
What’s Coming Next
Here’s what we’ll be working on over the coming weeks:
Governance Sketching: From submission flow to trust signals and appeals.
Contributor Workflow Design: What the path from idea → listing → maintenance actually looks like.
Quality & Review Criteria: What “good” looks like across code, content, accessibility, and UX.
Revenue & Recognition Models: How value is created, shared, and sustained.
How You Can Contribute Now
We’re still in active input-gathering mode, and your voice matters.
Survey #2 is still open – If you haven’t yet shared how a Drupal CMS Marketplace might help you or your business, take it now.
Survey #3 just launched – This one explores expectations around fairness, openness, and revenue models. Take the survey here.
Join the weekly Slack prompt in #drupal-cms-marketplace
Up this week: What would make you trust a site template listing?
Participate in our Drupal Certified Partner and Agency Ecosystem Roundtable 15 May 2025 UTC 15:30. Register here.
