Excellent idea for content wireframing, and I'd like to toss another idea in. Support the automated creation of hierarchical taxonomy tree at the same time.

Ideally this would have the option of automatically assigning the terms to a same-name node or not (Taxonomy Node and Node Automated Taxonomy modules don't), and of course allow spec'ing the relationship between content type and vocabulary.

And of course if this were possible, people would want to use it in production, not just prototyping.

Document how to use Views to show the same-name node at the top of a list/teasers etc of the other nodes tagged with the same-name term as the auto-created "parent" node.

Totally different topic (and feature request) look at how Node Hierarchy sets up its menu/breadcrumb/pathalias coordination - if you follow the same scheme that will allow for interoperability with an *excellent* and well-supported module. It doesn't do anything non-core, if you remove the module all the menus and pathaliases remain coordinated.

Basically this module would be a batch/mode enhancement to NH, but it doesn't do taxonomy either, so don't limit yourself to that :)

I know, I know, barely born and everyone wants every pie in the sky possible feature!

But IMO this type of functionality would make Drupal much more usable for hierarchical web sites.

Comments

usonian’s picture

usonian commented

Thanks for the many good suggestions HansBKK, especially the tip to look at Node Hierarchy. In terms of roadmap, what I would like to do is make v1.0 very good at doing one thing: importing a simple outline and building out a site framework. Once that's nice and stable, I can start to consider other features.

HansBKK’s picture

HansBKK commented

No worries, so ignore the taxonomy bit for now, there are a few import modules I'm checking out for that, only problem is I'd still have to make the node associations manually.

Big plus this allows is to see if you can make your tool an "import for NH". I bet Ronan would be open to cooperating, and if you could end up contributing an enhancement/sub-module there you'll get a lot more support and future dev without having to do it all yourself.

Plus your coding efforts would end up being of wider use to the community, and of course the benefits of reducing the number of contrib modules with overlapping functionality. . .

NH's Ajax outline management tool's a great example of efficient structure management, would greatly help the prototyping process when the client doesn't have a clear idea of the structure of their own navigation needs, easily modify the hierarchies after the initial creation.

usonian’s picture

usonian commented
Status: Active » Postponed
usonian’s picture

usonian commented
Version: 5.x-0.5 » 6.x-1.0-unstable1