Am 07.04.2006 um 17:03 schrieb Wilson Miner: > I'm open to being convinced otherwise, but I don't see it as within > the scope of the admin CSS to accomodate being embedded in other > interfaces. > > We've discussed this internally before and the general consensus was > that if you're reusing the admin templates and code in your public > site (which is great), you should be encouraged to restyle it for your > site rather than using the default CSS.
I realize I might not have made clear enough what I'm trying to do here... I'm working on a site where the customer is going to be managing the content. The management interface is basically the Django admin app, with a couple of custom fields and a custom base.html template. While the admin is not something that the general public will see, we still consider it important that the management interface reflects the design of the site in general. I.e. just using the Django admin with a branding logo in the upper left corner doesn't quite cut it. On the other hand, the styles for the tables, forms and widgets are great and usable as-is, and I'd really like to reuse instead of duplicate them. > The templates themselves are designed (or should be designed) to be as > semantic and design-agnostic as possible, so you're not tied to using > the admin design in your public sites. I want to use the admin design, just not the generic stuff (fonts, colors, etc). Restyling all the admin forms and widgets would be a *lot* of work. The other option would be using a different markup structure and style sheet for the admin than for the rest of the site. But I'm wary of the duplication here, too... two different ways to achieve the same resulting layout. > Again, I'm open to compelling arguments otherwise, but I don't want to > overload the admin CSS with too much specificity and redundancy to > encourage modular reuse. I think it's a good goal that the templates > should be as reusable as possible, but I'm not convinced that the > styles should be. Okay, I understand the concern about being overly specific in the markup and the style sheets. So here's a suggestion: what about splitting out the generic layout styles from the styles for the change-lists, change-forms, widgets etc? Then I could simply drop the reference to the layout style sheet from the base.html template, but still keep the other stuff. Or is that already possible with your recent changes? Thanks, Chris -- Christopher Lenz cmlenz at gmx.de http://www.cmlenz.net/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
