Why this module? What sets it apart?

Agreed.. I took a quick look at the code and nothing much stood out as unique functionality. As the writeup says to put a custom template for a given node type you just install node-<type>.tpl.php in your theme. Maybe it has to do with the per-node template? Dunno.

Thank you for your comments. I'm not sure what the feature request is here, but I will take a look when I can to see if I can improve the description when time permits. If you find there is something that does the same thing and serves the same purpose, then please feel free to comment further. I am not aware of such after searching. ConTemplate, other modules, and theme work each have their purpose and advantage. This module fills in a gap that may be useful in other cases. Yes, the primary advantage is overriding node display on a per node basis as I described. For a single instance "one-off", some code in the template.php file and a node template would accomplish the same thing. If one had several nodes to be displayed in the same way, this module is probably more useful (adding one node template) rather than adding several node templates that are the same (node-34, node-27, node-37, etc.).

I think what Nancy is suggesting is for documentation to help users who wind up confused about when to use which module or a comparision chart that will help users figure out which module they should choose over the others.

Other modules that seem to fit into the same categroy and aspire to do some of the same things include

http://drupal.org/project/themekey & http://drupal.org/project/node_template

Yes, definitely, it's a good point, and I really do appreciate the comments. If it's confusing for people who are very savvy and have been around Drupal a long time, then it's bound to be even more confusing for newer users.

A few things are included in the Help module, but I should draw those out. I didn't get a handbook page done - I need to schedule time for that.

I actually had a bit of a challenge with just trying to name this module because 1) names already used and 2) the often ambiguous nature of the English language. Template is a good example of this. Node Template is something completely different and pertains to
"templates" more in the sense of how it might be used with programs like Microsoft Word. So, maybe "template" in the sense of "pattern" - does that make sense? And themekey is something different too, just like Contemplate and a few others.

The purpose and value of this module is not with content types. Really, if one wanted to theme the node display on a per content type basis, working directly in the theme is the best way, I think - at least, that's what I do. Or in some cases using another module may be better depending on need and preference.

But these are all great points. I'm interested in having this be available where it fits someone's needs - and not to make it confusing / for someone to use it when another solution would be better. Perhaps creating a demo would be helpful as well.

In regards to comparison tables, is that something that someone usually just takes it upon themselves to create or is there a specific process for it?

There is no process for the creation of a comparison chart. Someone just decides to do it and it appears. This isn't a requirement and if your module doesn't compare to the others obviously there is no need.

The static tends to come from the active community members who do their best to try and guide module developers in a way that tries to minimize module duplication and getting developers to meld ideas/modules when and where they can be. Sounds like you've done your fair share of homework in this case and there is no duplication here but for those who only read the project page to determine what a module does or doesn't do is likely where the confusion is coming into play.

Documentation provided in drupal is great when the module is actually installed. It's an issue though if one is trying to figure out where a module will fit into the scheme prior to installing it where the fog will be thicker.

A demo or videocast linked to your project page in lieu of a full description or documentation page should provide the differentiation needed to clear the fog. When you've found the time to do so of course.

Hi,

Yes, definitely, I understand. It wouldn't be very useful to contribute something that does the same thing as another module. There are some great modules related to working with content types, although I personally tend to just do further theme development when working with content types specifically.

I started a handbook page and adjusted the description of the project a little to try to make it more clear on the purpose and use of this module.

Hi Reikiman,

No, not for node-type. If it does say that somewhere, please let me know. And yes, the main point is "per node", exactly. Even having contributed the module, I wouldn't use it to simply customize the display of a content type - I would just do theme development. Like the other posts I made in general on the thread, I'll continue to work on making this more clear as needed.

Here's my quick feedback because NancyDru posted #640460: Comparison page at ThemeKey's issue queue:

"Custom Node Template" and "Node Template" assign templates to nodes. "ThemeKey" could do the same and "ThemeKey UI" offers an additional user interface for that.
But "ThemeKey" isn't limited to assigning themes to nodes but offers a more sophisticated rule engine to switch between themes:
- paths
- path aliases
- cookies
- browser detection
- dates
- taxonomy
- roles
- ...

Especially in combination with "ThemeKey Properties" you could achieve features like:
- one theme per "channel"
- front page theme
- test homepage redesign in production environment
- automated theme switching for Christmas and New Year
- themes for search result pages
- special themes for mobile devices or different browsers
- content specific theme switching
- ...

"Content Templates (Contemplate)" seems to be something different as it isn't switching the theme but templates for parts of the page.

If you start the comparison page feel free to ask me for more details.

Hi NancyDru,

Thanks for the additional info. And thanks for your additional comment. It's no problem, I do understand the point of your post - and it's good to get constructive feedback such as this to help ensure clarity for others.

Hi Mkalkbrenner.

Thanks for posting this information. I personally won't have time to do work on a comparison page this month, but depending on how things go in the next couple of weeks I may try to tackle it. The info you posted is very helpful - I appreciate it.

I'm not sure about creating a comparison page right now (a matter of finding time mostly), but I've included some clarification in the module description and online help per suggestions here. I've also started a handbook page and updated the project page.

Thanks again for the suggestions everyone.

I know this issue is closed, but thanks anyway for this module. I understand a little about custom node templates per content type, but I do not know much about coding.
I was trying to get error messages to show up at the bottom of a particular node type (because the page is very long and the error needed to be lower down) and node templates were not working for me. I could see how to modify the main page template file, but not for a specific content type or page.
With this module, now I can copy and rename page templates and tweak them a little for different node types or nodes. That is great!