Our family of watermark parameters allows users to add watermarks as text or images and control the positioning, size, alignment, and transparency of the watermark separate from the base image. We’ve now added two new watermark parameters to provide greater flexibility for users looking to add custom watermarks to their images: mark-tile and mark-rot.
This post gives a brief overview of how the new parameters can be used to tile a watermark across an image and customize the rotation of a watermark.
We’re constantly soliciting user feedback to ensure we provide tools that serve the diverse needs of the developer community. Our users have asked for support for Angular applications, and we listened. Today we’re announcing the launch of an Angular Client Library for imgix. This addition to our suite of SDKs will allow developers to easily serve images in their Angular applications.
This post walks you through the features of our new Angular library, including placeholders and lazy loading.
Last month we released new parameters to give you more control over the framing of your images. Before, it was only possible to add uniform border and padding to images. This made it difficult to achieve certain visual effects and layouts using the imgix rendering API. With the new parameters, you can now adjust each side of an image where border or padding is applied.
This post provides an overview of how to customize image borders and padding using the new parameters.
Earlier this year, the imgix SDK team rolled out a new feature across all core libraries to help users build responsive images more easily: automatic srcset generation. However, this functionality only allowed users to generate one of two default srcset attributes: one for fluid-width1 images and one for fixed-width2 images. Although we were confident that these default srcsets would fit a majority of use cases, we thought the developer experience was a bit lacking. This motivated us to expand the SDK srcset-building interface to provide more flexibility in how srcsets are generated.
With the launch of our Image Manager and Source management API, we wanted to ensure consistency across all of our APIs and make the experience as user-friendly as possible for developers. To that end, we have launched a new API version and will be deprecating our legacy API keys in March 2021.
In this post, we’ll walk you through the advantages of our new APIs, how to move to the new version, and the deprecation timeline.
As we continue to roll out more features (like the Source API and the public launch of the Image Manager), our old permissions model where the roles were Owner, User, Billing, and Read-Only has become too limiting. For instance, there isn’t a way to grant a user access to Sources and Billing without elevating them to an account Owner, which automatically confers additional privileges you may prefer not to grant.
That’s why we have improved the way we handle user permissions—now account Owners can assign users any of the following permissions: