<p dir="auto">Pulling in <a href="https://github.com/jakevdp/JSAnimation">https://github.com/jakevdp/JSAnimation</a> (which hasn't changed in over a year) would greatly enhance the experience of using animations in the notebook with stock matplotlib. Also, like trendvis, oceancm, and viscm, this would move an very useful matplotlib-based tool into our fold.</p>
<p dir="auto">The core implementation of JSAnimation is just two parts:</p>
<ul dir="auto">
<li>A new writer, HTMLWriter, which also includes some icons for the HTML controls</li>
<li>IPython notebook display hook code</li>
</ul>
<p dir="auto">The <code class="notranslate">HTMLWriter</code> clearly makes sense in matplotlib (alongside <code class="notranslate">FFMpegWriter</code>, etc.). I'm not sure what to do with the IPython display code. Adding it as a <code class="notranslate">_repr_html</code> might not be too bad.</p>
<p dir="auto">Thoughts?</p>
<p dir="auto">Trying to make the what's new and following the <a href="https://matplotlib.org/devdocs/devel/release_guide.html#update-and-validate-the-docs" rel="nofollow">update and validate the docs</a> guide and it says:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="comment out the next whats new glob at the top"><pre class="notranslate"><code class="notranslate">comment out the next whats new glob at the top
</code></pre></div>
<p dir="auto">but it's already commented out <a href="https://raw.githubusercontent.com/matplotlib/matplotlib/master/doc/users/whats_new.rst" rel="nofollow">in what's new</a></p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content=".. _whats-new:"><pre class="notranslate"><code class="notranslate">.. _whats-new:
</code></pre></div>
<p dir="auto">Also the instructions in the what new:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="   For a release, add a new section after this, then comment out the include
   and toctree below by indenting them. Uncomment them after the release.

  .. include:: next_whats_new/README.rst"><pre class="notranslate"><code class="notranslate">   For a release, add a new section after this, then comment out the include
   and toctree below by indenting them. Uncomment them after the release.

  .. include:: next_whats_new/README.rst
</code></pre></div>
<p dir="auto">kind of conflict with these instructions from the guide:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="copy the current content to a file in doc/users/prev_whats_new
merge all of the files in doc/users/next_whats_new/ into doc/users/whats_new.rst and delete the individual files"><pre class="notranslate"><code class="notranslate">copy the current content to a file in doc/users/prev_whats_new
merge all of the files in doc/users/next_whats_new/ into doc/users/whats_new.rst and delete the individual files
</code></pre></div>
<p dir="auto">If you do both, you end up with duplicated entries.</p>
<p dir="auto">Also, possibly a separate PR/discussion, but what about having some set of categories for what's new sections?</p>