Sascha Eggenberger
Sascha Eggenberger. Senior User Experience Designer @unic @Drupal Contributor. Drupal Design System, Claro, Gin. #OpenSource

The default Drupal administration interface looks dated in terms of modern design standards. It’s time to change that.

Image for post
Image for post
The Gin Admin Theme

Gin is based on Claro and delivers an all-new admin experience for Drupal 8 & 9. Gin brings a refreshed, more modern and fully customisable experience onto the table.

A radical new design

“Is this really Drupal?” is one of the most often heard reactions I usually get when I present the Gin Admin Theme to people. A radical redesign which will delight content editors, site builders and site admins. The editorial experience is at its core of Gin’s adjustments.

Image for post
Image for post
New Content overview

The design for the content is oriented at classic powerful editing tools which users know best like MS Word or Google Docs. The most important functions like the published state, Preview & Save are always on hand as they’re sticky at the top of the node edit form. …

You just upgraded your brew packages and composer updated itself to version 2.x but you still need version 1.x? This is how you can downgrade (& upgrade again):

brew log composer

For me the latest 1.x version to date is: composer 1.10.15

composer self-update 1.10.15
composer self-update --rollback

If vagrant does not run on macOS 11 Big Sur and you’re not able to update it’s plugins, follow this guide.


If you use brew for ansible etc. Make sure brew works under Big Sur:

Update vagrant

First make sure you have the latest version of vagrant.
Download the latest version from:
vagrant plugin update

You should get a message like

Updated 'vagrant-share' to version '1.1.11'!
Updated 'vagrant-vbguest' to version '0.28.0'!

Now try it again.

vagrant up

It now should work just fine.

If you encounter issues with brew on macOS 11 Big Sur, than it has a high chance of being a similar issue that I ran into.

One of the many error messages regarding brew on macOS 11:

Traceback (most recent call last):
11: from /usr/local/Homebrew/Library/Homebrew/brew.rb:23:in `<main>'
10: from /usr/local/Homebrew/Library/Homebrew/brew.rb:23:in `require_relative'
9: from /usr/local/Homebrew/Library/Homebrew/global.rb:37:in `<top (required)>'
8: from /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
7: from /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
6: from /usr/local/Homebrew/Library/Homebrew/os.rb:3:in `<top (required)>'
5: from /usr/local/Homebrew/Library/Homebrew/os.rb:21:in `<module:OS>'
4: from /usr/local/Homebrew/Library/Homebrew/os/mac.rb:58:in `prerelease?'
3: from /usr/local/Homebrew/Library/Homebrew/os/mac.rb:24:in `version'
2: from /usr/local/Homebrew/Library/Homebrew/os/mac.rb:24:in `new'
1: from /usr/local/Homebrew/Library/Homebrew/os/mac/version.rb:26:in `initialize'
/usr/local/Homebrew/Library/Homebrew/version.rb:368:in `initialize': Version value must be a string; got a NilClass () (TypeError)

How to fix this?

sudo rm -rf /Library/Developer/CommandLineTools
sudo xcode-select --install
brew upgrade

Note: I had to run it twice

/bin/bash -c "$(curl -fsSL"

Test if brew works

brew doctor

Now brew should work just fine under macOS Big Sur!

In this guide I’ll show you how you can setup Matomo Analytics together with Drupal (will work fine with other systems with some minor adjustments, too) to be GDPR compliant and to respect the “Do Not Track” (DNT) setting of your users.


  1. Make sure you’re using the EU Cookie Compliance module.
  2. Set the module up to your liking.
    This module will provide you with a customisable consent banner

Note: I’ve added the Matomo tracking code with a simple JS file, but if you like to configure Matomo on the Drupal backend you can also install for that

Matomo Analytics

Matomo already provides you a setting to respect users with a “Do Not Track” (DNT) header set. But to also not bore those users with a cookie consent banner we need to do some adjustments. …

Sometimes Time Machine backups can take a while. The backup process is getting throttled and therefore has not a very high priority.

But you can allow the Time Machine process to gather a higher priority and therefore speed up the backup overall with the following command:

sudo sysctl debug.lowpri_throttle_enabled=0

To set the process back to it’s original priority we can just set it back to 1.

sudo sysctl debug.lowpri_throttle_enabled=1

For me this speeded up the backup process by other 100%.

See also my tutorial on how to setup a Raspberry Pi 4 as a Time Machine server:

Time Machine is built into the system of macOS and I’m using it since the early days of Mac OS X Leopard. If you have a Raspberry Pi (or two) lying around at your place like me, this tutorial comes in handy to create a cheap and speedy backup solution.

Image for post
Image for post


Make sure your Raspberry Pi is running on the latest software.

sudo apt-get update && sudo apt-get upgrade

We’re going to first install Samba (for SMB) which is a very popular Open Source file sharing protocol which is officially supported by Time Machine for backing up data over a network. …

Image for post
Image for post

Chrome 56 executes some computations to make the scroll position stay in the same position. This currently looks like this:

Image for post
Image for post
Current behavior in Chrome 56+
Image for post
Image for post
Expected behavior

How to change this behavior?

overflow-anchor to the rescue!

overflow-anchor: none;

It’s as easy as this. The result now looks again like this:

Image for post
Image for post
with overflow-anchor set to none

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store