If you've worked with large Django projects, you probably know how quickly things can get hard to navigate.

How to get rid of the pain in large Django projects? Evrone developer Pavel Kutsenko decided to explore this and built next•dj.

Here's how he explains the problem and the solution:

"The real pain shows up on large projects – too many views, templates and handler functions scattered across different locations, and maintaining a 100k+ codebase becomes a nightmare. My project next•dj is built around file-routing architecture, where each block has its own URL prefix (on large projects, you sometimes have a microfrontend for different parts of the site). It includes static files (version 0.5.0 introduced the ability to store and process them right next to the page and component), form logic, templates, and context handler functions – what else do you need to be happy?"

Pavel started the experiment in the summer of 2025. In March of this year, versions 0.4.0 and 0.4.1 were released. The key update is the component system – a reusable UI block now lives in one place, with props, slots, and dependency injection. They also added a global NEXT_FRAMEWORK configuration, similar to DRF, keeping all settings in a single place.

The project is already on GitHub. It's a layer on top of Django that reflects this approach and might be useful if you've run into similar issues.

Come try it, fork it. More details on our website: https://evrone.com/blog/next-dj