On this page

Updated 19 November 2026

2 min read

Django MVP

Django MVP gives a Django project a finished application shell: a configurable layout, a library of components, menus, icons and enhanced views, styled with Tailwind CSS and daisyUI. Around it sits a family of packages for accounts, forms, charts, payments, compliance and more, each one ready to drop into the shell.

Django has a huge ecosystem but it’s unevenly maintained. Some packages thrive, some are abandoned and most ship only bare templates. Each time I wanted a third-party package in a project, I paid again in integration and template work. Every new project started from nearly zero. Django MVP is the shared starting point I wanted: install it, configure it and start on the part of the project that is actually new.

What it does

  • A settings-driven shell: the layout, navigation and branding are configured in Django settings rather than rewritten in templates for every project

  • A component library: reusable interface components built with django-cotton

  • Menus in Python: navigation declared in code rather than hard-coded into templates

  • Icons by name: use any icon in a template by name, without managing icon files

  • Enhanced class-based views: list views with search, ordering and pagination, plus create, update and delete flows, inline formsets and tables

  • A package family: accounts, forms, charts, payments, compliance and more, built to fit the same shell

My role

I designed Django MVP and maintain it. It began inside FairDM: that framework grew until changing the front end broke the code and changing the code broke the front end. The answer was to modularise and to split the general-purpose parts into their own packages.

The layers, from most general to most specific:

  • django-easy-icons and django-flex-menus, small packages usable on their own

  • Django MVP, the application shell built on them

  • FairDM, research data portals built on Django MVP

  • the World Heat Flow Database Project portal, built on FairDM

I use Django MVP for projects outside research data as well.

Stack

Python, Django, django-cotton components, Tailwind CSS and daisyUI, with shared GitHub Actions workflows across the family.

Outcome

  • About 18 repositories in the Django MVP organisation, with django-mvp itself at version 0.35 on PyPI

  • The foundation of FairDM and the heatflow.world portal