Answers.Body: <p>This isn't documented, so it's subject to change:</p>
  
  <p>When you set a Single to be the homepage, its slug is automatically set to <code>__home__</code>.</p>
  
  <p>If you want your homepage to be part of a Structure, rather than a separate Single, you can set the slug of a Structure entry to <code>__home__</code>, which makes it act as the site's homepage and gives it that little Home icon in place of its slug in the structure view.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-28T14:26:23.170Z
Answers.Text: Yep just remember to untick the box on the default single that says "This is for the homepage"
Answers.UserDisplayName: John Macpherson
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-11T05:26:30.757Z
Answers.Text: Coming across this and checking, the slug for the homepage appears to be `homepage` currently.
Answers.UserDisplayName: Marty
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-11T13:20:57.863Z
Answers.Text: Technically, the actual _slug_ can be whatever you want. The _URI_ must be `__home__`. But, unless you want to open up the db and edit those values separately, you would probably be editing both together via the _slug_ input.
Answers.UserDisplayName: Michael Rog
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-02T05:46:28.580Z
Answers.Text: This tip is absolutely brilliant. I just stumbled across it, and it works like a charm!
Answers.UserDisplayName: Lindsey D
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-10T21:23:33.803Z
Answers.Text: But now every child page have `__home__` in the url
Answers.UserDisplayName: jlcharette
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-04-12T08:01:05.640Z
Answers.Text: @JCharette In my setup, the homepage is a sibling of the other first-level pages on the site, so it doesn't need to have any children. I recommend this approach.
Answers.UserDisplayName: Michael Rog
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-01-05T16:03:11.007Z
Answers.LastActivityDate: 2015-01-05T16:03:11.007Z
Answers.UserDisplayName: Michael Rog
Answers.Body: <p>From an IA and content-modelling perspective, putting all your site's "pages" in a Structure is fraught with problems, and, in my opinion, does a terrible disservice to the future-friendly approach with which you should be building sites. I wrote about this at length recently: <a href="https://cld.agency/blog/content-utopia" rel="nofollow noreferrer">https://cld.agency/blog/content-utopia</a></p>
  
  <p>To more directly answer the question:</p>
  
  <ol>
  <li>stop mixing all your content types together in a single Structure (see article);</li>
  <li>divorce your navigation from the content;</li>
  <li>use a dedicated Channel or Structure for home page entries (note the plural - allows for A/B tests and seasonal variations, permanent storing of draft home pages etc), then load the most recent or first-structure-ordered entry manually in your home page template.</li>
  </ol>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-11-30T20:35:57.130Z
Answers.Text: I totally agree, and when I wrote that “I am using a structure for all of my site's pages”, I meant entries where you usually use Singles for. The reason to go with a structure instead, was that there’s no way to list Singles in the CP in manual sort order. In this project we had so many Singles that it was getting hard to find the right one in the list.
Answers.UserDisplayName: carlcs
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-11-30T08:36:35.313Z
Answers.LastActivityDate: 2018-11-30T08:36:35.313Z
Answers.UserDisplayName: James Smith
Answers.Body: <p>I kludged this to work by creating a global whose value was the entry I wanted to use as the home page (<code>everyPage.homePage</code>), and then on <code>_pages/_entry.html</code> using twig to sort things out based on the entry:</p>
  
  <ul>
  <li>if no entry: 404 (this should never happen)</li>
  <li>if entry is <em>everyPage.homePage</em>: 404</li>
  <li>if entry is the Craft home page single: set entry to <em>everyPage.homePage</em></li>
  </ul>
  
  <p>Then proceed as normal.</p>
  
  <pre><code>{% if entry is not defined %}
    {% exit 404 %}
  {% elseif entry.id == everyPage.homePage.first.id %}
    {% exit 404 %}
  {% elseif entry.id == craft.entries.section('homePage').first().id %}
    {% set entry = everyPage.homePage.first %}
  {% endif %}
  </code></pre>
  
  <p>This was using a channel (not a structure) for the pages, and the URL is simply <code>{slug}</code></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-31T17:50:57.517Z
Answers.Text: Whooohoo, Marion! Kinda hacky but really great solution, if this really works. Off for the test...
Answers.UserDisplayName: carlcs
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-31T18:05:30.240Z
Answers.Text: To be true, I don't really understand it. Let's try: I'd still need a single (the only entry I could route `/` to), the global is basically not necessary, right? (just for convenience) and then you'd just "import" the content from the select channel- or structure-entry by getting it's entry model... good that's a plan!
Answers.UserDisplayName: carlcs
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-31T18:13:07.380Z
Answers.Text: Actually... why not simply get the desired entry model (with id or slug) from my `public/index.html` template!? If that's all I needed, I totally don't know why I didn't come up with that myself. That's all the more reason to thank you, Marion! :D
Answers.UserDisplayName: carlcs
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-31T17:34:31.310Z
Answers.LastActivityDate: 2014-07-31T17:34:31.310Z
Answers.UserDisplayName: Marion Newlevant
Answers.Body: <p>The "this is for the homepage" button available on single sections does two things for you, when you navigate to the home page's URL:</p>
  
  <ul>
  <li>it populates the <code>entry</code> variable with the single's entry model</li>
  <li>it loads the template spezified in the single's CP settings</li>
  </ul>
  
  <p>.</p>
  
  <p>Actually nothing you can't do manually with your home page's <code>index.html</code>:</p>
  
  <pre><code>{# Replace the default `entry` variable with the home page's entry model #}
  {% set entry = craft.entries.section('pages').id('1').first() %}
  
  {# Load the home page's template from the "pages" structure #}
  {% include "_pages/_entry" %}
  </code></pre>
  
  <p><code>_pages/_entry.html</code> further includes the template partial designed for the entry type I assigned my home page to:</p>
  
  <pre><code>{# Load the designed template for this entry's entry type #}
  {% include '_pages/' ~ entry.type %}
  </code></pre>
  
  <p>This is all you need to replicate the "this is for the homepage" button behaviour for a structure entry. Additionally you might want to exclude the home page from your navigation menu for example. Again use the <a href="http://buildwithcraft.com/docs/templating/craft.entries#id"><code>id</code></a> or <a href="http://buildwithcraft.com/docs/templating/craft.entries#slug"><code>slug</code></a> parameter on the ElementCriteriaModel:</p>
  
  <pre><code>{# Get top-level entries in pages structure (exclude home page)  #}
  {% set pages = craft.entries.section('pages').id('not 1').level(1) %}
  </code></pre>
  
  <p>.</p>
  
  <p><em>Thanks again to Marion, her answer pointed me in the right direction.
  I added this answer, because her configuration is a bit spezific and rather complicated.</em></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-02-22T19:42:01.340Z
Answers.Text: This is a great answer, but wouldn't '/homepage/{slug}' now be part of the uri for all subpages? I would think you would also need to add a custom route that re-maps uris to remove the 'homepage' segment.
Answers.UserDisplayName: Douglas McDonald
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-02-22T20:35:46.920Z
Answers.Text: Nope @Douglas, "Home" could go anywhere in my structure, as it is excluded from the nav loop. So pages like "About" and "Contact" are still first level entries in my "Pages" structure, peacfully located besides "Home" (one could say this is not consistent, but I think it's good enough having it at the top).
Answers.UserDisplayName: carlcs
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-02-22T20:43:40.257Z
Answers.Text: Got you. I was thinking you were suggesting placing everything under 'home' in the heirarchy (i.e. level 2). That makes more sense. Thanks for clarifying. ;)
Answers.UserDisplayName: Douglas McDonald
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-11T06:36:13.980Z
Answers.Text: If you don't want to use and "id" or "slug", but the first element in the structure, it's very easy too. On the index page: {% set entry = craft.entries.section('pages').first() %}. For the navigation: {% set pages = craft.entries.section('pages').offset(1).level(1) %}. Works like a charm.
Answers.UserDisplayName: outline4
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-12T10:28:55.473Z
Answers.LastActivityDate: 2014-08-12T10:28:55.473Z
Answers.UserDisplayName: carlcs
Body: <p>I am using a structure for all of my site's pages (single pages and channel index pages). The structure settings are as follows:</p>
  
  <p>URL for Top-Level Entries:<br/>
  <code>{slug}</code></p>
  
  <p>URL for Nested Entries:<br/>
  <code>{parent.uri}/{slug}</code></p>
  
  <p>Entry Template:<br/>
  <code>_pages/_entry.html</code></p>
  
  <p>Additionally I set up multiple entry types for the structure to relate the pages with individual templates (basically as <a href="http://buildwithcraft.com/help/entry-type-templates">described in the FAQs</a>). This is my <code>_entry.html</code>:</p>
  
  <pre><code>{% include '_pages/_types/' ~ entry.type %}
  </code></pre>
  
  <p>This all works great for me [*], but now I'd like to further improve the template setup by adding my site's home page to the structure, too. With a single section I can simply trigger the option "this is the home page" in the section's settings, but how can I tell an entry of my pages structure to be my home page?</p>
  
  <p><sub>[*]: I can generate my site's main navigation from this structure (nice!) and all channels' index pages have entry slugs now, which is incredibly helpful in a multi-lingual Craft setup, if you want to translate your slugs.</sub></p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-07-30T02:57:20.700Z
Comments.Text: I think this is a great question, and I'm slightly bummed that it hasn't been answered yet. If it's not possible, perhaps it's worthy of an official feature request. If a single can be set "as the home page", why not a structure page?
Comments.UserDisplayName: Lindsey D
Tags: <url><navigation><structure><slug>
Title: Add home page to a structure?
ThreadText: # Add home page to a structure?
  
  (Asked by: username_0 on 2014-07-28)
  
  I am using a structure for all of my site's pages (single pages and channel index pages). The structure settings are as follows:
  
  URL for Top-Level Entries:  
  `{slug}`
  
  URL for Nested Entries:  
  `{parent.uri}/{slug}`
  
  Entry Template:  
  `_pages/_entry.html`
  
  Additionally I set up multiple entry types for the structure to relate the pages with individual templates (basically as [described in the FAQs](http://buildwithcraft.com/help/entry-type-templates)). This is my `_entry.html`:
  
  ```
  {% include '_pages/_types/' ~ entry.type %}
  
  ```
  
  This all works great for me [\*], but now I'd like to further improve the template setup by adding my site's home page to the structure, too. With a single section I can simply trigger the option "this is the home page" in the section's settings, but how can I tell an entry of my pages structure to be my home page?
  
  [\*]: I can generate my site's main navigation from this structure (nice!) and all channels' index pages have entry slugs now, which is incredibly helpful in a multi-lingual Craft setup, if you want to translate your slugs.
  
  **Tags:** url, navigation, structure, slug
  
  > **Comments:**
  > **username_1**: I think this is a great question, and I'm slightly bummed that it hasn't been answered yet. If it's not possible, perhaps it's worthy of an official feature request. If a single can be set "as the home page", why not a structure page?  
  
  ---
  
  ## 4 answers
  
  ### Answer by username_0 on 2014-08-12. Score: 16 | Accepted answer
  
  The "this is for the homepage" button available on single sections does two things for you, when you navigate to the home page's URL:
  
  * it populates the `entry` variable with the single's entry model
  * it loads the template spezified in the single's CP settings
  
  .
  
  Actually nothing you can't do manually with your home page's `index.html`:
  
  ```
  {# Replace the default `entry` variable with the home page's entry model #}
  {% set entry = craft.entries.section('pages').id('1').first() %}
  
  {# Load the home page's template from the "pages" structure #}
  {% include "_pages/_entry" %}
  
  ```
  
  `_pages/_entry.html` further includes the template partial designed for the entry type I assigned my home page to:
  
  ```
  {# Load the designed template for this entry's entry type #}
  {% include '_pages/' ~ entry.type %}
  
  ```
  
  This is all you need to replicate the "this is for the homepage" button behaviour for a structure entry. Additionally you might want to exclude the home page from your navigation menu for example. Again use the [`id`](http://buildwithcraft.com/docs/templating/craft.entries#id) or [`slug`](http://buildwithcraft.com/docs/templating/craft.entries#slug) parameter on the ElementCriteriaModel:
  
  ```
  {# Get top-level entries in pages structure (exclude home page)  #}
  {% set pages = craft.entries.section('pages').id('not 1').level(1) %}
  
  ```
  
  .
  
  *Thanks again to username_7, her answer pointed me in the right direction.
  I added this answer, because her configuration is a bit spezific and rather complicated.*
  
  > **Comments:**
  > **username_8**: This is a great answer, but wouldn't '/homepage/{slug}' now be part of the uri for all subpages? I would think you would also need to add a custom route that re-maps uris to remove the 'homepage' segment.  
  > **username_0**: Nope @username_8, "Home" could go anywhere in my structure, as it is excluded from the nav loop. So pages like "About" and "Contact" are still first level entries in my "Pages" structure, peacfully located besides "Home" (one could say this is not consistent, but I think it's good enough having it at the top).  
  > **username_8**: Got you. I was thinking you were suggesting placing everything under 'home' in the heirarchy (i.e. level 2). That makes more sense. Thanks for clarifying. ;)  
  > **username_9**: If you don't want to use and "id" or "slug", but the first element in the structure, it's very easy too. On the index page: {% set entry = craft.entries.section('pages').first() %}. For the navigation: {% set pages = craft.entries.section('pages').offset(1).level(1) %}. Works like a charm.  
  
  ---
  
  ### Answer by username_2 on 2015-01-05. Score: 34
  
  This isn't documented, so it's subject to change:
  
  When you set a Single to be the homepage, its slug is automatically set to `__home__`.
  
  If you want your homepage to be part of a Structure, rather than a separate Single, you can set the slug of a Structure entry to `__home__`, which makes it act as the site's homepage and gives it that little Home icon in place of its slug in the structure view.
  
  > **Comments:**
  > **username_3**: Yep just remember to untick the box on the default single that says "This is for the homepage"  
  > **username_4**: Coming across this and checking, the slug for the homepage appears to be `homepage` currently.  
  > **username_2**: Technically, the actual _slug_ can be whatever you want. The _URI_ must be `__home__`. But, unless you want to open up the db and edit those values separately, you would probably be editing both together via the _slug_ input.  
  > **username_1**: This tip is absolutely brilliant. I just stumbled across it, and it works like a charm!  
  > **username_5**: But now every child page have `__home__` in the url  
  > **username_2**: @JCharette In my setup, the homepage is a sibling of the other first-level pages on the site, so it doesn't need to have any children. I recommend this approach.  
  
  ---
  
  ### Answer by username_6 on 2018-11-30. Score: 4
  
  From an IA and content-modelling perspective, putting all your site's "pages" in a Structure is fraught with problems, and, in my opinion, does a terrible disservice to the future-friendly approach with which you should be building sites. I wrote about this at length recently: <https://cld.agency/blog/content-utopia>
  
  To more directly answer the question:
  
  1. stop mixing all your content types together in a single Structure (see article);
  2. divorce your navigation from the content;
  3. use a dedicated Channel or Structure for home page entries (note the plural - allows for A/B tests and seasonal variations, permanent storing of draft home pages etc), then load the most recent or first-structure-ordered entry manually in your home page template.
  
  > **Comments:**
  > **username_0**: I totally agree, and when I wrote that “I am using a structure for all of my site's pages”, I meant entries where you usually use Singles for. The reason to go with a structure instead, was that there’s no way to list Singles in the CP in manual sort order. In this project we had so many Singles that it was getting hard to find the right one in the list.  
  
  ---
  
  ### Answer by username_7 on 2014-07-31. Score: 4
  
  I kludged this to work by creating a global whose value was the entry I wanted to use as the home page (`everyPage.homePage`), and then on `_pages/_entry.html` using twig to sort things out based on the entry:
  
  * if no entry: 404 (this should never happen)
  * if entry is *everyPage.homePage*: 404
  * if entry is the Craft home page single: set entry to *everyPage.homePage*
  
  Then proceed as normal.
  
  ```
  {% if entry is not defined %}
    {% exit 404 %}
  {% elseif entry.id == everyPage.homePage.first.id %}
    {% exit 404 %}
  {% elseif entry.id == craft.entries.section('homePage').first().id %}
    {% set entry = everyPage.homePage.first %}
  {% endif %}
  
  ```
  
  This was using a channel (not a structure) for the pages, and the URL is simply `{slug}`
  
  > **Comments:**
  > **username_0**: Whooohoo, username_7! Kinda hacky but really great solution, if this really works. Off for the test...  
  > **username_0**: To be true, I don't really understand it. Let's try: I'd still need a single (the only entry I could route `/` to), the global is basically not necessary, right? (just for convenience) and then you'd just "import" the content from the select channel- or structure-entry by getting it's entry model... good that's a plan!  
  > **username_0**: Actually... why not simply get the desired entry model (with id or slug) from my `public/index.html` template!? If that's all I needed, I totally don't know why I didn't come up with that myself. That's all the more reason to thank you, username_7! :D  
  
  ---
  
  