We all don't know where exactly Phoenix is flying, but this fact beside: Is the new "Content Menu" module something interesting for Phoenix?

http://wunderkraut.com/en/blog/content-menu-module-%E2%80%93-menu-author...
http://drupal.org/project/content_menu

As many other Drupal shops, we at wunderkraut are also currently working on improving authoring experience in Drupal, in our case for editors of editorially driven sites. One aspect of that is menu authoring, which in Drupal is rather cumbersome for many editors. We just released the Content Menu module that improves menu management in Drupal for editorial sites.

Content menu module rewires Drupals default menu management interface for tighter integration of content authoring and menu management. The goal is to make building a site's structure and content in one fluid process seamless, easy and natural. Editors can create content along with a menu item without ever really leaving the menu management process. Editors can find, associate and edit content right from the menu management interface. Content Menu module makes building a structure-oriented website "page by page" with Drupal effortless and intuitive. To get an impression of how easy content centric menu management is with the content menu module, watch our screencast:

http://youtu.be/sYoYtoQ1s8c

So: What do all of you think: Is this a possible direction to take for improving menu authoring experience in Drupal, and does it fit into Phoenix?

Comments

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Project: » Spark

Moving to Spark; closing down Phoenix. See http://buytaert.net/announcing-spark-authoring-improvements-for-drupal-7...

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

Interesting stuff, thanks! That definitely helps to address a class of problems we've uncovered in usability tests on core. e.g. "What's a path?" Might be worth pinging the Drupal core queue about this. I think Content Menu might do a few too many things to be considered for core inclusion directly, but the general concept of letting people wireframe out their site hierarchy first, worry about the actual content of those pages after is spot-on. We lost that capability in D6 with the new menu system. :(

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Version: » 7.x-1.x-dev
Component: User interface » Code
Issue summary: View changes
Status: Active » Closed (works as designed)

We didn't end up doing this in core, so unfortunately Spark won't either. We could always backport it though if this functionality makes it into a later D8 point release.