About
What Phosphor Works is making and why.
What
Phosphor Works makes a Linux desktop built around window placement. Where a window goes and how it gets there is the first decision, and the shell, the compositor and the tools are designed around it.
- Phosphor, wayland compositor. In design.
- Lambent, desktop shell. In development.
- PlasmaZones, window management. Released (3.5.5).
- Afterglow, terminal. In development.
- Facet, settings manager. Planned.
- Limn, text editor. Planned.
- Glisten, screen capture. Planned.
- Cresset, file explorer. Planned.
- Illume, image viewer. Planned.
Underneath are 64 focused libraries, each with a narrow public API and one role. The apps share them, and other Qt projects can use them too.
Where it came from
PlasmaZones started as a scratch-my-own-itch project. After moving from Windows to KDE Plasma, the one tool I kept reaching for and couldn't find was FancyZones: hold a modifier, drag a window across named regions, drop it into one and have it fill the zone. Plasma had tiling scripts and KWin effects, but nothing that gave the same direct drag-to-snap workflow. PlasmaZones was written to fill that gap and grew from there into autotiling, layout editing, shader effects, and multi-monitor zone assignments.
As the app grew, enough of its internals were already shaped like libraries that it made sense to treat them that way. Layer-shell hosting, shader compilation, tiling algorithms, zone persistence, and global shortcuts each got lifted into their own library. That split finished in 2026 and the libraries now live under the phosphor-works umbrella. PlasmaZones remains the flagship consumer, and the same libraries are open for other Qt projects to build on.
Owning the placement engines made a bigger idea possible. A shell that shares them can draw your real layout in its bar and place its own panels like windows, which became Lambent. A compositor that runs them in-process removes the last layer in between, which is the Phosphor compositor. Afterglow and Facet fill in the tools you use every day, and Limn, Glisten, Cresset and Illume are planned to join them for text, screenshots, files and images.
Design principles
- One library, one responsibility. If a piece can be used without the rest, it's its own library.
- Interfaces first. Every non-trivial subsystem ships an abstract interface so apps can mock or swap any implementation. Clients depend on
ILayoutManager, notJsonLayoutManager. - Wayland-native. No X11 fallbacks in the public API. XWayland clients work as windows within a Wayland session; everything else is layer-shell, compositor protocols, and QtWaylandClient.
- Scriptable extension points. Tiling algorithms are Luau scripts in a sandboxed VM. Shader effects are plain GLSL 450 files with a metadata manifest. No recompile needed to customize either.
- Readable over clever. The libraries skew toward code that reads well in review. Compile-time tricks are reserved for the handful of cases where they actually pay for themselves.
Who builds it
Phosphor is developed by fuddlesworth with community contributions. The source and issue tracker for PlasmaZones live at phosphor-works/PlasmaZones; the library split and the website live under phosphor-works.
License
- Libraries: LGPL-2.1-or-later, so projects under other licenses can link them.
- Apps: GPL-3.0-or-later.
- Brand assets: CC-BY-SA 4.0, hosted at
phosphor-works/branding. Logos, icons, and color tokens are yours to use with attribution. - Docs: the content of this website is GPL-3.0-or-later alongside the rest of the code.
Contributing
Issues, pull requests, packaging, and documentation are all welcome. The contributing page summarizes where to file what, the commit-message convention, and the build + test flow; the full CONTRIBUTING.md in the PlasmaZones repo has the canonical details.
AI disclosure
Some of Phosphor's code and docs are drafted with AI coding assistants, then reviewed by a human before they land. The AI disclosure page describes how that process works and what it does not cover.