Konstantin Obenland

Erick Hitter

Adam Silverstein

Brandon Kraft

Pascal Birchler

Ipstenu (Mika Epstein)

Michael Arestad

Mark Uraine

Johan Falk

Shiny Updates is a WordPress Core Feature Plugin.
It replaces The Bleak Screen of Sadness™ (example) with a simpler and more straight forward experience when installing, updating, and deleting plugins and themes. 
Progress updates for these actions don’t add a benefit, they are disruptive and confusing. Shiny Updates deals with these details behind the scenes, leaving users with clear actions and results.
Development for this plugin takes place at GitHub. 
To report bugs or feature requests, please use <a href="https://github.com/obenland/shiny-updates/issues" rel="nofollow ugc">Github issues</a>.
<h3>Testing</h3>
We need help testing the user flows! Please <a href="https://wordpress.org/plugins/shiny-updates/" rel="ugc">install the Shiny Updates plugin</a>, run the tests below, and share your feedback in the <a href="https://wordpress.slack.com/archives/feature-shinyupdates" rel="nofollow ugc">#feature-shinyupdates</a> channel in Slack or <a href="https://github.com/obenland/shiny-updates/issues" rel="nofollow ugc">create an issue on GitHub</a>.
Update core
<ol>
<li>If you have any themes or plugins that need updating, update them. If you don’t have any that need updating, you can edit the them and change the version number to something older. Once saved, they will show as needing an update.</li>
<li>Update one specific item, a theme or a plugin.</li>
<li>Try updating all items in the table.</li>
<li>Share your feedback. Or if you found a bug, <a href="https://github.com/obenland/shiny-updates/issues" rel="nofollow ugc">create an issue on GitHub</a>.</li>
</ol>
Questions
<ol>
<li>What were the noticeable differences in the new install/update/activate/delete process compared to the old one without Shiny Updates?</li>
<li>How did installing and activating a plugin or theme go? Was it difficult or easy? Was it faster or slower than expected?</li>
<li>Do you have any further comments or suggestions?</li>
</ol>

Shiny Updates

Why isnt this in core, who wants to see the ugly installation screen ? the only thing i would be worried about and hopefully is considered if there is a problem with installation does it give a valuable error ? other than that we must get rid of the ugly install screen's



Needs to be in core

A smoother experience for managing plugins and themes.

Delicious Brains

Brad Touesnard

Image Processing Queue is an alternative to on-the-fly (OTF) image processing (e.g. <a href="https://github.com/syamilmj/Aqua-Resizer" rel="nofollow ugc">Aqua Resizer</a>) 
for WordPress themes.
Like OTF image processing, it allows theme developers to define image sizes for specific theme 
contexts rather than defining a size for all uploaded images. This greatly reduces the number of 
resized images and hence reduces disk space usage and the wait time when uploading an image.
Image Processing Queue differs from OTF image processing in how it behaves when an image doesn’t 
exist yet. OTF generates the image right away and the end-user has to wait for the image to be 
generated. With Image Processing Queue there’s no waiting. It immediately returns an image that 
already exists (that is the closest fit to the image size requested) and adds the image size to 
a queue. Image sizes are quietly generated in the background using <a href="https://github.com/A5hleyRich/wp-queue" rel="nofollow ugc">WP Queue</a>.
Image Processing Queue also accommodates responsive themes much better than OTF. It allows theme 
developers to define a list of image sizes that will work best for their theme’s responsive 
breakpoints. Images generated by Image Processing Queue are added to the post meta so that WordPress 
core’s responsive functions will automatically add them to the <code>srcset</code> and delete them from the 
filesystem when the image is deleted from the Media Library.

Image Processing Queue

It works!

tbh, it took me a few minutes to fully understand how this library would benefit my workflow and my clients - but once I started to grasp the changes in development and how I wouldn't be running Regenerate Thumbnails every time I needed a new image size, it clicked!

I think with some more detailed documentation and usage examples this could be a near perfect solution to the image size problem in many themes and plugins.



This could be a game changer!

Real intresting approach and something that should be considered for WP Core - especially the Batch Processing Stuff isn#t only useful for images ...

Shiny Updates vs Image Processing Queue