You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
● cli → kubectl · change it any time with /sett… tab panes · enter open · ctrl+p search · f fin
59
-
```
30
+
<divalign="center">
60
31
61
-
<sub>Real frame, rendered headlessly by `just shot` - every screenshot in these docs is generated from the code, never hand-drawn.</sub>
32
+
<imgsrc="assets/screenshot.png"alt="k10s running in a terminal: resource sidebar, pod table with live status, and an action pane for the selected pod"width="960">
33
+
34
+
<sub>A real terminal capture of `k10s` running - `just screenshot`, on the offline demo backend. Every frame in these docs comes out of the running binary, never hand-drawn.</sub>
35
+
36
+
</div>
62
37
63
38
## Why k10s
64
39
@@ -298,12 +273,15 @@ The barrier is low on purpose. `just` lists every recipe:
298
273
```bash
299
274
just dev # run from source
300
275
just shot 140 44 # render one frame headlessly - no TTY, no cluster
276
+
just screenshot # capture the README hero from a real terminal (vhs)
301
277
just check # fmt + vet + test, in the order that fails fastest
302
278
```
303
279
304
280
`cmd/shot` is why UI work here is pleasant: you can iterate on layout, replay
305
281
keystrokes (`just shot 140 44 j,j,d`) and diff frames without a terminal or a
306
-
cluster. Every screenshot in this README came out of it.
282
+
cluster. Nothing in these docs is drawn by hand - the frames come from that
283
+
renderer, the hero image from `just screenshot` driving the real binary in a
284
+
real terminal.
307
285
308
286
Good first issues live in [roadmap.md → possible next
309
287
steps](docs/roadmap.md#possible-next-steps): more kinds, click-to-sort
0 commit comments