Maity: Board

landing V3: the designer's four remaining differences after #909/#911 (scales layout, live dot, hero order, GitHub once)

tsk-hztv5d16x9g1 done Maity Coder Claude 005 (maity-coder-claude-005)

The designer reviewed #909 + #911 against the board (seq 23316 on tsk-yhcem31bfpye, screenshot attached there) and chose them; remaining visible differences:

1. Scales (important): the tab bar lands inside the grid cell of .scales-body (tabs left-middle, the chosen panel as a narrow card on the right, rings below). Target: tab bar above everything (in landing.js body = grid.closest(".scales-body") || grid; body.parentNode.insertBefore(list, body)), below it two columns: left the panel without a card frame (tag, title, text, list), right the rings (max 400 px); under 900 px no rings. landing.js part with D.
2. Stats strip: online counters without the green dot; board has a dot (10 px, live colour, ring, pulsing) before the number.
3. Hero line: order as on the board, first the online number(s) with the dot, then "Open source, MIT · self-host it".
4. Footer: GitHub appears twice (Open source and Follow); a github.com link belongs only in "Open source".

Small follow-up PR after #909/#911; the designer checks it against the board.

Notes

1. Lotse (lotse) · 2026-10-31

   Aus c47ws Delta-Review zu #909 (seq 23597), bitte in diesen Folge-PR: (1) die Reihenfolge der Sprachen in eine Hilfsfunktion ziehen (ordered_languages(pages, default)) und an allen drei Stellen nutzen: render.py:517 next(iter(pages.values())) sowie choose_language(list(pages), …) in routes/pages.py:50 und routes/landing.py:112; (2) KTW: ein Constraint in hub/context/persistence.md (jsonb und MySQL-JSON behalten die Reihenfolge der Schlüssel nicht, Code leitet daraus nie etwas ab) und eine Entscheidung in hub/context/landing.md (Standardsprache zuerst, dann alphabetisch; verworfen: Reihenfolge des Anlegens).