Hello, Technology Enthusiasts!

As summer ☀️ reaches its peak in the Northern Hemisphere and many of you are (hopefully) enjoying a well-deserved break 🌴, we’ve decided to take a slightly different approach with this month’s newsletter.

We did consider skipping the newsletter altogether for the summer, but instead we decided to bring you a little gift. Something light, informative and maybe even helpful to explore while sipping your iced coffee. You’re welcome! 🎆 

So, instead of highlighting new features, we want to share a new section we have added under ‘Useful information’ on our developer site, i.e. how Liquid code and code architecture impact template performance.

🚀 Template performance: How to write performant Liquid code

Template authors generally do not control how templates are rendered. They only have limited building blocks to work with and how templates render and communicate is set in a certain fixed framework. 

That being said, the key element where template authors do have control over, and that actually has by far the largest impact on template performance, is dependencies. 

To maintain strong performance across templates and workflows, it is crucial to minimise dependencies across templates and periods, and to only include those that are absolutely necessary.

☀️☀️☀️

The new page lists some tips&tricks to help you manage dependencies. 

☀️☀️☀️

Moreover, we’ve also dedicated a more low level section with some small tips to improve specific pieces in the Liquid code, e.g.:

• Avoiding unnecessary iterations in loops
• Accessing correct drops
• Reducing code repetition

Let us know what you think—and enjoy the rest of your summer! 😎