Dan Wilson has an intro article followed by a 5-part series all about the Web Animations API. If you were unaware, .animate() is a native thing now. I think there is a ton of interesting things about the Web Animations API, like:

• Yet another great example of how a libraries pave the way, then browsers learn from that and get better. Then:
  

  These libraries can then focus on providing newer features, and the cycle can continue.

• Under the browsers proverbial hood, the Web Animations API powers CSS animations as well.
• Will animation libraries, under their hoods, use this as part of the fallback stack? Or are they seeing equally good or better performance with requestAnimationFrame or whatever they are doing now?
• It’s not every new web feature that has an official polyfill.

Direct Link →