Hi,

I am starting a new Drupal-project. A site for a minor travel company. I have experience with Drupal, not I am not an expert at all!

The site is very simple, user needs to be able to add Country, Destinations (City/Area) and Hotels.

I am going to add a content type for Destinations and Hotels. I think country will be based on taxonomy, since it will hold no information other than the country name.

First question, does this structure seems like the best way to build it?
How can you link a hotel to a destination? So if I want to make a list of hotels from a certain destination?

I also need a menu, like Nice Menu. With a menu point listing all countries and from each country you can select a destinations.
I have never worked with nice menu, how do you populate the menu based on both taxonomy content and custom type content?

Have a lot more questions, but this will do for now.... Hope somebody can give me some good advice so i can get started the right way..

Comments

First question: yes, that

First question: yes, that sounds like a good setup. You can link a hotel to a destination using CCK's node reference field. That will give you a list of links to the hotel nodes on the destination page. You may want to use views to build these kind of lists, ie. if you want to show more hotel information than just the title.

Personally, I would not use a menu for selecting the country and destination. Finding a hotel is the core application of your site, so selecting country and destination should imho not be hidden in a nice menu, but much more in the center of everything. Creating a view with exposed filters is a good way to build such an hotel finder.

Hope that helps.

Change to structure, and NICE MENU needed

Thanks for your comment, very much appreciated.

Client has changed their mind, they want countries listed by continent. And still in a overlay menu!

If I have a vocabulary with continents and one with countries, is there any way you can link a taxonomy term to
another taxonomy term. So when the user adds a hotel, the only select the right country and based on country
you know which continent.

AND as mentioned earlier they want to access countries from a menu, so now I need a menu point, listing continents
with countries as children. Which links to a view listing hotels from the selected country.

Kind regards

I think you should make a

I think you should make a hierarchical taxonomy for the countries, so you would get

- Asia
- - Thailand
- - India
- - China
- - etc.
- Europe
- - UK
- - Germany
- - France
- - etc.

To create the menu, this looks good: http://drupal.org/project/taxonomy_menu. (It wasn't hard to find, just search http://drupalmodules.com for 'taxonomy menu'.)

Yeah! Now subpages....

Yeah of cause - as I said - new to Drupal - and forgot all about hierarchy. That part is all set up now.
Thanks alot....

Now I need to make the Hotel content type - next challenge is the a hotel needs subpages!!
and a submenu! So when you first enter a hotelnode-page you have a brief description of the
hotel and then I need a hotel menu with different subpages containing different info about the hotel.

How can you create this, without making it too difficult to maintain for the user. One idea is to create
a content type called Hotel-subpage, with a Title (menu link) text-field for the description of what ever
need to be described and image upload.
The only thing bugging me with this approach is that it seems like alot of steps to add a hotel.
And it will always be the same 5-6 subpages. (Rooms, Restaurant, Perfect for etc.)

So what if I put all the info in the hotelnode. Creating a Rooms descriptions field, Restaurant
descriptions field and so on... Then you can edit all info on the hotel page. But how can you
then make the hotel subpage menu, and change the displayed content according to what menu
point you have clicked. While only having one node, displaying it over several pages...

Hope this makes any sense...

If a hotel sub-page is not

If a hotel sub-page is not going to be re-used in any other context, then it doesn't make sense to store it as a separate node. I would indeed put everything in one node an maybe use tabs to divide the content of the hotel node into smaller sub pages. You may want to look at http://drupal.org/project/cck_fieldgroup_tabs or http://drupal.org/project/quicktabs.

Great...

I will go with only on hotel node, but content needs to be access via menu and not tabs...

Any idea ?

In that case, you could use

In that case, you could use the Panels module to override the node view (www.example.com/node/123). With an extra argument in the url you could define which content needs to be shown (www.example.com/node/123/rooms, www.example.com/node/123/restaurant).

The next step would be to create a custom module, implementing hook_nodeapi, that automatically adds links to the sub-pages (probably as children of the node's main menu item). Have a look at the code in http://drupal.org/project/automenu to see how you can add a menu item programatically inside a hook_nodeapi implementation.