Wordmark dot placement — round 3

Why round 2 looked stuck

The dot is an inline-block with overflow: hidden, sitting inside a flex container with align-items: baseline. For that combination, the flex container computes its line baseline from each item's "baseline" — and for an inline-block with overflow hidden, the item's baseline is the bottom margin edge. So when we used margin-bottom: -3px intending to push the dot 3px below baseline, the flex container recomputed the line baseline to follow the dot's new margin edge, effectively cancelling the shift. The dot moved a fraction of what the value said.

Fix: use transform: translateY(Npx) instead. Transforms render after layout — they don't affect flex baseline calculation — so the visual shift is exactly N pixels, every time. All variants below use this method.