Dash to Dock turns the GNOME overview dash into a permanent bar

The dash is pulled out of the overview instead of copied

GNOME keeps its application dash inside the Activities overview, which means the launcher is one keypress away from nothing at all. Dash to Dock takes that same widget and moves it to the desktop permanently, so launching an application and switching between windows and desktops happens without entering the overview. The extension does not add a second launcher. It relocates the existing one, which is why the description talks about transforming the dash rather than adding a panel.

That relocation is the whole product. Every setting in Settings.ui, every entry in the schemas directory, exists to tune the behaviour of a dock that GNOME itself does not ship. The result is familiar to anyone who came from Unity or a classic bottom panel, and unfamiliar to anyone who configured GNOME to hide its dash entirely.

dockStruts.js claims screen space, intellihide.js gives it back

The repository is flat and readable: roughly two dozen JavaScript modules sit next to metadata.json, with no bundler in between. Two names describe the geometry work. dockStruts.js deals with reserving a strip of screen so maximized windows do not slide underneath the dock. intellihide.js decides when the dock should be present at all, which is the piece that maps onto the always-visible question most users ask.

Beside them sit the modules that make the dock feel like an application switcher rather than a picture. They include windowPreview.js, appSpread.js, locations.js, locationsWorker.js, fileManager1API.js, desktopIconsIntegration.js, notificationsMonitor.js, dbusmenuUtils.js and theming.js.

SASS selection happens before the stylesheet can compile

The stylesheet is authored as _stylesheet.scss, so a source install cannot skip the compile step. Three implementations are supported: dart-sass, sassc, and ruby-sass. The build defaults to sassc, and the choice is made through an environment variable read before make runs.

export SASS=dart
# or...
export SASS=ruby

Ruby is the one to leave alone. It is deprecated, and the project says so while still accepting it as a value, which is the kind of compatibility that keeps an old laptop building but gives you no reason to stay on it. Every distribution ships at least one of the three, so the variable matters when you want a specific compiler rather than when you are stuck.

make installs into your home directory unless DESTDIR is set

Installation is two commands, and the destination depends on a variable most people never set.

git clone https://github.com/micheleg/dash-to-dock.git
make -C dash-to-dock install

The Makefile checks whether DESTDIR is empty. Empty means a local install, and the extension lands in your own gnome-shell extensions directory under your home. Set DESTDIR and the same target switches to a system-wide prefix, which is what a distribution package build wants. Nothing asks you to choose; the default quietly writes to your account.

After the build the Shell needs a reload. Under Xorg that is the Alt, F2, r sequence followed by Enter; under Wayland you may have to log out and log back in. Then enable the extension through GNOME Extensions or through dconf. The Makefile calls the extension dash-to-dock at micxgx.gmail.com, so that identifier, not the repository name, is what GNOME looks for.

A missing msgfmt stops the build before any extension is installed

The Makefile collects translation files from the po directory, which means the build depends on gettext. If msgfmt is not on the system, make fails with a plain missing-command error:

make: msgfmt: No such file or directory

The fix is to install gettext from your distribution's repository, then run the install target again.

Checking for dart-sass or sassc before cloning saves the debugging round trip.

Source git install and packaged installs take different paths

The source route exists for two reasons: convenience of using git, and testing the latest development version. Both come at a cost the packaged route does not pay. You compile the stylesheet yourself, you reload the Shell yourself, and you re-run make after every pull to see a change. The repository also ships default.nix, so a Nix build can do the same work declaratively, and the README links the extension's extensions.gnome.org listing, with releases tagged extensions.gnome.org-v108, v109 and v110.

That is the real trade. Bundled or distribution-packaged installs arrive compiled, land where the package manager expects, and update with the system. Source installs give you the newest commit and a per-user copy you can edit, at the price of a toolchain in the loop.

Cloning the default branch gives you master, and VERSION decides the label

The build instructions say to clone the desired branch, but the clone command shown clones the default branch, and that default is master. No command in the documentation picks a branch by GNOME version, so the branch that gets installed is whatever master currently holds. Meanwhile the published releases are tagged extensions.gnome.org-v108, v109 and v110. The Makefile adds a third mechanism: the current commit SHA becomes the version string, which makes every local build report a different version. Two versioning schemes coexist in the same repository, and only one of them is reachable from the documented command.

This is also why the version string behaves oddly. Passing VERSION to make sets it in the metadata and in the generated zip. Pass nothing and the Makefile substitutes the current commit SHA as the version, while the zip file gets no string attached at all. If you package this for more than one person, set VERSION yourself.

Editorial conclusion

Adopt Dash to Dock if you run GNOME and want the dash docked, accept compiling a stylesheet, and are willing to reload the Shell after every source update. Stay on the overview if you dislike a permanently reserved strip, or use a distribution package instead of git when you want updates handled outside your own build. Before switching, verify that a SASS implementation and gettext are present; confirm your build actually compiled the stylesheet before you spend time on preferences.

Frequently asked questions

Official sources

1. License: GPL-2.0
2. micheleg/dash-to-dock on GitHub
3. Project website
4. README
5. Releases