---
title: Hyprland Ecosystem Overview
url: https://doc.liz6.com/en/tools/hyprland/01-overview
locale: en
area: tools
tags:
- tools
- hyprland
date: null
modified: 2026-07-16
description: A mental model for the Hyprland desktop — compositor + shell + theming engine + a suite of companions, and how they fit together.
---

# Hyprland Ecosystem Overview

Hyprland itself is merely a tiling compositor, responsible only for window management. A complete desktop is assembled from four components. Understanding their division of labor will make the following articles easier to read:

- The compositor [Hyprland](02-hyprland.md) manages windows, input, keybindings, and multi-monitor setups;
- The shell [Quickshell](03-quickshell.md) provides the "visible desktop" elements such as the top bar, sidebars, control center, and notifications;
- The theming engine [matugen](04-waybar-theming.md) derives a color palette from the wallpaper and distributes it to all components;
- [A suite of companions](05-companions.md) fills in the gaps: lock screen, screen blanking, wallpaper, launcher, power menu, and input method.

What ties them together is the theming pipeline. When you change the wallpaper, matugen recalculates the Material You palette and distributes it—Quickshell reads its `colors.json`, Ghostty changes its color scheme along with its open windows, and the lock screen, launcher, and input method follow suit. The result is a unified color scheme across the entire desktop, without me ever having to manually fill in color values.

```mermaid
flowchart TD
    WP[Change Wallpaper] --> MG[matugen]
    MG --> QS[Quickshell Shell]
    MG --> GT[Ghostty Real-time Theming]
    MG --> X[hyprlock / fuzzel / fcitx5 / GTK / Zellij]
    HL[Hyprland · hyprland.lua] --> QS
    HL --> CMP[hypridle / hyprlock / hyprpaper / walker / wlogout]
```

The other thread concerns the ownership of visual aesthetics: rounded corners, borders, blur, and animations are uniformly handled at the Hyprland layer. Applications like terminals focus solely on content (which is why [Ghostty](../ghostty.md) can appear completely bare without decorations). Furthermore, the `hjkl` movement keys flow seamlessly from [nvim](../nvim/01-overview.md) all the way to window focus. With a single source for theming, a single owner for visual aesthetics, and a unified vocabulary for movement keys, the desktop remains cohesive.