Jeroen Schmit

Make the <a href="https://wordpress.org/plugins/timber-library/" rel="ugc">Timber</a> plugin work with Jetpack’s Photon. Once installed, all TimberImages use Photon as a CDN and for image manipulation (eg. resize).
<a href="http://jetpack.me/support/photon/" rel="nofollow ugc">Photon</a> is an image acceleration and modification service for Jetpack-connected WordPress sites. Converted images are cached automatically and served from the WordPress.com CDN. Photon is part of the Jetpack plugin and completely free.
<h3>What does it do?</h3>
Timber with Jetpack Photon extends the current TimberImage class to use Photon to serve and manipulate your images:
<ul>
<li><code>{{post.thumbnail.src}}</code> returns a Photon URL</li>
<li><code>{{post.thumbnail.src|resize(100)}}</code> returns a Photon URL</li>
<li><code>{{post.thumbnail.src|resize(100,200)}}</code> returns a Photon URL</li>
</ul>
A Photon URL looks like this:
//i0.wp.com/www.slimndap.com/wp-content/uploads/2014/05/slimndap.png
Requires the <a href="http://jarednova.github.io/timber/" rel="nofollow ugc">Timber plugin</a> by <a href="https://profiles.wordpress.org/jarednova/" rel="nofollow ugc">Jared Nova</a> and the Jetpack plugin with Photon activated.
Contributors welcome
<ul>
<li>Submit a <a href="https://github.com/slimndap/TimberPhoton" rel="nofollow ugc">pull request on Github</a></li>
</ul>
Author
<ul>
<li><a href="http://slimndap.com" rel="nofollow ugc">Jeroen Schmit, Slim & Dapper</a></li>
</ul>

Timber with Jetpack Photon

Plug-in to use JetPack's free Photon image manipulation and CDN with Timber.

Philip Newcomer

When developing locally, it’s common to use a database dump from a production site. With large sites, it’s also common that the production site’s image uploads cannot be easily copied to the local environment, because there are simply too many of them.
While local environments like <a href="https://github.com/Pilothouse-App/pilothouse" rel="nofollow ugc">Pilothouse</a> allow you to easily proxy image uploads to your local environment from the production site, that doesn’t work so well if you add or change one of the registered thumbnail sizes in your local copy of the theme, since the new thumbnail size can’t be proxied from production as it doesn’t exist there. You’re also not able to regenerate the needed thumbnail sizes locally, because the original image file is not present locally.
CDN Image Proxy solves this problem by using <a href="https://jetpack.com/support/photon/" rel="nofollow ugc">Jetpack Image CDN</a> (formerly Photon) to proxy image uploads from your production site. Jetpack Image CDN will automatically generate and serve any required thumbnail size on-the-fly, but CDN Image Proxy will tell it to look for the original image on your production server, rather than on your local URL.
The result is that you can add or change registered image sizes locally whenever you want, and Jetpack Image CDN will generate and provide a CDN URL for whatever thumbnail size is required, sourced from the original image file located on the production site.

CDN Image Proxy

Use Jetpack Image CDN (formerly Photon) to proxy image uploads from another site.

Timber with Jetpack Photon vs CDN Image Proxy