I am in the process of creating a site for a Tour Operator. Aside from the usual pages the bulk of the site consists of the following parent-child-grand child page structure, all with the ‘destinations’ page at the root. This example uses Africa as the child of the destinations page but the pattern is replicated many times over:
The issue I’m trying to resolve is how best to build the site given that each country page needs to return links to pages using the ‘Accommodation’, Itinerary’ and ‘Highlights’ templates, i.e. the 3 grandchild types. I also need to return links to the parent pages.
This I could normally do with separate query posts on the page templates but I am wondering if I should be using Custom Post Types for Accommodation, Itinerary and Highlights pages? At present I am struggling to implement these pages and assign them to their correct place in the sitemap e.g. Creating an ‘Accommodation’ CPT leaves all accommodation pages as children of http://www.sitename.com/accommodation whereas I need multiple instances of ‘accommodation’ as a child of the respective ‘country’ page. This also obviously applies to the other parent page names.
Any thoughts on how best to implement this would be great.
That’s exactly what I’m doing at the moment – custom templates with custom fields (using Advanced Custom Fields plugin). I just wanted to know if using CPTs would be more efficient
The other issue – which I should probably have explained in the original post – is that I need to be able to query not only pages that children of the pages outlined above, but also have a search function where users can specify multiple Itinerary requirements with results returned in an archive style list. So I figured that creating taxonomies for these page types such as “5 star” “Honeymoon” “Safari” etc would be the most logical way to do this and that creating parent-child relationships of the CPTs would be the way to go?