V2 json#1
Open
githubflyideas wants to merge 5 commits into
Open
Conversation
- Tier now walks one target at a time with a pause between them, and pauses again every few file rewrites. Doing all targets in one burst rewrote dozens of day files back to back, which on a box also serving charts showed up as a nightly IO spike. - removed config.example.jsonc (config files were dropped back in v2.1, nothing reads it) and five unreferenced hero images; README only uses hero8 and hero9 - clean.sh stays: file storage still benefits from a manual purge tool
Same work as main's colour and typography passes, brought over to the JSON-storage line: the temperature-ramp smoke (hot core, cooling edge, distinct hue from the median line), the sans/mono split for interface vs numeric text, the real type scale, and body contrast pulled from ~13:1 to 9.5:1. - five themes: dark, daylight, arctic, budapest, amber (solarized and nord retired, matching main) - login.html carried the same core colours and now supports all five themes instead of two; button and label typography updated to match the main page Verified: body 9.5:1 on every theme, trace-vs-cloud-core >= 2.2:1, 112 hex values across both files with no malformed ones, build and tests pass. CSS/colour values only — no JS or Go logic changed.
v2.11.0's release job failed on the tap-push step (stale/insufficient TAP_TOKEN), even though the four tarballs it needs to build first came out fine and are what people actually download. scp-and-run is the primary path; brew was always an extra, not worth carrying a second token for. Dropped brews: entirely — archives, checksum, and the GitHub release stay as they were.
Root cause of 'nord/dark/solarized look identical': the last port only updated the
CSS palette blocks (daylight/arctic/budapest/amber) but left the THEMES array naming
the OLD set (nord, solarized). Selecting either did nothing - no matching CSS rule
existed, so the browser silently fell through to the unstyled root/dark variables.
That is why they looked the same as dark: they WERE dark, just mislabeled.
Fixed the array to match real definitions, and took the chance to give v2 its own
identity instead of reusing v3's Bauhaus/Anderson framing:
terminal - a trading-desk screen at 2am; amber trace, slate-blue cloud sinking
to navy (replaces dark/root)
newsprint - broadsheet market page; near-black ink trace, cloud runs brick to
warm halftone grey (replaces daylight)
ukiyo - Hokusai's indigo woodblock prints; deep aizuri trace on washi paper,
cloud runs Prussian blue to pale moss (replaces arctic)
memphis - Sottsass's 1980s Milan collective; coral trace against soft lavender-
grey, teal cloud instead of the expected pink (replaces budapest)
phosphor - P1 green CRT, amber's mirror image: green trace, amber-to-rust cloud
instead of the usual green fade (replaces amber)
All five verified: body contrast 9.5-11.6:1, trace-vs-cloud-core >= 2.0:1,
cloud-vs-background >= 1.5:1. 78 hex values checked, none malformed. login.html
carries the same core colours and the corrected theme list. Colour values and the
theme-name array only - no rendering logic touched.
…ogping cross-link - .mark grown from 19px to 26px, close to the metric readouts (30px) instead of reading as a subtitle. It was too easy to miss at a glance, which is the one job a wordmark has. - the dot after 'pingping' now alternates the same green/red already used for host status (healthy/down), so the letterhead uses a colour vocabulary the reader already knows instead of inventing one. Respects prefers-reduced-motion. - tagline: 'One binary. One graph. One metric: Latency.' replaces 'Zero guesswork.' (updated in both the visible tag and the share-intent text) - sponsor bar gains a 'Powered by Fogping' link next to Star on GitHub, pointing at the sibling project. Verified in a headless browser against a real build: mark renders at 26px, the blink dot is present, tagline and Fogping link resolve, zero console/page errors.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.