We now have a Django project for our overall ShapeEditor system. We next need to break down our project into several related applications, following Django's design philosophy of having applications be small and relatively self-contained. Looking back at our design for the overall project, we can see several possible candidates for breaking the functionality into separate applications:
Let's choose some names for our applications, keeping them short and to the point:
We will define one more application, which we'll called
shared, to hold the database models and Python modules that are shared ...