The short version
Keyframe is a blog about motion. Not the philosophical kind, the literal kind: pixels that start over here and end up over there, and the small decisions that make that trip feel deliberate instead of like a bug someone forgot to fix.
It started in the Flash era, which is a sentence that now needs a footnote. For about a decade, if something moved smoothly on the web, there was a decent chance it had ActionScript underneath, a timeline somewhere, and a person nearby who held strong opinions about easing. The runtime is gone. The opinions survived.
What this is actually about
Tools are temporary. A menu still has to open without startling anyone. A button still has to admit, out loud, that you clicked it. Motion still has to obey physics that nobody voted on, because the human eye files constant speed under broken and there is no appeals process. We write about that layer, the part that outlives whatever framework happens to be winning this quarter.
Some of the tutorials here are ancient, and they are kept on purpose. The code targets a runtime you cannot install anymore, which is fine, because the ideas were never really about the runtime. Ease-out is ease-out. Loading a menu from XML instead of hardcoding it was a good instinct in 2007 and it is the same good instinct today, just with different punctuation.
Who writes it
One person who has shipped enough interfaces to be deeply suspicious of the phrase it looks fine. The comedy is included at no extra charge, mostly because motion work is five percent inspiration and ninety-five percent nudging a single number by one pixel and reloading to see if that fixed it. It did not. Nudge it back.
No newsletter wall. No cookie-banner theatrics. Read what is useful, ignore the rest, steal the code.