<p>You can create change the <code>uri</code> pattern for your structured section to something like <code>{ parent.uri }/{ slug }</code> and create an additional entry type <code>landing-page</code>. Your landing page will have the slug <code>liver</code> and all entries below that will have the URI <code>liver/{slug}</code> </p>

<p>You can load different templates based on the entry type and if the type is your landing page, you'll display all children</p>

<p>Another Approach is to use a <code>template</code> path directly and insert the template <code>liver.twig</code> in your templates folder</p>

CC BY-SA 4.0
2018-07-02T17:20:21.677Z
Interesting idea...thank you! My hesitation is that the 'liver/' subsite encompasses a number of structures...but only one of them houses the liver homepage. So I have primary and secondary navigations...and a utility nav that includes the homepage. I will think about this and try it before marking it correct...as well as see if there are alternative suggestions.
userAW
CC BY-SA 4.0
2018-07-02T23:40:12.447Z
now I marked it as correct. It worked...thank you!
userAW
CC BY-SA 4.0
2018-07-02T17:13:01.820Z
2018-07-02T17:13:01.820Z
Robin Schambach
<p>In Craft2, I have structures that each have a landing page/homepage for that structure. </p>

<p>If the structure's URI format is "liver/{slug}", how do I make the 'landing page' entry have a URI of only "liver/", with no slug? </p>

<p>This is important since I want users visiting the liver/about-us page to be able to remove 'about-us'...and land on the liver homepage (not get a 404).</p>

<p>I don't understand routing very well-- from what I have gleaned I cannot see how to make routing associate a given URI with a given entry-- I only understand how to associate it with a template. </p>

<p>This is similar to <a href="https://craftcms.stackexchange.com/questions/18190/can-i-use-a-structure-without-slugs">this question</a>, except that I want these landing pages to have dashboard entries and use the same template as all the other pages...not be an index-type page. </p>

<p>Note: I have seen answers regarding adding a site homepage to a structure, but this is not a site homepage- these landing pages do not live at the site domain root...they live at the root of each structure's URI. </p>

<p>Thanks in advance for the help. </p>

<url><structure>
How can I set a landing page for a structure with no slug?
# How can I set a landing page for a structure with no slug?

(Asked by: username_0 on 2018-07-02)

In Craft2, I have structures that each have a landing page/homepage for that structure.

If the structure's URI format is "liver/{slug}", how do I make the 'landing page' entry have a URI of only "liver/", with no slug?

This is important since I want users visiting the liver/about-us page to be able to remove 'about-us'...and land on the liver homepage (not get a 404).

I don't understand routing very well-- from what I have gleaned I cannot see how to make routing associate a given URI with a given entry-- I only understand how to associate it with a template.

This is similar to [this question](https://craftcms.stackexchange.com/questions/18190/can-i-use-a-structure-without-slugs), except that I want these landing pages to have dashboard entries and use the same template as all the other pages...not be an index-type page.

Note: I have seen answers regarding adding a site homepage to a structure, but this is not a site homepage- these landing pages do not live at the site domain root...they live at the root of each structure's URI.

Thanks in advance for the help.

**Tags:** url, structure


---

## 1 answers

### Answer by username_1 on 2018-07-02. Score: 2 | Accepted answer

You can create change the `uri` pattern for your structured section to something like `{ parent.uri }/{ slug }` and create an additional entry type `landing-page`. Your landing page will have the slug `liver` and all entries below that will have the URI `liver/{slug}`

You can load different templates based on the entry type and if the type is your landing page, you'll display all children

Another Approach is to use a `template` path directly and insert the template `liver.twig` in your templates folder

> **Comments:**
> **username_0**: Interesting idea...thank you! My hesitation is that the 'liver/' subsite encompasses a number of structures...but only one of them houses the liver homepage. So I have primary and secondary navigations...and a utility nav that includes the homepage. I will think about this and try it before marking it correct...as well as see if there are alternative suggestions.  
> **username_0**: now I marked it as correct. It worked...thank you!  

---

