<p>Assuming that those pages are working off of different <strong>entry types</strong>, you should check out this great help article...</p>

<blockquote>
  <p><a href="http://buildwithcraft.com/help/entry-type-templates" rel="nofollow">How can I give each Entry Type its own template?</a></p>
</blockquote>

<p>Basically, you let a parent template decide which child template to load, based on the current entry type.</p>

CC BY-SA 3.0
2014-10-16T23:04:23.843Z
2014-10-16T23:04:23.843Z
Lindsey D
<p>Entry types is probably the way to go but you could also check advanced routing - <a href="http://buildwithcraft.com/docs/routing#advanced-routing" rel="nofollow">http://buildwithcraft.com/docs/routing#advanced-routing</a></p>

CC BY-SA 3.0
2014-10-16T23:08:56.353Z
2014-10-16T23:08:56.353Z
erwinheiser
<p>I have a site that's mostly 'static' content pages, with a few dynamic &amp; more complicated pages mixed in.  To make editing &amp; setting up the navigation easy, I started by creating a Structure that holds all the entries in my Pages section.  Let's say that structure looks something like this -</p>

<ul>
<li>About
<ul>
<li>People</li>
<li>History</li>
</ul></li>
<li>Products
<ul>
<li>Product A</li>
<li>Product B</li>
</ul></li>
</ul>

<p>It's more complicated, but just a longer version of that.  This structure is used to generate my navigation for the site, and everything is working as expected.</p>

<p>Now, all my content pages are in place and I need to add the 1-offs.  The first is a contact page, which is going to live @ /about/contact.  I'd like to place it within the structure because otherwise my navigation becomes a lot more complicated.</p>

<p>The problem is, it draws from a different template than my normal content pages, and a structure can only pull from a single template regardless of what sections are listed in it.  Ok, I thought, I could put the entry into that structure and then use a route to direct that page to the template I want to use.  That doesn't work, however, because page URI's are processed before routes.</p>

<p>So, the question is - what am I missing about doing this?  Is there a better way to set up what I'm doing?</p>

<structure><routing>
Working with Structure & Multiple Pagetypes
# Working with Structure & Multiple Pagetypes

(Asked by: username_0 on 2014-10-16)

I have a site that's mostly 'static' content pages, with a few dynamic & more complicated pages mixed in. To make editing & setting up the navigation easy, I started by creating a Structure that holds all the entries in my Pages section. Let's say that structure looks something like this -

* About
  + People
  + History
* Products
  + Product A
  + Product B

It's more complicated, but just a longer version of that. This structure is used to generate my navigation for the site, and everything is working as expected.

Now, all my content pages are in place and I need to add the 1-offs. The first is a contact page, which is going to live @ /about/contact. I'd like to place it within the structure because otherwise my navigation becomes a lot more complicated.

The problem is, it draws from a different template than my normal content pages, and a structure can only pull from a single template regardless of what sections are listed in it. Ok, I thought, I could put the entry into that structure and then use a route to direct that page to the template I want to use. That doesn't work, however, because page URI's are processed before routes.

So, the question is - what am I missing about doing this? Is there a better way to set up what I'm doing?

**Tags:** structure, routing

---

## 2 answers

### Answer by username_1 on 2014-10-16. Score: 4

Assuming that those pages are working off of different **entry types**, you should check out this great help article...

> [How can I give each Entry Type its own template?](http://buildwithcraft.com/help/entry-type-templates)

Basically, you let a parent template decide which child template to load, based on the current entry type.


---

### Answer by username_2 on 2014-10-16. Score: 1

Entry types is probably the way to go but you could also check advanced routing - <http://buildwithcraft.com/docs/routing#advanced-routing>


---

