The Drop Times: Drupal: A Digital Public Good for a Better Digital Future
A Drupal Couple: Orchestrating Development Teams Like Kubernetes
The pricing conversation has been interesting to watch, especially as it relates to development team orchestration and resource allocation. The comments, the ecosystem convergence discussion, and industry thoughts on agency transformation all point to the same thing: we're in the middle of a shift in how development work gets organized.
I mentioned thinking there might be a better approach to this. Here's what I had in mind.
The Orchestration ModelThink about how Kubernetes works - it's a container orchestration system that automatically manages where and how applications run across multiple servers. You don't manually decide "we need 3 web server pods on server A and 2 database pods on server B."
Instead, you define what services you need (web servers, databases, caches) and how they should scale based on demand. Kubernetes figures out how many of each type to run based on current load and metrics, then figures out where to place them based on available resources and constraints.
What if we applied that same orchestration model to development teams?
Instead of throwing senior-level rates at routine maintenance, or abandoning smaller projects because they don't fit traditional agency economics, we coordinate talent based on what each task actually requires.
A technical architect acts like that Kubernetes orchestration system. They look at project requirements and figure out what types of expertise are needed and how much of each. Then they coordinate between client requirements, available talent, and project constraints to assign the right people to the right tasks. Whether that's a senior developer handling complex architecture decisions, a mentored developer working on implementation tasks, or AI handling routine code generation.
It's about matching the right resource to the right task.
Why This Matters NowThe ecosystem pieces we've been discussing are reducing coordination costs: affordable hosting, professional themes under $500, mentored developers through the IXP (inexperienced) program, Drupal CMS for less technical users, Experience Builder for visual personalization. We still need someone to orchestrate how these pieces work together.
That's where the technical architect orchestration model becomes important. It's not about cheaper labor. It's about intelligent resource allocation.
The Human ElementThis connects to what Dries wrote about the "accountability gap" in his analysis of AI and agency transformation. AI can generate code and automate processes, but someone needs to own the results and make sure everything's going the right direction. Sometimes AI gets confused. Someone has to guide it.
The technical architect fills that accountability layer while coordinating the broader team.
Looking AheadI've been working on how this orchestration model works in practice - the tools, the processes, the communication patterns that make cross-cultural, multi-skill-level teams effective.
The economics are promising. The client gets better value through intelligent resource allocation. The developers get meaningful work that matches their skill level and expertise. And projects that used to be impossible become viable again.
I'll dive into the implementation details in upcoming posts. But first, what's your experience with these kinds of orchestrated approaches? Have you seen coordination models that work well for distributed teams?
The conversation's just getting started.
About We're Still Too Expensive, and We Should Talk About It Author Carlos Ospina Abstract Applying Kubernetes orchestration principles to development teams. How technical architects coordinate talent based on what each task actually requires. Tags Drupal Drupal Planet Technical Architect Development Community Drupal Leadership Team Orchestration Rating Select ratingGive Orchestrating Development Teams Like Kubernetes 1/5Give Orchestrating Development Teams Like Kubernetes 2/5Give Orchestrating Development Teams Like Kubernetes 3/5Give Orchestrating Development Teams Like Kubernetes 4/5Give Orchestrating Development Teams Like Kubernetes 5/5Cancel rating No votes yet Leave this field blank Add new comment
mark.ie: My LocalGov Drupal contributions for July 2025
Great month this month, tricky questions answered in Slack, via screenshare, and at Tech Group Drop-in. I'm feeling energised, read on, friends ...
Centarro: Will Shopify Plus Work For Your B2B Commerce Website?
Shopify is the biggest name in the e-commerce space, and for good reason. The platform is relatively easy to set up, performs well, and has excellent marketing. Its app marketplace is constantly growing, adding more capabilities.
For many merchants, Shopify is all they need. Going with the market leader is an obvious choice.
However, when you reach an enterprise scale, with requirements for B2B commerce and increased operational complexity, the story becomes quite different. Shopify says they offer B2B capabilities at scale, and when you’re subjected to their marketing and advertised track record, it's easy to start nodding your head to the beat of their tune.
Let’s dive into the true cost of Shopify Plus. Reading this will help you ask the right questions and better equip you to judge the answers.
The Shopify Plus Sales MachineWhen Shopify's enterprise sales team comes knocking, they arrive with a compelling story. They position Shopify Plus as the solution to all your B2B woes: lower total cost of ownership, enterprise features without enterprise overhead, and the promise that migrating to Shopify Plus will lead to a conversion rate boom.
But often these promises are unrealistic. The pitch typically centers around three key pillars that deserve closer scrutiny.
The conversion rate promiseShopify's sales pitch often includes dramatic claims about conversion improvements—sometimes suggesting compounding monthly increases that would theoretically give you a 55% conversion rate within six months.
Read moreThe Drop Times: What Bram Driesen Sees from Inside the Drupal Ecosystem
Droptica: Drupal 7 vs Drupal 11 – How Have This System and Its Functionalities Changed?
Drupal 7 was released in 2011 and has been the foundation of many websites for years. However, in the world of technology, 14 years is almost an eternity – during this time, Drupal has undergone a huge evolution. Today, the latest version, Drupal 11, is a modern system based on current coding standards and offering features that were once only a dream. In this article, we will look at the key differences between Drupal 7 and Drupal 11. If you last worked with Drupal years ago (e.g., with version 6 or 7), prepare yourself for the "wow" effect – Drupal 11 is a whole new experience.
Joshuami: Taking a Tour of the Tour Module
Dries Buytaert: Why Drupal is built for the AI era
Evolving Web: When Accessibility Isn’t Easy: Website Features That Need Extra Love
Interested in exploring this topic more ? Join our live accessibility webinar on August 15 at 12 pm EDT with Janell Sims, Manager of Digital Accessibility Services at Harvard University.
When we talk about web accessibility, it's easy to focus on guidelines and checklists. But in practice, not every feature on a website is easy to make accessible. Some elements—like custom search filters, maps, or dropdown menus—require more testing and creativity than others.
At Evolving Web, we’ve encountered many of these challenges firsthand. In this post, we’re sharing some of the techniques we’ve used when tackling tricky accessibility issues.
To meet WCAG AA guidelines and create genuinely usable experiences for all, we regularly use tools like Axe DevTools, DubBot, SortSite, and Siteimprove. But using accessibility testing during development and QA generally uncovers issues too late in the process. That’s why it’s important to plan for the features that will require extra accessibility work. Designers, strategists, project managers, and QA specialists all play a role in identifying those tricky areas from the start.
Features to Flag for Accessibility Review Making Megamenus AccessibleMegamenus often include more than just a list of links — they might have headings, images, featured articles, short blurbs, or even interactive elements like buttons or embedded search fields. But adding these elements creates accessibility challenges if the keyboard and screen reader experience isn’t carefully planned.
IssueWhen content beyond basic links is added to a megamenu, users navigating via keyboard or screen reader may:
- Not be able to reach all content using the Tab key if focus isn’t properly managed.
- Get stuck in the menu due to keyboard trap loops, especially if tabindex is misused.
- Lose track of where they are because menu sections aren't announced clearly.
- To make the entire megamenu accessible — not just the links — we apply a few specific techniques:
- Ensure all focusable elements inside the open menu (links, buttons, form fields) are reachable in a logical tab order.
- Use aria-expanded="true" on the parent menu item when the menu is open, and aria-controls to reference the submenu container.
- Add aria-hidden="false" to the open menu container so that screen readers know when the menu content is available.
- When the menu opens, move focus into the first focusable item inside the panel, and use keyboard listeners (like Escape key and arrow navigation) to allow users to exit or move between items cleanly.
- Ensure visible focus styles are present for extra headings and buttons in the menu dropdowns
The ROM museum website opens a megamenu under the “Visit” tab. The menu displays three content columns: a list of links like Visitor Information and Accessibility, a visual tile for Museum Maps & Tours with an image, and another for Location & Parking. On the far right, there’s a panel showing admission hours by date. The layout reflects accessibility best practices by grouping content logically, supporting clear tab order, and offering visual structure that could be paired with ARIA roles like aria-expanded and aria-hidden to ensure screen reader compatibility and smooth keyboard navigation.
Main Navigation Dropdown Toggling
In many website navigation designs, especially on desktop, the first-level menu items act both as links and as toggles for dropdowns. But combining these two functions in one element can confuse keyboard users and screen readers. To simplify the experience, we often design navigation so that top-level items with submenus act only as toggle buttons, not links.
IssueWhen a first-level menu item functions as both a link and a dropdown toggle, it can cause:
- Confusion for keyboard users: Should pressing Enter activate the link, or open the dropdown?
- Inconsistent behavior across screen readers, depending on how the markup is structured.
- Difficulty in managing focus and aria states cleanly, especially when nesting multiple levels.
To provide a clearer, more accessible experience, we:
- Convert the parent menu item into a button (or a link with role="button") that only toggles the visibility of the submenu, rather than navigating to a new page.
- Use the first link in the dropdown to link to the top-level page for that section of the website (sometimes it’s a section landing page).
- Use aria-expanded="false" on the toggle button, and update it to true when the dropdown is open.
- Include aria-controls pointing to the submenu container’s id for better screen reader context.
- Ensure the submenu is hidden by default (using aria-hidden="true" and/or display: none), and revealed when toggled open.
- Place focusable items within the dropdown in a logical tab order, and allow for keyboard-only navigation through all items before returning focus to the parent nav.
We implemented this pattern on the Georgia Center website, where the top-level menu items with dropdowns act only as toggles. This makes it easier for keyboard users to explore all submenu items without accidentally navigating away, and it gives screen reader users clear cues about expandable content.
Making AJAX Search Filters Screen Reader-Friendly
We love using AJAX to make search filters feel fast and responsive—content updates instantly without reloading the page. But while this improves the visual and performance experience, it creates barriers for screen reader users, who may not realize anything on the page has changed.
Issue- When results update dynamically (via AJAX), screen readers don’t automatically detect or announce those changes:
- Users may not know their filter selection did anything.
- The results section may change visually, but not be announced to non-visual users.
- Without proper cues, users can feel disoriented or think the filter “didn’t work.”
To ensure dynamic updates are communicated to assistive technologies, we:
- Add an aria-live="polite" region around the content area that updates (e.g., search results or counts).
- After filters are applied, add a clear message like “12 results found”.
- Use JavaScript to trigger updates to that region after the AJAX request completes.
- Test the implementation with screen readers to ensure the live region is actually being read.
On the Georgia Gwinnett College website, we provided a screen reader announcement for Drupal views that require page reload. We appended the counter to the “skip to main” link with JavaScript so that it’s being read first after the page is loaded.
To support screen reader users, the Georgia Gwinnett College search interface includes a live region that announces updated result counts after filters are applied—ensuring dynamic AJAX changes are clearly communicated without a page reload.Making Custom Select Menus Accessible
Custom-styled form elements are a favorite of designers, especially when a project calls for a more branded or polished look. But replacing native form controls—like <select> elements—with JavaScript replacements introduces accessibility challenges. While native HTML elements are the most accessible by default, they don’t offer the design flexibility that clients and designers want.
IssueCustom select menus often:
- Break keyboard navigation (Tab, Arrow keys, Escape) if not fully implemented.
- Lack proper screen reader support, especially for focus announcements, selection changes, and open/close states.
- Trap users inside the field or fail to return focus correctly after selection.
To balance accessibility with visual customization, we often use Select2—a JavaScript library that mimics native selects but with better styling and feature support.
Here’s how we make it work:
- Use Select2's built-in accessibility modes, including ARIA support and keyboard navigation patterns.
- Customize behaviour when needed—e.g., ensuring focus returns to the appropriate element after a selection is made, or that assistive tech announces open/closed states correctly.
- Manually test each implementation with screen readers and keyboard to catch edge cases.
When showcasing visual content—like photo galleries, product views, or exhibition highlights—designers often rely on modals or lightboxes to create an immersive experience. While these interactions look great, they can easily become accessibility barriers if not carefully implemented for keyboard and screen reader users.
IssueStandard lightbox/carousel libraries often:
- Don’t properly trap keyboard focus inside the modal, allowing users to tab into hidden background content.
- Lack appropriate ARIA roles or labels, so screen readers may not recognize the modal context.
- Fail to provide intuitive ways to close the modal with the keyboard.
To build accessible modals for image galleries, we use Parvus, a customizable JavaScript lightbox. If a modal is used to display content or a menu, we create a custom modal with JavaScript.
Here’s are some things to make sure you do when implementing a custom modal:
- Add role="dialog" and aria-modal="true" to the modal container so screen readers know it should get the user’s attention.
- Ensure the modal includes a labeled close button (e.g., aria-label="Close modal").
- Hide background content from screen readers using aria-hidden="true" while the modal is active.
On the Royal Ontario Museum site, we use the Parvus library to create the modal lightboxes for exhibits. When users click the info icon on an image, a modal lightbox opens with detailed content and imagery.
Inside the modal:
- Keyboard users can tab through all interactive elements, including text, images, and the close button.
- After the last item, focus loops back to the first item inside the modal.
- Users can press Escape to close the lightbox and resume navigation from where they left off.
Preventing Keyboard Traps in Sliders
Sliders and carousels are commonly used to highlight featured content—especially in hero areas or product showcases. But when using libraries like Swiper.js, this can introduce keyboard accessibility issues, trapping users inside the slider with no way to escape.
IssueSwiper’s default loop mode duplicates slides to enable infinite scrolling. This has unintended consequences for keyboard users:
- All duplicate slide elements remain in the DOM and are focusable, even if they’re not visible.
- This creates a keyboard trap, where users tab endlessly through duplicated slides and never exit the slider.
To fix this, we use a custom JavaScript function to control which elements inside the slider can receive focus:
- We dynamically set tabindex="-1" on all non-visible slides, and remove it only from those currently in view.
- We detect slide changes using Swiper’s event listeners (on: slideChange, etc.) and update focusable elements in real time.
- This ensures that only visible slides are keyboard-reachable, and users can tab forward to content outside the slider.
- We also test the slider with real content (especially when using links or buttons inside slides) to make sure screen readers and keyboard users can interact without confusion.
On one project, we implemented a looping slider using the Swiper library to feature linked articles and stories within each slide. However, with loop mode on, all slide links remained focusable—even off-screen—creating an infinite tab loop. To solve this, we added custom JS to make only visible elements focusable.
This simple adjustment allowed keyboard users to tab through the slider once and move on to the rest of the page.
Handling Non-Essential SVG Maps in an Accessible Way
SVG maps can be a visually rich, clickable way to help users explore content—especially for regional directories or filtering tools. But when maps are used as enhancements rather than essential navigation tools, they can create more accessibility challenges than they solve.
IssueSVG-based maps often:
- Contain many interactive regions that need proper ARIA labeling and keyboard support.
- Are not inherently keyboard-navigable, requiring extensive scripting to manage focus, interactivity, and screen reader compatibility.
When maps are non-essential to the user experience we can:
- Hide the map from assistive technologies using aria-hidden="true" or similar techniques.
- Provide a fully accessible alternative—such as a structured list or dropdown.
On the Canada’s Drug Agency website, we used an SVG-based regional map to help users find programs by region. However, making each region fully accessible (labeling, focus control, keyboard behavior) would have required a substantial custom build. Instead, we provide a link to “View Data Table” that shows all the same content in a structured, accessible way.
This regional SVG map was used to visually enhance navigation on a program directory page. Because making the map fully accessible would require complex scripting, it’s hidden from assistive tech using aria-hidden="true", while a structured data table link offers a fully accessible alternative for screen reader and keyboard users.Making Icons Meaningful for Screen Readers and Editors
Icons are everywhere on modern websites. Whether used to break up dense content, convey meaning quickly, or support a brand’s visual language, they’re a valuable design tool. But when icons are used as the only way to communicate important information, they become content, not just decoration. And that means they must be accessible.
IssueIcons used as content need to:
- Be labelled for screen readers with meaningful descriptions.
- Be structured so content editors can easily manage them in the CMS.
- Avoid duplicating content or creating confusion with conflicting visual/text cues.
- If not handled carefully, screen readers may skip the icon entirely—or announce something generic like “image” or “graphic.”
To ensure icons are accessible and manageable by content authors, we:
- Paired each icon with screen reader-only text (e.g., “Gluten-free”) using visually hidden HTML elements
- Allowed editors to add or manage this text directly in the CMS, rather than hardcoding it.
- Used ARIA roles so screen readers interpret the icons as labels, not decorative graphics.
On the University of Georgia (UGA) website, we implemented this solution on the restaurant menu, where icons communicate important dietary info. By structuring the markup to include hidden descriptive text and enabling editorial control in the CMS, we made the interface both accessible and sustainable for ongoing content updates.
Ensuring Accessible Focus States in Dark Mode
Dark mode has become a popular design choice for modern websites. It can reduce eye strain, support user preferences, and create a sleek aesthetic. But enabling a dark mode theme adds an extra layer of complexity when it comes to accessibility—particularly for colour contrast and focus visibility.
Issue- Colour contrast that passes in light mode may fail in dark mode, especially on hover or focus.
- Focus indicators can disappear or become too subtle against dark backgrounds.
- Keyboard users may lose visual cues for navigation if focus styling isn't tested across themes.
- Test all state variations (default, hover, focus, active) in both light and dark modes.
- Use WCAG-compliant color contrast:
- 4.5:1 for text
- 3:1 for UI components (borders, outlines, focus rings)
- Customize styles to ensure visible focus indicators in dark mode (e.g., outlines, box shadows).
Takeaways: What Teams Should Watch For
Whether you’re a developer, designer, or project manager, here are a few things to keep in mind:
- Check keyboard and screen reader support early in development, especially for interactive elements.
- Don’t rely on testing tools alone. Manual testing with user scenarios are key.
- Look for alternatives and fallbacks—like offering a text version of map content or a non-dynamic option for filters.
Accessibility isn’t just about checking boxes or following rules—it’s about creating digital experiences that work for everyone. By identifying tricky features early in the process, your team can better plan, estimate, and design with inclusion in mind, reducing the need for late-stage fixes and improving usability for all.
At Evolving Web, we specialize in helping organizations meet these challenges head-on. From accessibility audits to custom component design and strategic guidance, we support teams in building websites that are not only compliant—but genuinely accessible. . If you're looking to improve your website's accessibility or tackle a specific challenge, get in touch with us.
+ more awesome articles by Evolving WebDrupal Association blog: Transform Your Business by Sponsoring a Drupal Leader
An extraordinary opportunity exists to support Drupal CMS, boost your organisation's credits, and bring one of the leading minds behind Drupal CMS directly into your organization.
We're seeking sponsors for Cristina Chumillas, the UX and Product Design Lead for Drupal CMS, who has been defining and driving the product direction since the Starshot initiative started in May 2024.
We were lucky to have Cristina engaged in this role full-time for seven months, thanks to Lullabot. Now we're looking to extend this to ensure we can deliver on the strategy for Drupal CMS 2.0 and beyond.
Why Core Contributors Are Business Game-ChangersThe real value of this sponsorship goes beyond supporting Drupal—it's about what core contributors can do for your business.
"Working with a core contributor is like having a superhero on your team,” explains Pam Baronne, CTO at Technocrat and Drupal CMS Product Owner.
"There should be an absolute premium on hiring core contributors. They aren’t just an asset to Drupal -- their skill, knowledge, and connections make them incredibly valuable to your company”.
Sponsoring a member of the Drupal CMS leadership team ensures your organization is not just prepared for what's coming, but also has the insider insight to help position you in the shifting market.
Cristina can bring a depth of experience to your organization that is hard to match. Your sponsorship earns you contribution credits directly, boosting your Drupal Certified Partner ranking. Additionally, she can mentor your team on Drupal contribution, building expertise that elevates your company's productivity as well as your standing in the community.
Meet Cristina - The Designer-Developer Leading Drupal's TransformationAs a designer who later learned front-end development and specializes in Drupal, Cristina brings a diverse range of skills to the role. She has been a core contributor for many years. She joined the Core Leadership Team as a front-end framework manager in 2021, and was recently also appointed as a core UX Manager. Cristina has been coordinating key design and UX initiatives in Drupal since 2017, most recently with the new Navigation in Drupal 11.
Based in Barcelona, Cristina is also active in organising the local community as well as DrupalCon. She will be a featured speaker at DrupalCon Vienna and (pending sponsorship) DrupalCon Nara as well.
The vision for Drupal CMS as a tool for marketers, designers, and content creators requires deep expertise in user experience design—exactly what Cristina brings to the role.
Flexible Engagement OptionsThe structure of the sponsorship engagement is flexible, and we are open to offers:
- Full or partial sponsorship
- Project-based arrangements for specific milestones
- Part-time combinations of Drupal work with your business needs
- Custom arrangements tailored to your goals
We're open to alternative arrangements as well, so if you are interested in learning more about this opportunity, please fill in this sponsorship interest form and we will be in touch.
Picozzi.com: Drupal + Mailgun: A Simple Setup for Transactional Email
LakeDrops Drupal Consulting, Development and Hosting: Drupal's Modeler API released - learn about the benefits
Drupal's ECA module has been released 3 years ago, and provides an incredible workflow automation and orchestration platform together with an intuitive UI based on BPMN diagrams. Other complex configuration requirements can now be managed with the same tools as the newly introduced Modeler API provides the framework to serve applications like ECA or AI Agents with modern, exchangeable UIs without having to re-implement any of those ever again. This blog post describes the architecture, and the benefits that come out of all this for software developers and end-users alike.
1xINTERNET blog: Keep your software healthy with refactoring
Learn why periodic software refactoring is essential for long-term success. We update Drupal modules and dependencies to reduce costs, improve performance, and accelerate future development cycles.
DevCollaborative: Hey Drupal Content Editors, Make Your Work Easier with Admin Menu Swap
Change out the developer-centric administration menu with one that meets the needs of your site admins, editors and authors with the Admin Menu Swap module.
Drupal AI Initiative: Installing the AI Module and Basic Features — Webinar Recap
The second webinar in the Bringing Drupal AI Into Your DNA series focused on rolling up your sleeves and getting Drupal’s AI module working on real sites. Hosted by Jamie Abrahams, co-founder of FreelyGive, and Marcus Johansson, lead developer on the Drupal AI initiative, this session balanced developer-focused walkthroughs with honest takes on what’s working and what still needs your help.
This session is part of a free, public training series backed by the European Commission in partnership with the Drupal community. The goal: to equip builders, developers, and digital agencies with ethical, open-source tools and knowledge to bring AI into Drupal sites responsibly.
Watch the webinar recording now.
The first session in the series — “Bringing Drupal AI Into Your DNA: Introduction” — featured Jamie alongside Dries Buytaert and introduced the strategic initiative, the long-term vision, and the open contribution model being built around AI in Drupal.
This second session moves from vision to implementation: it’s about getting the AI module installed, configured, and ready to use.
Keep Calm and Install AIRight from the top, Jamie made the audience feel comfortable diving in, regardless of where they’re starting from:
This one is going to be slightly more developer focused, but you’re going to know how to get started.
Jamie Abrahams
The session covered:
- Installing the AI module via Composer and verifying dependencies.
- Connecting the module to OpenAI or your LLM of choice, with examples for local dev and production.
- Managing permissions and API keys securely.
- Running a basic content generation test to confirm that the setup works end-to-end.
Jamie’s role as co-founder of FreelyGive and maintainer of the AI module keeps him right at the centre of this fast-growing ecosystem. He shared that:
I’ve been focusing on native Drupal CRM and been particularly obsessed with AI recently
Jamie Abrahams
He made it clear this is all a work in progress. That’s exactly why the Drupal community’s input is so critical. Expect a bit of trial and error, but know that the maintainers genuinely want your feedback.
Marcus’ Hands on DemosMarcus, who leads parts of the Drupal AI initiative, gave the developer audience concrete examples of how to work with AI functionality, from voice output to local installations. These live demos showed exactly how flexible the AI module can be and where it’s heading next. Expect more video walkthroughs, local dev examples, and client modules that link to other providers.
Join In!If you’re interested in Drupal + AI, there’s no better time to get involved. Your contributions, whether that’s testing new releases, sharing feedback, or writing documentation, matter.
Next steps:
- Watch the webinar replay if you missed it
- Check out the AI Module on Drupal.org
- Join the #ai channel on Drupal Slack to connect with Jamie, Marcus, and the rest of the community
This webinar is exactly what more open source projects need: practical, transparent, and focused on real implementation, not hype. Install the AI module. Test it. Break it. Improve it. And share what you learn, because that’s how Drupal AI moves forward.
Upcoming SessionsIn the coming months, the webinar series continues with targeted training sessions that build upon each other. All sessions are free, recorded, and open to the public.
- 2 September: AI Search
- 23 September: AI Agents (No-Code Creation)
- 7 October: Advanced: Build AI Agents with Code
Freelock Blog: Automating all the things - 24 ideas for things you can automate with your website
Last December I wrote up 24 specific things we've automated on Drupal, and published them as an Advent Calender -- one little nugget each day.
Sustainable/Open Business Read MoreDrupal Association blog: The Drupal Association Announces 2025 Board Election Winner and Additional Board Members
The Drupal Association is excited to announce the winner of 2025 Community At-Large Board Elections and additional board members joining this year.
We extend a sincere thank you to Fei Lauren, Lynne Capozzi and Rosa Ordinana for their service and dedication, not only to Drupal, but to the Drupal community. Your time spent on the board made such a difference to the future of the Drupal project, and we thank you all for participating with grace, thoughtfulness, and insightful contributions.
We would like to congratulate and welcome Dominique De Cooman and Glenn Hilton as our newest board members.
An additional congratulations to Maya Schaeffer for winning the community-elected seat during our 2025 At-Large Board Elections.
We cannot wait to see all the amazing things the new board members will accomplish while on the Drupal Association Board.
Detailed Voting ResultsThere were 7 candidates in this year’s At-Large board member election. 528 voters cast their ballots out of a pool of 1459 eligible voters.
Under Approval Voting, each voter can give a vote to one or more candidates.
The final total of votes were as follows:
Candidate
Votes
Alexander Varwijk
114
Carlos Mario Ospina Anzola
140
Matthew Saunders
158
Matt Glaman
264
Maya Schaeffer
269
Vladimir Roudakov
106
Will Huggins
120
On behalf of all the staff and board of the Drupal Association, a heartfelt Drupal Thanks to all of you who stood for the elections this year. It truly is a big commitment to contribution, the Drupal Association, and the community, and we are so grateful for all of your voices. Thank you for your willingness to serve, and we hope you’ll consider participating again in 2026!
Smartbees: How to Configure the RobotsTxt Module in Drupal?
Proper Robots.txt file configuration is a cornerstone of SEO optimization for every Drupal website. In Drupal, RobotsTxt can serve as an excellent tool for controlling web crawlers’ access, as it affects how your site appears in search engines. Let's explore how to efficiently create a robots.txt file in Drupal using the RobotsTxt module.
Specbee: Getting started with Lando and Drupal
Talking Drupal: Talking Drupal #513 - Back To The Office
Today we are talking about Working from home, heading back to the office, and the current state of remote work with guest Kaleem Clarkson. We’ll also cover Microsoft 365 Connector as our module of the week.
For show notes visit: https://www.talkingDrupal.com/513
Topics- Exploring Remote Work with Kaleem Clarkson
- Trust Issues in Management
- Employee Red Flags and Data-Driven Decisions
- Managerial Concerns with Return to Office Policies
- Respectful Implementation of Return to Office
- Challenges of Enforcing Office Mandates
- Benefits of In-Person Work
- Hybrid Work Models and Their Challenges
- Variations in Hybrid Work Policies
- Impact of Seniority on Office Policies
- Cutting DEI Initiatives: Fear and Legal Risks
- Employer Brand and Social Contracts
Kaleem Clarkson - kclarkson
HostsNic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Rich Lawson - richlawson.co rklawson
MOTW CorrespondentMartin Anderson-Clutz - mandclu.com mandclu
- Brief description:
- Have you ever wanted your Drupal site to integrate with Microsoft 365, so users can log in with their Azure AD credentials, and then have direct access to shared files, see recent emails, and more? There’s a module for that.
- Module name/project name:
- Brief history
- How old: created in July 2019 by immoreel, though the most recent release is by Boris Doesborg (batigolix), both of Finalist, a Dutch Drupal shop
- Versions available: 5.0.22 and 5.1.0-beta1, the latter of which supports Drupal 9.4, 10, and 11
- Maintainership
- Actively maintained
- Security coverage
- Test coverage
- Two documentation guide available
- Number of open issues: 18 open issues, 1 of which is a bug, though it is postponed waiting for more info
- Usage stats:
- 365 sites
- Module features and usage
- This module integrates your Drupal site with the Microsoft Graph API, a unified API that provides a single endpoint for accessing data and intelligence from Microsoft 365 services, including Exchange, SharePoint, OneDrive, and more
- Microsoft 365 Connector includes more than a dozen submodules, each of which provide specific capabilities like Single Sign-On, syncing data to Drupal user accounts, sending Teams messages from within Drupal, and more
- You can also use this module to do things like automatically add an event node to your Outlook calendar, and invite other people at the same time
- It’s worth noting that in the documentation guide the submodules are named “Office 365”, which is probably what the module was named until around 5 years ago when Microsoft retired the Office 365 name
- Finally, setting up this module requires registering an app in Azure AD, so it’s not for the casual user. But if you're working on an intranet or similar collaboration platform for an organization that is heavily invested in the Microsoft 365 suite, this could make for a compelling integration
- « erste Seite
- ‹ vorherige Seite
- …
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- …
- nächste Seite ›
- letzte Seite »