administration

Something I have had issues with on multiple sites I have worked on is administrative areas and permissions.

Example:
If I build a site for a client and then decide I want the client to be able to edit certain areas of the admin panel ("/admin/settings/site-information") but I don't want them to have full access to the administration area then there really isn't a good solution.

So, I ask... What exactly can be done about the issue? What would be some of the best work arounds?

Overview: Provide an Installation Profile (or a similar system) for helping people so that they can easily build a Project Management tool with typical groupware features as a Drupal website.
Key Points: Modular Architecture, High Usability, High Flexibility.

Finally after several weeks of preparation the Drupal Security Module Packages are available.

About the Security Package:

There is a discussion at http://groups.drupal.org/node/19171 regarding revamping the administrative menu. It seems to me that the issue of the improving the menu INTERFACE is different than the issue of STRUCTURE. Here, I'd like to see if we can gather the discussion of practical alternative menu interfaces for core. As I mentioned in the aforementioned thread, please let me know if I'm duplicating efforts here.

I've been working over in the theme candidate for core7 area for a while focusing on a 960 based core theme and subtheme starter kit. In addition to this I've ported over an admin theme from d5 we've used internally for a while now to d6/960 grid. I would love to get feedback from the UX team on what is good/bad about it, and where it might be improved. Ultimately I'd like to see if we can get this into core as an administrative theme. Let me know what you all think, and how I can improve this.

Eclipse

http://www.drupalworx.com/files/ninesixty.tar.gz

DRAIP: Drupal Remote Administration Interface Protocol

"Pay no attention to that man behind the curtain, err drape, err draip!"
--- with appologies to L. Frank Baum :)

Why are the "Administration Theme" settings are located in "Administer -> Site Configuration" area, rather than with all of the other theme settings in "Administer -> Site Building -> Themes".

The only unique configuration option that is in the "Administration Theme" menu is the "Use admin. theme for content editing" checkbox -- and this could simply be moved to the bottom of the list of themes in the "Administer -> Site Building -> Themes" menu. It seems unnecessary for this single option to have it's own section in the administration menu.

Create a new installation/site administration mechanism for Drupal. I should be able to configure any number of sites for my Drupal installation, right from the installer, through a simple GUI, without ever needing to manually copy files. The installer should be able to create the appropriate folders and files in the sites directory for me. I also should be able to return to the installer at any time to add additional sites to my installation, or to reconfigure existing sites.

I just came across this post: http://drupal.org/node/53836

I agree with the basic points. From an administrative post (and only trying to maintain a small site) I've already wished that I could go to /admin/node and for a group of nodes make all the same common changes (e.g. author, taxonomy, etc).

From what I know about Drupal, it would be simpler to imagine trying to code this if actions could only be applied to nodes of one type.