Today is the twenty-first day of our Advent Calendar, and we are looking at how you will search your Drupal CMS site. We are joined by Baddý to summarise the work her team is doing…

The Search Track, led by Baddý Breidert, Dr. Christoph Breidert and Artem Dmitriiev from 1xINTERNET, has made substantial progress since DrupalCon Barcelona. A key achievement is the integration of the Search Recipe into the Drupal CMS project. This recipe provides a flexible framework for configuring search functionalities based on specific user needs.

To enhance advanced search capabilities, the team has…

Tags

• Search

Last Chance Proposal Help: MidCamp 2025 Session Proposal Workshop

Missed the last Session Proposal Workshop? Don't worry; we have another one in January right before the submission deadline!

🚀 Ready to take your session ideas to the next level? Whether you're a seasoned speaker or a first-time presenter, the MidCamp 2025 Session Proposal Workshop is here to help you craft standout submissions.

📅 Date: January 7, 2025
🕒 Time: 3:00 PM - 4:00 PM CST
🌐 Location: Virtual via MidCamp Slack (#speakers channel)

Facilitated by Aaron Feledy

This workshop will be led by Aaron Feledy, a seasoned Drupal contributor and experienced speaker. Aaron brings years of expertise in proposal crafting and conference speaking, offering practical advice to help you refine and elevate your session submissions.

Why Attend?

Submitting a session proposal can be daunting—but it doesn't have to be! This workshop is designed to guide you through the process, from brainstorming topics to refining your submission. Our expert facilitators will share insider tips on what makes a proposal stand out to reviewers and resonate with attendees.

What You’ll Learn:

• How to choose and frame a compelling topic
• Crafting clear, concise, and engaging abstracts
• Tips for tailoring your proposal to different audiences
• Insight into the MidCamp review process

Session Submissions Now Open

Ready to submit? Session submissions for MidCamp 2025 are now open! Visit the MidCamp 2025 session submission page for guidelines and start your journey to the stage.

How to Join:

Simply join the MidCamp Slack and head over to the #speakers channel on December 12th at 3:00 PM CST. No registration required—just jump in and start collaborating!

As explained in the previous article in the series I've started working on maintaining Views Data Export again.

I've decided to document my work in 2 week 'sprints'. And so this article is about what I did in Sprint 1.

Sprint progress

At the start of the sprint there in the Drupal.org issue queue there were:

• 204 open bugs
• 276 other open issues.

So that's a total of 480 open issues.

By the end it looked like this:

• 91 open bugs
• 17 fixed issues.
• 81 other open issues

So that's a total of 189 open issues, a 60% reduction from before!

Key goals

In this sprint I wanted to:

• Tame the issue queues on Drupal.org and get a handle on what the common frustrations and missing features were.
• Read and understand all of the code in the Drupal 8.x-1.x branch.

Taming the issue queue

As mentioned in a previous article I decided to close down pretty much all the tickets for the Drupal 7 version of the module. This is the codebase that I'm most familiar with, but it's causing a lot of noise in the issue queue, so getting rid of that is a great first step, and pretty easy.

https://www.drupal.org/project/views_data_export/issues/3492246 was my ticket where I detailed what I was going to do, and then I went about doing that.

This felt immensely good! I went through each Drupal 7 ticket and gave it a quick scan and then pasted-in my prepared closing statement. It took just over an hour, and was like taking a trip down memory lane: seeing all those old issues come up and remembering when I triaged some of them originally.

After this initial round of work, I've also been working in the 8.x-1.x queue to close out duplicate and solved issues. I've been focussing on support requests which are usually super quick to evaluate and close out. However, this means that I've not really had a chance to look through all the feature requests and bugs, so I still don't really have a handle on what's needed/broken with the module.

Understanding the code

I had a good old read of the code. There's some really great stuff in there, and there's some obvious room for improvement.

But, at least I know what the code does now, and can see some obvious problems/issues. But also, the codebase is small, and there some automated tests, so we've got a great platform to get going with.

Giving direction

There were a few tickets for 8.x-1.x where there were contributors making great contributions and I was able to provide some guidance of how to implement a feature or resolve a bug. I feel like the issue queue has been lacking any kind of technical leadership and so many tickets are collections of patches where developers are fixing the problem they have in quite a specific way. I'm really looking forward to giving some direction to these contributions and then at some point committing and releasing the great work!

Future roadmap/goals

I'm not committing myself to doing these exactly, or any particular order, but this is my high-level list of hopes/dreams/desires, I'll copy and paste this to the next sprint summary article as I go and adjust as required.

• Get the project page updated with information relevant to Drupal 8.x-1.x version of the module
• Update the documentation on Drupal.org
• Not have any duplicate issues on Drupal.org

• Read more about Automatically post to BlueSky
• Add new comment

Since the 2024 election, the BlueSky social network has exploded in popularity, and appears to be replacing the cesspool that used to be Twitter. I'm not much of a social media person -- I much prefer hanging out in smaller spaces with people with shared interests. If you're like me, I would highly recommend finding a Mastodon server that caters to your interests, where you're sure to find rewarding conversations.

It’s day 20 of the Drupal Advent Calendar, and today we’re looking at the admin UI Navigation. Joining us today are Pablo López and Matthew Oliveira, so let’s look into it…

The aim of the Navigation track is to provide a better site management experience for Drupal users. It does not provide a specific recipe or feature to Drupal CMS. Navigation is a core experimental module. However, the Navigation track provides key integration points to Drupal CMS that will help other tracks to highlight their features in the new Navigation left sidebar.

Since Navigation has replaced Toolbar in Drupal CMS…

Tags

• Navigation
• Admin UI
• Administration
• New Admin Toolbar
• Drupal Starshot

This year, we lived to see the release of a new version of Drupal. Drupal 11 brought many new features, such as intuitive menus and ready-made configurations (called recipes), making it an even better choice as a platform for building a dedicated CMS. How does this system differ from previous versions, and how can you take advantage of its capabilities when building your website? Find out why you should consider choosing this system or upgrading to Drupal 11.