Cloudinary Integration, Data File Templates and Other Features
Image Transformation and Responsive Image Delivery
Today we’re proud to announce an easy way to optimize your image delivery with a Cloudinary integration for Forestry.
As a developer you can now use the super fast Cloudinary CDN and store your assets outside your repository. While at the same time your editors can use Forestry’s Media Library and Editor to upload and manage Cloudinary assets without even knowing it.
This integration makes it possible to efficiently store, organize and deliver images in Cloudinary while keeping the editing experience simple and clean in Forestry.
Non-developers can continue to use our simple drag and drop feature without having to juggle assets across different accounts and multiple providers.
The Forestry Media Library and Cloudinary are always in sync. All assets on Cloudinary can be accessed through the Forestry Media Library and vice versa.
Instead of only supporting a subset of Cloudinary’s features in our UI, Forestry gives you the maximum amount of flexibility for upload resources. Once you connect Cloudinary to your account, Forestry only inserts the
image_name.extension without any path components into your Front Matter, allowing you to use Cloudinary’s URL-based manipulations.
Here are a few examples of image manipulation via Cloudinary URLs:
Other New Features
We also rolled out a few other features that might be interesting to you.
Front Matter Templates for Data Files
This update allows you to use and change templates for data files.
Until now you weren’t able to use templates with data files and anytime the format of the data files changed a developer needed to go into the code base.
This new field allows your users to easily change colors in a Front Matter Field from within Forestry.
You can add values through HEX, RGB or pick a color from the selector.
OAuth Login for Remote Admin
OAuth login is now available in the remote admin.
You can now login with your favorite Git-provider.
For a full list of changes please check out our changelog
Caught a mistake or want to contribute to the blog? Edit this page on Github!