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. 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. 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. On 4/7/06, Christopher Lenz <[EMAIL PROTECTED]> wrote: > > Hi all, > > (this one is mostly for Wilson, I guess) > > I see there's been some refactoring of the CSS for the admin app > going on, so this might be a good time for a related change: > > Many of the style rules used in the admin CSS have very generic > selectors (there are styles for p, ul, etc). In my current project, > we're embedding the admin screens in our own layout, reusing the > styles for the rest of the site. The generic rules in the admin CSS > make that a lot more cumbersome than it'd need to be. I'd really like > to see the selectors changed to be more specific (for example, use > ".admin-form p" instead of just "p"). > > Also, the the markup use some class and ID names that are fairly > common, such as #content. These are pretty much guaranteed to clash > with names used for the site layout. Could those be changed/prefixed > (for example, "#admin-content" instead of "#content"). > > Those changes would make it a lot simpler to embed the admin app in > an existing layout. > > 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 [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
