Oh, this is neat.

I do kind of wish that there was more of a summary of how it works on the page from a user standpoint. For example, the page links to niri, which the author previously used. That describes the basic niri paradigm right up top:

Windows are arranged in columns on an infinite strip going to the right. Opening a new window never causes existing windows to resize.

Every monitor has its own separate window strip. Windows can never “overflow” onto an adjacent monitor.

Workspaces are dynamic and arranged vertically. Every monitor has an independent set of workspaces, and there’s always one empty workspace present all the way down.

The workspace arrangement is preserved across disconnecting and connecting monitors where it makes sense. When a monitor disconnects, its workspaces will move to another monitor, but upon reconnection they will move back to the original monitor.

I mean, you can very quickly skim that and get a rough idea of the way niri would work if you invested the time to download it and get it set up and use it.

It does say that reka uses river, and maybe that implies certain conventions or functionality, but I haven’t used any river-based window managers, so it doesn’t give me a lot of information.