And these days, if you want a modern, responsive, interactive application—and who doesn't?—your front-end codebase may end up as large and complex as your back end.
const element = <h1>Hello, world!</h1>;
It's the guide I wish I had when I first started bringing React—and later Vue, Sass and other front-end technologies—into my own Django projects. It contains the knowledge I've accrued from 10+ years of working on Django projects big and small.
The guide is broad in scope and so it's broken into several parts.
Part 1 covers our big-picture setup. We'll discuss two common ways of organizing front-end code in a Django project—which we'll call server-first, and client-first. Then we'll outline why neither of these are perfect, and learn how a hybrid architecture can help provide us with the best of both worlds.
Finally, in Part 4 we'll go deep on some real-world examples of a hybrid architecture. We'll discuss many of the common issues that come up and offer design patterns that help address them.
Ready to go? Let's roll up our sleeves and dive in!
Up next: Part 1: Organizing your Front-End Codebase in a Django Project. Or view the complete series below.
The nuts and bolts of integrating our shiny new front-end pipeline into our Django project—and using it to create some simple "Hello World" applications with webpack, React, and Vue.
Learning about hybrid applications by creating a single-page React app. Exploring the common issues that come up and how to solve them.
Subscribe for Updates
Sign up to get notified when I publish new articles about building SaaS applications with Django.
I don't spam and you can unsubscribe anytime.