Commons' make file needs to include modules and tools for administrators and related backend navigation.

Let's collect the list of modules that are required.

Comments

izkreny’s picture

Title: Select the required admin menu and tools » Improve Commons DX - select the required admin menu and tools

Here is the list of modules that Commerce Kickstart distro include for the developers.

We already included (but commented in commons.info file) Devel module.

I suggest that we definitely enable core toolbar module, at least in this early development phase - because when you install site you're totally blanked! ;)
About menus - I personally prefer Toolbar module because I can use it easily without mouse (e.g. with extension such Vimium or Pentadactyl).

We can choose between Administration menu and Admin (+ Admin tools) which Spark team included/activated.

What about admin theme? Not at this point in time?

We could also steal (do we need to credit them because of GPL?) Spark README.txt file or write similar file.

Actually, I would prefer to have as less text as possible in those README files - we just need to provide links to the docs, which brings as to: #1704202: Commons 3.x documentation

OK, I think I need to stop now - I can't control myself and that produce long comments. :P

P.S.
I also changed issue title to address issue more accurately.

izkreny’s picture

Aha, I forgot to mention/suggest http://drupal.org/project/module_filter module. :)

achton’s picture

Title: Improve Commons DX - select the required admin menu and tools » Select the required admin menu and tools

Obviously, Toolbar is included. Let's just enable that to begin with.

If we find later that there are shortcomings to Toolbar, we can either let people go with their own choice of replacement, or select a contrib module for Commons instead. (I particularly like the flyout menus that come with Administration Menu and Admin.)

We could also enable other core modules: Contextual Links & Shortcut. Shortcut could perhaps be utilized to preconfigure Commons-specific menu items in the admin toolbar.

And yes, we should include Module Filter.

achton’s picture

Also, AT has an admin theme included, which I think is fine (at least initially).

izkreny’s picture

Assigned: Unassigned » izkreny

Patch is half baked, will finish it tomorrow, it's late here at Europe, time for bed...

As for now it will do:

  1. Include + activate module_filter (2.x-dev) module
  2. Activate toolbar, Contextual Links and Shortcut core modules
  3. Enable AT admin theme

I think we discussed all of above @ IRC except activation of Contextual Links and Shortcut core modules. I give them +1.

achton’s picture

Cool! .. which patch? ;)

izkreny’s picture

Huh, today I figured out that it would be great to implement theme setup as a batch cleanup(?) install task (Inspiration: Julio distro) that we will be able to easily extend for other things like disabling Bartik theme, removing modules defaul options (like Flag's bookmarks), etc.

To speed up completion of this issue I wanted to create another task for that, and just put

theme_enable(array('adaptivetheme_admin'));
variable_set('admin_theme', 'adaptivetheme_admin');

code into commons.profile file, but that is a big no-no, it threw 500 Fatal error right into my face.

Will finish it next week...

BTW, we will definitely need other types of install tasks because they provide great tool for customizing installation/distro inital configuration process so this instantiation of commons_install_taks function will only bring good to us.

crimsondryad’s picture

I'm loving module_filter, so please, add it. Not as wild about admin menu, usually just use the toolbar.

izkreny’s picture

Assigned: izkreny » Unassigned

I'm quite busy these days, so I unassigned myself.

I also planed to try most current release of Spark to see their admin interface solution - I think it would be good to adopt that ASAP.

Also closed #1758908: Empty site / Access Denied after clean install as duplicate of this one.

Regarding theme enable we just could do it in plain drupal_install() function in commons.install file.

I think I will be able to finish this by the end of this week, of course, if somebody doesn't finish it before...

erikwebb’s picture

To add my two cents, here are the modules I'd recommend in this batch -

Some of the other modules mentioned above, like Contextual links, should be enabled in the core profile IMHO.

ezra-g’s picture

Admin (+ Admin tools) which Spark team included/activated.

Good thinking to keep compatibility with Spark in mind. However, I don't see those modules in the Spark make file

Let's start with everything from #10 except Filter perms - I'm not sure that the additional UI results in a net increase in clarity for a new users.

So:

- Toolbar (core)
- Shortcut (core) - with sane defaults
- Module filter

erikwebb’s picture

Status: Active » Needs review
StatusFileSize
new1.1 KB

Here's a start on the modules, without the defaults for Shortcut.

ezra-g’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

giorgio79’s picture

http://drupal.org/project/admin_views ?
http://drupal.org/project/total_control ?

Some pretty essential admin stuff these days :)

erikwebb’s picture

Status: Closed (fixed) » Needs work

I think the key is to get the ball rolling here (and we've done at least that). It's certainly worth taking some more considerations before closing this.

I like Admin Views. Never had experience with Total Control, but looks intriguing.

ezra-g’s picture

giorgio79’s picture

  • http://drupal.org/project/admin_views has Views maintainers on board by now, so it's a safe bet.
  • Drupal core Contextual Links is essential as well :), mentioned several times by others also :)
lsolesen’s picture

Version: » 7.x-3.x-dev
Issue summary: View changes

@erikwebb What is your take on this issue. Could it be closed?