Practical advice on HR operations, payroll compliance, CRM pipeline management, and getting the most out of Horilla.
This series has covered extending detail, list, and card views through the same declare-don’t-subclass pattern: define an *Extension class, point...
The previous post in this series showed how _inherit_detail lets an extension app inject fields and context into an existing...
Every CRM eventually runs into the same wall: the built-in Lead or Contact detail page is almost right, but not...
Sooner or later, every Horilla implementation needs to add something to a list view that already exists a custom column...
Detail pages are great when a record deserves a full page, but a lot of the time, a user just...
Every Django project has an apps.py in each app: most of the time, it’s three lines nobody thinks about. In...
Long forms hurt conversion. When a user has to fill in fifteen fields on one screen – contact info, company...
Forms are part of almost every create and edit screen in Horilla. In a typical Django project, this can mean...
When a CRM form contains only a few fields, putting everything on one page is perfectly fine. But some records...