Now that we have a Drupal 7 version of Menu Editor out, someone mentioned a new module called "Content Menu", with a purpose quite similar to Menu Editor. It has been suggested that we join forces.
http://drupal.org/project/content_menu

As a start, we should make a comparison and summary of the features that make you favor one over the other.
We can update the the issue summary accordingly.
(unfortunately, we cannot have one issue shared between two projects)

Unique features of Content Menu:
- Search form
- Fewer text fields visible at once - this can be a good thing.
- Content type visible from
- Node creation from menu editing form
- Choose a node, instead of path autocomplete.

Unique features of Menu Editor:
- Add up to 8 items at once.
- Direct inline editing of title and path.
- Multi-delete via delete checkbox
- Node creation from placeholder page
- Path autocomplete

Implications for menu editor

Atm I do not think that merging the two modules would be technically a good idea. The two modules solve similar problems, but in slightly different ways. A merge would probably sacrifice more than it helps.

However, we can study which problems each of the two modules solve, and how they compare in usability.
I would expect that menu editor has a higher productivity, while content menu might have a better usability.

The result might lead to a few design changes and improvements in menu editor, or maybe also in content menu (this is out of my powers to decide)

Comments

dsdeiz’s picture

Hi,

Was able to play around with content_menu a bit.

- Direct inline editing of title and path.

content_menu also allows inline editing of title. Hovering on a menu item provides a link "edit title" to edit the title.

- Fewer text fields visible at once - this can be a good thing.

Agree. Loading of the "Poweredit" is a little slow when there are too many menu items.

- Node creation from placeholder page

- Node creation from menu editing form

These two somewhat provide similar function as far as I can tell. But with a different approach.

I think menu_editor + me_node_creation provides almost the same features as content_menu but content_menu somehow has better UI.

- Add up to 8 items at once.

Just a thought, maybe it's better to provide a button that says "Add new menu item" (or something else) that would add another row on the table? Maybe better rather than limiting the new items to 8?

donquixote’s picture

Just a thought, maybe it's better to provide a button that says "Add new menu item" (or something else) that would add another row on the table? Maybe better rather than limiting the new items to 8?

Have you ever tried multicrud? If you have an old D6 site around to play with, you could try it..
Otherwise, new items could be added with a button, as you suggest. This needs some ajax to let the form validate when we submit..

dsdeiz’s picture

I made a comment there at #1295216: Is there an equivalent in Drupal 7?.

Otherwise, new items could be added with a button, as you suggest. This needs some ajax to let the form validate when we submit.

Will probably try this instead. :D Just wondering, should this still be part of 7.x-1.x? Or 7.x-2.x now? I'm also planning to make some clean ups w/o affecting its current features, and try my hands on #1682960: Create a reusable form element for menu item path.

donquixote’s picture

Hi,
thanks for picking this up!
I am a fan of new branches. Let's keep 7.x-1.x as the straight-up and reliable D7 port, and put new features or technical changes into 7.x-2.x.

danielnolde’s picture

The common goal of both menu editor and content_menu is to make menu editing less cumbersome for the user. From there on, both modules differ in what they specifically aim to achieve. Speaking for content_menu i can say: 1) The focus for content_menu is not the menu management page itself, but the editorial workflow for integration of editing menu structure and associated content. 2) We were looking to improve and evolve existing menu authoring experience
I think for the moment and for D7, both module can best coexist.

For D8, we both have to redo much of the module anyway, and this we could perhaps achieve best when joining forces. The first step would be to assess the "feature final" state of D8's menu management interface (including new developments like in-place editing for menu) and what we then can improve, how we have to reconsider and adapt our modules and how we can fit in our modules into D8.

Next step then would be to come up with a good set of objectives and a corresponding concept and to discuss it with an authoring experience or user experience fellow (like Wunderkraut Belgium's Roy Scholten).

What do you think?

Let's discuss this in the re-fitted issue http://drupal.org/node/1676726