Because of its MVT architecture, which is a variation of the MVC architecture, Django is said to as a loosely linked framework. It aids in the separation of server and client-related code. Django’s models and views handle the server-side functionality, such as obtaining records from a database, while the templates are largely HTML and CSS that just need data from models handed in by views to render them. Django is said to as a loosely connected framework since these components are self-contained.
A loosely coupled system is one in which the individual components are not so thoroughly bound together that a change in one breaks the other. You should be able to interchange pieces like legos without having to redesign the entire world.
A good example of this would be MVVM architecture, where you have a UI piece (A view) and a back-end piece that handles any data presented on that view (the viewmodel). This pattern is designed to be loosely coupled, so that you can swap out one viewmodel for another at any time without having to redesign the UI.
A loosely coupled system is much easier to maintain, because the components can be isolated from one another much more easily.