Closed patrickvonplaten closed 1 year ago
Great point! In recent blog post we've been pushing much more for compressed images as well, as large posts will lead to very slow user experience while reading.
I think we can explore moving assets from our blog posts to a dataset and keeping here the community ones, but we should still aim for very light blog posts.
@simoninithomas I see 70_deep_rl_q_part1 73_deep_rl_q_part2 78_deep_rl_dqn 63_deep_rl_intro @merveenoyan same for 29_streamlit-spaces 28_gradio-spaces And myself for the top one
I think independently of moving these assets to a Hub dataset, it would be good to compress the images/thumbnails for a good experience even with slow connections. Maybe we could take care of the corresponding blog posts mentioned above?
Ok, I cloned the repo. I can reduce some stuff, for instance the gifs.
But most of my folders are 20mb because for instance for deep-rl-q-part1 we have 73 files (jpegs no png).
What we could do as Omar mentioned if the size is too big is to put in a dataset 🤔.
✅ Optimized and deleted some illustrations: #489
closing this as we now require authors to upload their assets to a dataset repo on the hub
BTW, we could do this for thumbnails too in the future, potentially
The blog repo is now ca. 300MB heavy - should we maybe move the images etc... out into a dataset? What do you think @osanseviero ?