VSH Hospital — Website & Staff Portal

A single Django project with four apps serves both audiences: core owns the public site and most staff-facing logic, while doctor, hr and team each own a scoped notification feed for their role. Staff routes live under /account/... in the same URLconf, protected by login plus a Summary.role check that redirects each staff member to their own dashboard section — a custom authorization layer built at the application level rather than Django's group/permission framework.

Appointments use a ContentType generic relation so one model can point at either a recurring or a one-off timing slot without duplicating scheduling logic, and fast-moving paid-campaign pages (Specialty Clinic, Home Care) are deliberately kept outside the department CMS so they don't destabilize the core content model. I also found and fixed an N+1 query pattern on the busiest staff page, cutting per-request queries from linear to a constant handful via bulk-fetching and select_related.