We take pride in providing consistent content to our developer community at ZEIT, usually via this blog. Previously, our workflows involved coordinating with our design team in order to add accompanying Open Graph images to our content.
Since most of our social cards look somewhat homogenous, we decided to automate this process by eating our own dogfood and using our platform to meet this need. This takes a load off of our talented design team, and removes a dependency from our developer relations team — allowing us to provide content more efficiently on the whole.
How it Works
Given that lambda size is an important metric on Now, .dom is a delightful tool of choice to render the User Interface of our Open Graph image generator, giving our lambas a tiny footprint, and allowing for an extremely cost-effective deployment.
We appreciate this typeface because of the high degree of legibility it brings across a number of devices while maintaining a beautiful aesthetic and contextual alternatives: like a slash-filled zero when 0 needs differentiating from O.
Now makes use of caching servers to store your content closer to your users. This greatly reduces latency and causes content to reach a consumer as efficiently as possible, providing end-users with a pleasant experience.
In the case of our generator, every time a user generates an image, the image gets cached. Each subsequent user will receive the cached image directly from the caching server nearest to them until it expires. The lifetime of cached assets is configurable via
The header enables use of Now's built-in edge caching. With this, our consumers are able to download our generated Open Graph images in a flash.
We enjoy improving developer experience and workflow automation. This is very much at the core of who we are at ZEIT. We hope you've enjoyed this brief window into how we improve our internal workflows and test our products by eating our own dogfood.