Last articles

One year ago I started tracking my own contributions to Drupal.org and posting a report on my Mastodon account. See the last quarter of 2025 report as an example. The goal is not to flex (it would be cheating given that Acquia sponsors me for working on Drupal Canvas almost full time); and this is far from being a good way of tracking contributions or your own productivity, but it's better than nothing. 

Still, it helps me evaluate where I've been focusing (out of necessity, from being nerdsniped, or just for fun), and check if I need to balance that for my "volunteer" contributions. In this last year I've been appointed as Drupal CMS committer (which includes maintainership of 20+ projects 😱😱😱), and Drupal Core subsystem maintainer for Content Translation and Language modules. So tracking where my efforts go is really helpful for self-accountability.

And to be fair, I spent more time maintaining this blog than writing, so finding a new topic that is recurrent is a good way to force me to keep it up to date 😅.

In the last 4 quarters I've been tracking this, it's been ~1 credit per day among all projects. Last quarter I had credits at 1295 issues. As of now, it's 1376. So 81 new credits, vs 93 last quarter, which is a little below 1 credit/day.

Breaking those down:

Canvas: 143 (+61)
Core: 150 (+8)
CMS*: 42 (+4)
Dashboard: 61 (+3)

I also enjoy contributing to projects like DDEV, which helps me learn Golang and clear my mind from working on the same stack. Recently I've been working on Add --project/-p flag to ddev exec command to target a named DDEV project from any directory and it was just merged! 

And I've been pushing a bit this quarter to keep the Drupal Canvas development DDEV add-on up to date, with several improvements and releases.

Hope to write again before July 1st!

Happy coding! 🎉🎉

I haven't kept up with updating this blog, so this is a short summary of what happened, and where we are with the Dashboard Initiative.

Our initial goals

When the Dashboard Initiative was announced, the goal was to get this into Drupal Core. 

As with most initiatives, we started in a sandbox, then moved to a contrib module.

Based on the above, our idea was

• providing a very simple Dashboard framework,
• according to Drupal core standards,
• based on layout builder,
• providing a set of blocks that could cover the requirements for 80% of sites
• that users would see first thing when they log in to their site,
• and with nice defaults for the standard profile in Drupal core.

We had weekly meetings, where we worked on defining what the defaults for the Standard profile would be (with Aaron, Cristina and Megh leading the way), while the module was steadily progressing. We attended many events, where we (Cristina, Pablo and I) spoke about the initiative, gathered lots of interesting feedback, and could work on sprints where we got dozens of new contributors to help with the initiative.

Fast-forward to the Drupal Starshot initiative

And that was our plan for DrupalCon Portland 2024. But we were surprised with the Drupal Starshot announcement. Our session about the dashboard, scheduled just after the keynote, was quite an experience for Pablo and me.

The Drupal Starshot initiative has evolved, but its foundation was packaging a new version of Drupal providing a great out-of-the-box experience. So we pivoted and the Dashboard initiative became one of the Starshot Tracks that would become Drupal CMS 1.0.

In a few months we were able to redefine our goals and implement what was needed to launch Drupal CMS on January 2025, which included the Dashboard 2.0.0 first release.

Shortly after, I was appointed as one of the few Drupal CMS committers, which I consider a huge honor. 

Is becoming part of Drupal Core still the goal?

Drupal CMS is the promoted option for downloading on drupal.org. In DrupalCon Atlanta 2025, exploring a marketplace of site templates was announced, which would be based on Drupal CMS 2.0. Given that, having the dashboard as part of Drupal Core shouldn't be a priority, even if it would be satisfying.

In Dries' July 2025 update to the Drupal core strategy 2025-2028, you can find good arguments for both including it or not including it. If I leave my bias aside, I'm 50-50. The tie-breaker would be adoption.

Dashboard adoption

Before 2.0.0 was released, I worked on a proof-of-concept for updating Dashboards with Layout Builder module to be based on Dashboard, to ensure this was possible with an automatic upgrade path. That's feasible, but never really happened.

Of course, Dashboard adoption is great. Even if it's short-lived, since it's part of Drupal CMS and the future site-templates on top of it. So I'm looking at what distributions outside of that are adopting it.

The last releases of the Varbase distribution moved to Dashboard already (and they have been really collaborative on issues on the Dashboard queue, thanks!). 

Drupal Commerce introduced its own dashboard functionality in their 3.x releases ^[1]. I think adoption on high profile distributions/modules like Commerce would help make the point on having this as part of Core. 

Another case I'm looking at is drupal.org itself. With their upgrade to Drupal 10, it is quite possible some kind of dashboard is needed on drupal.org too for feature parity with what we have today. Opening an issue to see if they already have something in mind is on my to-do list.

What's next then?

If we look at our initial goals, providing a set of blocks that could cover the requirements for 80% of sites is not something I'm looking at right now. Thanks to Drupal's new recipes system, I don't think that belongs in the dashboard module itself anymore, but on dedicated recipes (as Drupal CMS proves) or modules.

We've been working on bugs, minor features (like our new coffee integration!), and keeping up with new core releases and PHP new features. We just released 2.1.0-beta1, which should be shortly followed by 2.1.0.

So to be honest, I don't know what's next. Feedback is welcome on the issue queue or at the #dashboard channel on Drupal Slack.
 

^[1] I was corrected that this happened with Commerce 2.37.
 

Photo by Paul Johnson, available for publishing under Creative Commons Licence with attribution via Flickr.

I've been struggling lately with PhpStorm IDE, specially when closing a big project and opening another big one, where sometimes it just hanged (if you are doing Drupal, any Drupal project might fall in this category given the amount of files).

After checking settings, I found out that I had the defaults, while my computer has 32Gb of RAM. 

If you want to play around with the options to see if it improves your experience, go to Help > Edit custom VM options....

It will open phpstorm64.exe.vmoptions where you can customize the VM options. It's important that you save the location of this file, as if your experimenting breaks PhpStorm, you want to be able to edit this outside of it.

I ended up with

-Xms4G
-Xmx8G
-Dawt.useSystemAAFontSettings=lcd
-Dawt.java2d.opengl=true
-XX:ReservedCodeCacheSize=1G
-XX:+AggressiveOpts
-XX:+UseFastAccessorMethods
-XX:+UseStringCache
-XX:+UseCompressedOops
-XX:+UseCompressedStrings

and so far looks like it's working better.

UPDATE: das-peter pointed out about ulimit too for allowed open files. I remember having set up that before because my hard ulimit command inside WSL2 shows:

$ ulimit -H -n
1048576

You can set that with 

$ ulimit -n 1048576