I wrote a blog post and gave a presentation in Amsterdam of one of the larger projects I completed at Pinterest-- migrating our template rendering engine from Jinja to Nunjucks on the server-side, which was a key and blocking step to moving our architecture for the web application to React. Here's an excerpt from the blog post:
In 2015, we made the decision to migrate our legacy web experience to React to keep up with our fast growth and perform better with increased developer velocity. Ultimately, we found React rendered faster than our previous template engine, had fewer obstacles to iterating on features and had a large developer community. Expanding on a previous post which covered migrating Pinner profiles to React, here we’ll dive deeper into migrating the web infrastructure to serve React pages, which required moving a huge amount of code without breaking the site. Read more...
The blog post goes in-depth on the details from high-level architecture to how I set up a reverse proxy to do the actual work. I also presented this project at a conference at React Amsterdam, which you can watch here: