<p>You've hit on most of the options — all of which should work fine.</p>

<ol>
<li><p>Assuming you have a structure called 'pages', with the 'uri' set to <code>{slug}</code>, 'parent uri' set to <code>{parent.uri}/{slug}</code>, and template set to 'pages/_entry'; create a new entry 'resources' which should route to your template at 'pages/_entry.html', or</p></li>
<li><p>If you do not have a 'pages' structure you can also just create a template at 'templates/resources.html', or 'templates/resources/index.html', or</p></li>
<li><p>Create a route <code>'resources' =&gt; 'pages/_entry'</code></p></li>
</ol>

<p>If those aren't working, then you might check that the template itself isn't creating any restrictions, and/or that you don't have any other routes defined (i.e. in your config file) that might be creating conflicts.</p>

CC BY-SA 3.0
2015-06-03T17:56:19.650Z
Thanks for the reply. I figured out what it was. The client has a section/page entry called “resources” and guess what my folder for all the site resources (css/js/etc) is called? :)
Niall Thompson
CC BY-SA 3.0
2015-06-04T14:50:52.300Z
That would do it! Didn't even think about that. Good catch.
Douglas McDonald
CC BY-SA 3.0
2015-06-01T22:02:12.177Z
2015-06-01T22:02:12.177Z
Douglas McDonald
<p>I have a category group called "Resource Categories" and categories within it have their own urls.</p>

<p>Category Url Formats:</p>

<p>top-level categories: resources/{slug}
nested categories: {parent.uri}/{slug}</p>

<p>Category Template:
resources/_category</p>

<p><img src="https://i.sstatic.net/sbF8y.png" alt="Category Setup"></p>

<p>There's also a category template which is here:
resources/_entry</p>

<p>What I want to do is add a Landing page at /resources.</p>

<p>This would be a standard entry page ideally created within my Pages channel using the pages/_entry template.</p>

<p>Failing that I could also create an index page inside the resources folder.</p>

<p>But I keep getting 403 forbidden when visiting site.com/resources.</p>

<p>I've tried creating a route but that doesn't help the issue.</p>

<pre><code>'resources' =&gt; 'pages/_entry'
</code></pre>

CC BY-SA 3.0
2015-05-29T21:55:13.150Z
This might be healpful


http://craftcms.stackexchange.com/questions/1467/add-home-page-to-a-structure
Jam
<entries><categories><routes>
Landing Page with Same URL Structure as Category
# Landing Page with Same URL Structure as Category

(Asked by: username_0 on 2015-05-29)

I have a category group called "Resource Categories" and categories within it have their own urls.
Category Url Formats:
top-level categories: resources/{slug}
nested categories: {parent.uri}/{slug}
Category Template:
resources/_category

There's also a category template which is here:
resources/_entry
What I want to do is add a Landing page at /resources.
This would be a standard entry page ideally created within my Pages channel using the pages/_entry template.
Failing that I could also create an index page inside the resources folder.
But I keep getting 403 forbidden when visiting site.com/resources.
I've tried creating a route but that doesn't help the issue.
'resources' => 'pages/_entry'

**Tags:** entries, categories, routes

> **Comments:**
> **username_1**: This might be healpful   http://craftcms.stackexchange.com/questions/1467/add-home-page-to-a-structure  

---

## 1 answers

### Answer by username_2 on 2015-06-01. Score: 1

You've hit on most of the options — all of which should work fine.

1. Assuming you have a structure called 'pages', with the 'uri' set to `{slug}`, 'parent uri' set to `{parent.uri}/{slug}`, and template set to 'pages/\_entry'; create a new entry 'resources' which should route to your template at 'pages/\_entry.html', or
2. If you do not have a 'pages' structure you can also just create a template at 'templates/resources.html', or 'templates/resources/index.html', or
3. Create a route `'resources' => 'pages/_entry'`

If those aren't working, then you might check that the template itself isn't creating any restrictions, and/or that you don't have any other routes defined (i.e. in your config file) that might be creating conflicts.

> **Comments:**
> **username_0**: Thanks for the reply. I figured out what it was. The client has a section/page entry called “resources” and guess what my folder for all the site resources (css/js/etc) is called? :)  
> **username_2**: That would do it! Didn't even think about that. Good catch.  

---

