A few weeks ago I had the pleasure to present to DjangoCon US 2016 about how the technology team at Stratasan delivers front-end assets. We've honed this process over the course of a year and are happy with the flexibility and simplicity it allows us. We believe providing concrete examples taken from our codebase will benefit the community.
You can find my slides here.
A brief primer
Any modern, interactive web application is built in two parts: the back-end and front-end. The back-end runs on invisible servers and implements the majority of the business logic. Back-ends can be written in a variety of languages. At Stratasan we proudly use Python and Django as our web framework. Django provides a large number of tools around building websites and lets us focus on our business.
Playing nicely together
Second, technology teams no longer are only comprised of back-end developers but also include front-end developers and depending on the size of the application, operations engineers who focus on the stability of the application and invisible tooling that makes everything happen. Given this, we should strive for workflows that make sense to everyone, minimize the chance for downtime and make it as easy as possible for all team members to deploy new features.
In the next few posts, we'll describe (in full technical glory) our process for bundling assets, how we tie that into our main Django application and a few little niceties we've built into our deployment process to help our team be as confident as possible we deploy new features to our customers.
Article by Scott Burns, VP of Engineering for Stratasan