Posted by ksenzee on March 13, 2009 at 12:46am
I personally hate trying to theme the admin section. It's a totally different project from theming the front end. I bet there are designers out there who would contribute great themes to Drupal if they didn't have to theme the whole back end. So what if we made theming /admin optional? Just specify "admin = false" in your .info file, and the system defaults to Garland as an admin theme. What say you, designers? Is theming /admin a barrier, or am I the only one that hates it?
Comments
It is a pain, but I'm pretty
It is a pain, but I'm pretty sure if you go to "Site configuration › Administration theme" you can change the admin theme to Garland without having to write any code or touch the .info file.
Yes, you can set an
Yes, you can set an administrative theme without any code.
In your Drupal site, go to /admin/settings/admin
For some themes, I just set
For some themes, I just set body.section-admin: 90%; Which means that admin pages just stretch up to 90% of the viewport width, which fixes any problems with admin tables not fitting. This required that your theme is coded so that it can stretch horizontally without collapsing.
For other themes that almost fit the admin tables, I just make sure the admin tables can "hang over" the right sidebar. This just means you give the inner column a higher z-index than the sidebars (and give it position:relative so that it listens to the z-index). And if you want to make the "overhanging" work in ie6 too you also need to add somthing like this:
#content, .sidebar {
overflow:hidden; /* prevent collapsing of structure when childs elements are too wide - relies on below style on .inner for desired effect /
overflow-y:visible;
}
#content .inner, .sidebar .inner {
position:relative; / ie6 has a bug that allows relatively positioned elements to overflow while overflow:hidden is true. This combination facilitates "overhanging" without breaking the layout, identical to the behaviour of standards compliant browsers */
}
Where #content represents the inner column.
peach from All Drupal Themes!
Running SooperThemes Premium Drupal Themes
Please move this post to its appropriate group
Hate to sound like an "admin from hell" but....
The D4D group is not the place to discuss concrete theming issues and or finding help with ones theme work, the place for that would be http://groups.drupal.org/theme-development.
We need to keep the discussion here in focus
/morten.dk king of rock
morten.dk | geek Royale
/morten.dk king of rock
morten.dk | geek Royale
Let me try this again
I think I'm expressing myself badly. I'm aware that end users can choose their own admin theme. What I'm talking about is a concrete way to remove the expectation -- and it is an expectation -- that Drupal themes will address the admin section. I mentioned this in #drupal and immediately got told that if you aren't theming the admin section, you're a "lazy themer." I don't think that attitude helps attract designers to Drupal. That's why I'm making this suggestion. Wordpress themes don't have to address the admin backend. Joomla themes don't have to address the admin backend. I think it should at least be optional for Drupal themes as well.
This is true...
I never had a clue when contributing how much I would actually be expected to support. I had such high hopes of contributing more themes by now, but just trying to address the issues that come up on a weekly basis, and sometimes daily, of this module and that module, including admin stuff + the real job work has made it tough.
It would be nice not to worry about it, for contrib at least.
Yes!
I agree wholeheartedly with ksenzee. While it's nice and I understand the pressure for something like a core theme to support it, it does seem like an unnecessary burden given the insane range of interfaces in the backend of Drupal.
~~~
{ Drupal Themes from TopNotchThemes }
~~~
{ TopNotchThemes | Fusion Drupal Themes }