News for hackers. Stuff that matters.
Re:Django's Architecture: The Good, The Bad, and The Ugly by airtonix on Sunday June 16, 2013 @09:22AM (#5888335)
bootstrap is horrible and your suggestion doesn't address the problem.
Re:Django's Architecture: The Good, The Bad, and The Ugly by joelhaasnoot on Sunday June 16, 2013 @11:55AM (#5888808)
The only problems I've had with the admin is that it's very model based, while my user actions don't neccesarily reflect specific models.

If you want bootstrap BTW, this is a dropin addon https://github.com/riccardo-forina/django-admin-bootstrapped

Re:Django's Architecture: The Good, The Bad, and The Ugly by manojlds on Sunday June 16, 2013 @12:00PM (#5888835)
Bootstrap is ideal for internal admin interfaces
Re:Django's Architecture: The Good, The Bad, and The Ugly by LoganCale on Sunday June 16, 2013 @12:05PM (#5888851)
This is what I use it for, almost exclusively, and it works great for that purpose.
Re:Django's Architecture: The Good, The Bad, and The Ugly by mixmastamyk on Sunday June 16, 2013 @02:52PM (#5889433)
We don't have to solve every problem simultaneously.
Re:Django's Architecture: The Good, The Bad, and The Ugly by berntb on Sunday June 16, 2013 @11:01AM (#5888644)
Could you elaborate about what is horrible with Bootstrap?

It seems to me that it does what it set out to do. Well.