What should the successor to book module be named?

The perfect word hasn't come up yet, it's on the tip of my tongue, but so far I vote for structure...

Johan Forngren mentioned 'organize' as a possibility. I dig that.

How about the "Presentation" module --

Creating an organized list of nodes in a structured format is a way of presenting content.

The downside to this name is that it runs the risk of being misconstrued as something that sets up a presentation like a slideshow -- but, this misconception would be quickly laid to rest once the module was put to use.

On the dev list, some concern was expressed about "outliner" having no good translations in other languages -- I don't think "Presentation" would have this issue.

Cheers,

Bill

I was favoring "Outline" but after more consideration, I think "Structure" might be best (at least in English). An "Outline" module might thought to be as much related to writing as "Book".

Obviously, the final say goes to Dries/Steven/Gabor.

ehm... this is my opinion:

Presentation, sounds a bit like slideshow.
Hierachy, confusing because of Taxonomy hierarchy.
Structure, another word that scares people like Taxonomy. Why not rename Taxonomy?
Outliner, then lets take Outline. Why make the word longer than necessary?
Book, simple word. Easy to translate. Suggestive. Does not sound like wizardry...

We should think about naming this consistent with the Tab that's used to manage it. Right now it's outline, but it's possible that this is too confusing to the users. What about TOC or Table_of_contents. Site admins should have a clue as to which module to enable for a piece of the corresponding piece of functionality. Especially if it's not going to be "on by default".

Dave

Perhaps this is a bad one, but what about 'node tree'? It at least elicits the right visual image of what it does. Nodes arranged starting at a trunk and branching out to leaves.

Polling is fine
but let's keep Dries' very well informed opinion in mind when choosing a name:

4. I'd prefer to get rid of some of the book terminology. People new to Drupal want to structure pages, not create books. If this is too much work, we can leave that for another patch. _{(http://drupal.org/node/146425#comment-251305)}

I want to make it less book-like. Making it less book-like is key if we want this to be _the_ outliner feature. We have to stop using the wrong terminology, and as such, the notion of there being multiple books need to go._{(http://drupal.org/node/146425#comment-252697)}

I asked the following three questions in my office
Note that I did not mention Drupal.

Here are the questions followed by the point form gist of their answers

1) "What does outlining a website mean to you?"
- site map
- table of contents
- overview page

2) "What does structuring a website mean to you?"
- Deciding what links to what?
- Deciding what content goes in what area of the page

3) "What does organizing a website mean to you?"
- cleaning up unnecessary content
- making sure content is well related

According to my (very) simple usability survey:
"outlining" is conceptually too close to a "site map"
"organizing" is understood in terms of semantics
"structure" is the closest fit that I could find, (although is still a little confusing)

If the goal is to make this module more "usable" by making this terminology easy to understand for those new to Drupal, we NEED to ask those NEW to Drupal. We wouldn't commit a performance enhancement without benchmarking. Why would we commit a module rename without asking ordinary people to see what sense it makes to them?

For those of you working in an office environment,
Ask around to see what people answer to the above three questions
Simple usability testing only really requires 5 users to get an idea

my $2.

I'd suggest calling it after what it does - generating trees. That's short and simple.

Daniel F. Kudwien
unleashed mind

I would be happy with Outline(r), but I must say that I really like Tree. It's more suggestive than other words.

schnizZzla
BerlinerStrassen

I asked people around me and the consensus here (we're programmers, graphic designers and branding consultants) is that the name "Outliner" is synonymous with OmniOutliner. Here is what one of our principals said:

Unless the outlining feature is identical to OmniOutliner then the Outline module will have a steeper learning curve because users will start with the definition set by OmniOutliner. Changing the book module's "Outline" action name to anything else will increase Drupal's learning curve. If you start out with a concept that people already know and modify it, it's easier than coming up with something entirely new and foreign.

It's easy to get too abstract and think of "trees" and such when designing a UI. Unless a user immediately understands the abstract terminology, I strongly believe it isn't going to work. Our vote is for "Hierarchy."

It's a book module, keep it simple :)) books are fun to read, outlines suck

How about something more like, "Structured Document," "Organized Document", but not those exactly.

P.S.> I think there should be "other" as a vote option, for those not diggin' the current choices.