<p>If you are using a Structure to manage your site hierarchy, and the news index page naturally falls in that hierarchy, then yes, this can work well. Make an <code>entry type</code> for the index page, and in your template (which is the same for all the entry types),</p>

<pre><code>{% include ['_page/'~entry.type, '_page/_default'] %}
</code></pre>

<p>(So if you haven't defined a template for this <code>entry type</code> you will use the <code>_page/_default.html</code> template instead of getting an error).</p>

<p>I think it is a good idea to use an entry for the index page (rather than just an index template) because there is very likely to be some content on that page other than just the list of news items, and you will want the CMS to manage that content for you.</p>

CC BY-SA 3.0
2014-12-21T06:32:50.060Z
2014-12-21T06:32:50.060Z
Marion Newlevant
<p>If I have a section called "news" with section type "channel" with entries having their own URLs, what is best practice for creating an index for when people site.com/news?</p>

<p>Do I just create an index file in 'template/news' or should I create a route?</p>

<p>EDIT: Did some more digging! Looks like some users have recommended using Structure to create parent level pages. Is this an ideal method?</p>

<routes><best-practice><channels>
What's best practice for creating an index page for Channels?
# What's best practice for creating an index page for Channels?

(Asked by: username_0 on 2014-12-21)

If I have a section called "news" with section type "channel" with entries having their own URLs, what is best practice for creating an index for when people site.com/news?

Do I just create an index file in 'template/news' or should I create a route?

EDIT: Did some more digging! Looks like some users have recommended using Structure to create parent level pages. Is this an ideal method?

**Tags:** routes, best-practice, channels


---

## 1 answers

### Answer by username_1 on 2014-12-21. Score: 3 | Accepted answer

If you are using a Structure to manage your site hierarchy, and the news index page naturally falls in that hierarchy, then yes, this can work well. Make an entry type for the index page, and in your template (which is the same for all the entry types),
{% include ['_page/'~entry.type, '_page/_default'] %}

(So if you haven't defined a template for this entry type you will use the _page/_default.html template instead of getting an error).
I think it is a good idea to use an entry for the index page (rather than just an index template) because there is very likely to be some content on that page other than just the list of news items, and you will want the CMS to manage that content for you.


---

