Dynamic rendering at scale with HelloFresh

Without further ado, Pep, you want to kick us off? You want to share some slides and and talk about all the work that you've been up to over at HelloFresh? Yeah, awesome. Thanks. Um, I'll go ahead and just like let's get started right away. Um, so, uh, thanks again for to Matt and Purcell for having me. Um, this is basically a story from, uh, going from static mostly static, uh, content to dynamic. Um, and uh just to kind of like make sure

we're all on the same page with dynamic, I mean you see something else and some the other person if they open the laptop next to you hopefully. And static is really everybody gets the same thing. So there we go. Um, I'm quite new to Zoom, so if something goes wrong, Matt, just let me know, please. Yeah, we'll we'll if you have Zoom hot tips, put those in the in the chat, not in the Q&A. So yeah, let those let those do hot tips uh or any memes put those in

the in the chat, not in the Q&A. Um cool. Just I guess a quick introduction. Yeah. Yeah. Intro Pep, give us you're going to give us an introduction. I'll give an introduction myself. My name is Matt here. I'm on the sales engineering team at Forcell. I help customers and folks like who are in Pep's situation help them make the most out of Versell. Um, in HelloFresh is like one of our favorite examples and Pep has done an absolutely incredible job walking Hello like taking HelloFresh from their static experience to a dynamic experience. We're going to learn all about that today. Um, but yeah, Pep, tell us get us started. We're like this is our agenda. What are we going to get into today? So,

uh, I try to give these like agenda a little bit of boot. So, I'll get a little bit more into like what I do and what which which company I work for in a bit. But uh to kind of give you like a teaser, it's fruit related. So first of all, we're going to talk a little bit about like what static rendering really looked like for us and what it means for us. Then we're going to look into like what's like the the main ingredient for change and what what's the the basic

like the the kickoff to you know exploring this route to like dynamic rendering and how what does that look like? Where do you get the right performance bits to really enable that? And in the at the end we'll kind of like walk through like what what percent was there uh in this in this entire journey. So let's get into it. So like our static menu basically what what what why why did we have a static website? Well

hello is not a young company. We've been around for 14 years now. And um like I'm not sure if everybody in this room has been an engineer for that long. Um sadly I have. Um but what that meant is that we basically came with a lot of legacy. I know there's like some ex-colies in the chat as well. They probably are putting plus ones in their mind right now. Um, but what what really what that

really meant in practice is that we had to kind of like opt into static to make sure that we were able to do the things um like we're able to serve some content to our customers. Um, we have uh customers all over the globe. Um, we have um customers in New Zealand. We have customers all the way in California. That's probably well actually I'm Alaska even. So like we we it really goes very far. So we have to

make sure every one of those customers gets like an okay experience and to do that we actually relied a lot on a CDN and a CDN you can just like save your static content there and then the CDN kind of takes care of of it for you to make sure that this this content is served very fast to the customer where it's close to. But that means that it's static because the the personal elements and like the dynamic elements still have to