Aggregator

IXP Initiative Co-Creator | Technical Account Manager | Community Contributor

I'm running for the Drupal Association Board again because the work we started isn't finished. When I first nominated myself in 2023, I talked about the need for better regional representation and sustainable talent pipelines. Today, as several major DA initiatives directly address these challenges, we need to ensure they work for everyone - from small regional agencies to large global companies, from new developers to experienced contributors. If you're a member of the Drupal community who values global inclusion and sustainable growth, I'm asking for your support in this important moment of transformation.

I have worked for years within the Drupal community in both Latin America and the United States. I helped organize DrupalCon Latin America back in 2015, and honestly, I want to bring more opportunities like that to LATAM and other regions that get overlooked.

But this isn't just about Latin America. It's about recognizing that Drupal's future depends on communities everywhere having pathways to contribute and grow.

We're in a chicken and egg situation across many areas - community growth, code contribution, sustainability, and business development. For Drupal to grow at all levels of the ecosystem pyramid, we need more popularity and adoption. But this requires support from larger agencies. At the same time, the DA needs to develop sustainable revenue beyond just big agencies and DrupalCon North America. The challenge is that we still need those larger players to help create realistic pathways for regional agencies to participate and thrive. Breaking this cycle requires action on multiple fronts at once.

The International Federation initiative offers a way to break through some of these interconnected challenges by creating structures where global communities can actually participate, potentially moving all these areas forward together.

The thing I'm most proud of is co-creating the IXP Initiative. We saw this fundamental problem - new developers couldn't get hired without experience, but couldn't get experience without being hired. So we built something to fix it. Working with other members of the community and the Drupal Association, we turned this idea into a real program. Now we have companies actually participating, offering structured pathways for new developers, and getting 250 contribution credits for each successful engagement.

This proves we can move beyond just talking about problems to building actual solutions that strengthen the entire ecosystem.

My experience working in both Colombia and the United States since moving to the US in 2007 taught me how regional economic differences create both challenges and huge opportunities for Drupal.

At a recent board meeting, I brought up how a $1,000 partnership fee that works in the US becomes impossible in countries where monthly minimum wage is $200-300. These aren't just numbers - they represent talented developers who want to contribute but need different pathways to participation.

The International Federation initiative—a concept currently being explored to potentially give regional Drupal communities more formal representation—creates exactly the framework we need to address this. This structured approach can transform regional participation by providing clear business value to local companies, creating a more accessible path to becoming Drupal Certified partners while strengthening DA revenue.

Several major initiatives are reshaping Drupal's global landscape:

Drupal CMS now delivers enterprise-grade functionality to smaller markets and diverse budget contexts. With out-of-the-box features that previously required expensive custom development and no CS degree needed, Drupal has become accessible to communities previously excluded from its benefits.

The International Federation initiative is creating formal structures for global governance. With the working group starting in June 2025, we need board members who understand regional economic realities and can help shape this federation to truly serve diverse communities.

The Marketplace initiative is analyzing the feasibility of creating a marketplace for templates and quick site deployment options. I believe having quick ways to spin off a site that makes it 70% ready with Drupal CMS, decent price hosting to start, and templates that bring functionality and design very quickly, opens new paths to new business models. Add IXP to that and you have the affordable workforce to work on lower budget situations.

All these initiatives are interconnected: Drupal CMS makes participation technically possible, the International Federation creates the governance structure, and the Marketplace opens business opportunities. Making them work together is how we'll create a balanced ecosystem that serves both community values and business sustainability.

I understand we need a sustainable Drupal Association that balances community needs with business realities. I recognize the importance of balancing community, open source, and businesses, but the reality is today's Drupal global activities sometimes lack on the business part.

We can do better. When I proposed bringing back DrupalCon Latin America, I suggested adapting the fair-style event model common in our region. Organizations pay for exhibition spots and actively invite end users, creating genuine business opportunities alongside community building.

Another example is how IXP-trained resources could enable agencies to open a Drupal CMS line of business for smaller budget projects. This creates opportunities to serve clients with limited resources - whether they're smaller companies, organizations in developing markets, or even departments within large enterprises looking for internal solutions. This approach simultaneously develops talent, creates business opportunities, and expands Drupal's reach.

I've been writing about ways to help make contribution more economically sustainable, including authentic community contribution approaches and ideas about how Drupal.org could better connect businesses with service providers across different economic regions.

As a board member, I'd focus on:

• Ensuring the International Federation serves all regions - by making regional economic realities central to governance structures
• Creating opportunities in underrepresented regions - by expanding IXP's successful model to build global talent pipelines
• Generating economic value for regional developers - by supporting DA initiatives like the Marketplace for sustainable growth
• Creating opportunities for the entire global community - by connecting diverse economic contexts to build meaningful bridges

I've spent years contributing to the Drupal community and creating programs that develop new talent. I've written extensively about community-first approaches that create sustainable business value. Now I want to bring that same focus to board-level decision making as these critical initiatives unfold.

The future of Drupal depends on communities everywhere having real pathways to contribute and grow. With the International Federation, Drupal CMS accessibility, and Marketplace opportunities all developing simultaneously, the board needs to ensure these initiatives work together to build a truly global community where everyone (regardless of region or economic context) can participate meaningfully.

If you believe in this vision for a truly global Drupal, please:

1. Cast your vote during the election period (June 15-30, 2025)
2. Share this nomination with your colleagues who care about global representation
3. Reach out to me with questions or ideas at [email protected]

Together, we can build a Drupal ecosystem that works for everyone, everywhere.

– Carlos

Artificial Intelligence has arrived in the Drupal ecosystem and it is already making huge waves. This is the first in a series of articles about my experiences as I dip a toe into these exciting waters.

I was working on a large website with plenty of content dating back years, including numerous product reviews that required improved categorisation. The goal was to tag all of these review nodes with the relevant Make and Model.

I chose to write a custom Drush script to loop through all of the review nodes, using Artificial Intelligence to parse the Title and Body fields and return the make and model discussed therein.

I...

Mari Núñez

Frontend Engineer

Mari is a high-achieving Drupal frontend developer who has shown great proficiency in tackling complex frontend problems.

January 1, 1970

Crafting a visually engaging website isn’t just about eye-catching colors and typography — today it’s also about creating immersive experiences that captivate users as they scroll. One of the most compelling ways to achieve this is by using a parallax effect, where elements move at different speeds to create a sense of depth and motion.

With a thoughtful approach and some JavaScript, you can seamlessly add this effect to your site, enhancing storytelling and making your pages more dynamic.

This post will guide you through the process of integrating a custom parallax effect into your site. Whether building a feature-rich landing page or enhancing storytelling elements, this technique can bring your site to life. Let’s begin.

Our example site was built in Drupal, but the overall concept would be the same in any CMS. First, we will need to build a component that has all the necessary fields that we want to display in our parallax. In this example, we will use Paragraph types and have two kinds of slides: one with an image and another without an image.

This slide will let us add an image, a title, and the caption or information we want to tell about that specific slide, the alignment of the information (left, center, or right), and an option if we want to hide the credit of the image or show it.

This slide is similar to the previous one, but there are key differences. This one won’t include an image and anything else related to the image, and we allow a lot more text formatting on blank slides. This means that we can have the text on a blank slide take up much more of the available space without worrying about color contrast issues with advanced text formatting.

Once both paragraphs have been created, let’s create a ‘Parallax Slideshow’ paragraph that will only have a field that references the previous paragraphs created.

Once our component is ready, the next step is to integrate it into our custom theme. In this example, we’re using Emulsify, our design system, as our custom theme, to ensure a consistent and modular approach to theming.

First, we will have our paragraph--parallax-slideshow.html.twig that will include a parallax-slideshow.twig, which has a JavaScript library called parallax-slideshow that is in charge of all logic to make our parallax effect work, and also some required styles.

Here’s what our parallax-slideshow.twig looks like. Notice the empty <div class=””parallax-slideshow__image-wrapper””></div>. This is where the slide images will be rendered and where the fade-in and fade-out effects between images will occur.

Then, we will have a paragraph--parallax-image-slide.html.twig and a paragraph--parallax-blank-slide.html.twig. Both files include a parallax-slide.twig, which is a molecule in the design system that organizes the content of each slide and adds all the needed styles. They are almost identical — the only difference being that the blank-slide will not pass the slide image to the parallax-slide.twig file.

Here’s what our parallax-slide.twig looks like:

To prevent a visible delay between slides, the component needs to preload the first two images on page load. As the user begins scrolling, additional images are loaded dynamically in the background. This ensures a seamless transition between slides without noticeable lag and enhances the overall user experience.

We need to pass structured data from the backend to JavaScript. Below is a function that loads the data and attaches it to drupalSettings for use in a theme.

Once the data is attached to drupalSettings in our JavaScript file, we can access parallaxSlideshowData to dynamically load images and control the parallax effect.

Below is a breakdown of how the JavaScript file works to bring the parallax slideshow to life.

Let’s start by retrieving the slideshow data from drupalSettings and ensuring the script only runs once per slideshow element. The function initializeParallaxSlideshow is responsible for setting up and managing the parallax slideshow experience by initializing each slideshow. By tracking which slides have been loaded, we prevent redundant loading:

Then, it calls a preloadSlides function, which likely preloads images or other resources for the first two slides to prevent a visible delay between slides.

Next, it calls a createImageDiv helper function that is responsible for creating and managing an image element within the parallax slideshow.

The reason why we check if there is a firstImage is that we want the initial slide to fade in from black when it’s fully loaded. Once the image loads, it finds the overlay and the slideshow wrapper, fades out the overlay, removes the overlay, and re-enables scrolling.

Let’s go back to the initializeParallaxSlideshow. After the preloadSlides function there’s a scroll event listener for the parallax effect that listens for scroll events to update the slideshow’s image position dynamically.

The idea is to let the image wrapper take the whole height of the viewport, but since there can be components before or after the parallax slideshow, at some point it is necessary to change the position of the image wrapper, to let the user scroll and interact with other components.

The following logic is to set a scroll hijacking if the parallax slideshow is the first component of the page and if the first slide is an image.

Then, there’s a piece of code that iterates through all slides in the slideshow and calls the initializeSlideObserver() function on each slide.

Now let’s take a look at the initializeSlideObserver() function — the one that is responsible for setting up an Intersection Observer to track when a slide enters the viewport and dynamically updates the slideshow’s displayed image accordingly. It ensures that the slideshow loads the next image only when needed, preventing unnecessary rendering and improving performance.

Last but not least, there’s the loadNextSlide function that is responsible for preloading the next slide’s image to ensure a smooth transition when the user scrolls. This prevents unnecessary reloading of already loaded images. This function is very similar to the preloadSlides function.

With these functions in place — handling image creation, slide observation, and preloading — you now have a dynamic and efficient parallax slideshow that seamlessly transitions between images as users scroll. By leveraging the Intersection Observer API, preloading logic, and smooth fade effects, the slideshow ensures a visually engaging experience without unnecessary performance overhead.

Once you’ve added the necessary styles to control positioning, animations, and transitions, your parallax slideshow should be fully functional across your site. This approach not only enhances the storytelling aspect of your content, but also keeps interactions smooth and lightweight.

Now, all that’s left is to fine-tune the visuals to match your design, and you’re set to create an immersive scrolling experience!

The post Creating depth and motion: A step-by-step guide to parallax appeared first on Four Kitchens.

Great month, lots done, including a new module for Drupal.org - modules_list.