Django Deconstructed exists to answer a simple question that I had when first starting out with the Django framework.

How does Django work?

Most of the information available is focused on how to use Django as a tool, but my interest is deeper, specifically, how to build a framework like Django.  Not because I intend to make a full framework from scratch, but because understanding how this widely-used tool is architected and built is not only interesting, but extremely educational in terms of understanding software design and architecture. And yes, if you really understand how it was built, then it’s going to be easier to use it effectively.

My process for Django Deconstructed is straightforward: pick an area, dive into the docs and source code, deconstruct how that area functions at a code level, and then write up my findings in (hopefully) easy to understand language. This way even if your idea of a fun afternoon isn’t mapping out object relationships in source code submodules, you’ll be able to get a more clear picture of what is really going on inside the computer.

So in the name of applied curiosity, I hope you’ll join with me as we deconstruct Django.