A standing invitation rather than a task, and the smallest thing this repo
takes: one JSON file, no Swift, no build, no signing certificate.
The five built-in zone sets — Halves, Thirds, 60 / 40, Quarters, Priority —
are deliberately dull, because they have to be right on every screen. The
interesting layouts are the ones that only make sense on a particular desk: the
ultrawide split that needs 34 inches to work, the rotated monitor, the one
that exists because of a call that happens every morning.
zone-sets/ collects those. It arrives in #27 with eight to start and the
format written down, and each file is valid input to the app's own
/zones/save route as it stands, so anyone can try yours with one command.
How
- Draw it on the Zones page. Nothing has to be typed by hand.
plonk state --json prints zone_sets with the exact numbers the editor
produced.
- Save them as
zone-sets/<slug>.json, in the shape zone-sets/README.md
describes.
node scripts/check-zone-sets.mjs --preview validates it and draws it.
- Open a pull request and say which monitor it is for and what each zone holds.
That last sentence is most of what makes a layout worth copying. A rectangle
means nothing on its own; "the call goes top right because the notch does not
cover it there" is the part someone else can use.
Layouts nobody has yet
- A laptop screen on its own, where Halves is genuinely too coarse.
- Two monitors of different shapes, as a pair meant to be used together.
- A 5K in portrait beside a laptop.
- Anything built around one app that is fussy about its width.
Good ones end up shipping as built-ins. This issue stays open.
A standing invitation rather than a task, and the smallest thing this repo
takes: one JSON file, no Swift, no build, no signing certificate.
The five built-in zone sets — Halves, Thirds, 60 / 40, Quarters, Priority —
are deliberately dull, because they have to be right on every screen. The
interesting layouts are the ones that only make sense on a particular desk: the
ultrawide split that needs 34 inches to work, the rotated monitor, the one
that exists because of a call that happens every morning.
zone-sets/collects those. It arrives in #27 with eight to start and theformat written down, and each file is valid input to the app's own
/zones/saveroute as it stands, so anyone can try yours with one command.How
plonk state --jsonprintszone_setswith the exact numbers the editorproduced.
zone-sets/<slug>.json, in the shapezone-sets/README.mddescribes.
node scripts/check-zone-sets.mjs --previewvalidates it and draws it.That last sentence is most of what makes a layout worth copying. A rectangle
means nothing on its own; "the call goes top right because the notch does not
cover it there" is the part someone else can use.
Layouts nobody has yet
Good ones end up shipping as built-ins. This issue stays open.