Answers.Body: <p>This is something i've used, it should work for you, the only downside to it is there being a hardcoded <code>id</code>.</p>
  
  <pre><code>{% set nav = craft.entries.section('yourStructureSection') %}
  
  {% set headerItems = nav.descendantOf(TopMenuId) %}
  
  {% set footerItems = nav.descendantOf(BottomMenuId) %}
  </code></pre>
  
  <p>So you would just replace <code>TopMenuId</code> with the entry <code>id</code> of <code>Topmenu</code> and <code>BottomMenuId</code> with the entry id of <code>Bottommenu</code></p>
  
  <p>Then you will be able to loop through each nav :)</p>
  
  <p><strong>Edit</strong></p>
  
  <pre><code>&lt;nav&gt;
   {% nav entry in craft.entries.section('contentPages').descendantOf(13) %} 
      &lt;li&gt; &lt;a href="{{ entry.url }}"&gt;{{ entry.title }} &lt;/a&gt;
          {% ifchildren %}
              &lt;ul&gt; {% children %} &lt;/ul&gt; 
          {% endifchildren %}
      &lt;/li&gt; 
   {% endnav %}
  &lt;/nav&gt;
  </code></pre>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-07-21T13:15:33.403Z
Answers.Text: Thanks Alec, good suggestion. I tried this, but didn't work completely. What am i doing wrong? `{% set nav = craft.entries.section('contentPages') %}
     {% set headerItems = nav.descendantOf('topmenu') %}
     <nav>
         <ul>
            {% nav page in headerItems %}
                <li>
                    <a href="{{ page.singleEntrySelector.first().url | default }}">{{ page.title }}</a>
                </li>
               </ul>
              </nav>`
Answers.UserDisplayName: Tom Suter
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-07-21T13:16:37.967Z
Answers.Text: It looks like where you have `topmenu`, this needs to be the numerical `ID` of the entry
Answers.UserDisplayName: Alec Ritson
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-07-21T13:35:34.830Z
Answers.Text: I've updated my answer, it now has code based on your comment above, just a bit of refactoring. I can't see anything wrong with this snippet though? Are you missing an `{% endblock %}` or some other closing tag?
Answers.UserDisplayName: Alec Ritson
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-07-21T13:45:12.743Z
Answers.Text: Awesome, no worries :)
Answers.UserDisplayName: Alec Ritson
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-07-21T13:01:40.640Z
Answers.LastActivityDate: 2015-07-21T13:44:10.433Z
Answers.LastEditDate: 2015-07-21T13:44:10.433Z
Answers.UserDisplayName: Alec Ritson
Body: <p>I want to use one structure section for multiple menu's (navigations). So I want all pages under topmenu in the topmenu (header) and I want all pages in the bottommenu in a menu in the footer. How can I accomplish this most easily in my twig file?
  <img src="https://i.sstatic.net/rSTI2.png" alt="example of my structure lay-out"></p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-07-21T12:50:11.903Z
Comments.Text: Not really a direct answer to your question, but for specialized menus I prefer using this plugin: https://github.com/am-impact/amnav
Comments.UserDisplayName: peirix
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-07-22T06:13:39.233Z
Comments.Text: Hi Peirix, I know that plugin, but wanted to solve it native with Craft. I didn't want my users to do things on two places (first add content and then add it to a menu-item). Thanks for suggesting though! :-)
Comments.UserDisplayName: Tom Suter
Tags: <templating><structure><navigation>
Title: One structure section for multiple menu's (navigations)
ThreadText: # One structure section for multiple menu's (navigations)
  
  (Asked by: username_0 on 2015-07-21)
  
  I want to use one structure section for multiple menu's (navigations). So I want all pages under topmenu in the topmenu (header) and I want all pages in the bottommenu in a menu in the footer. How can I accomplish this most easily in my twig file?
  ![example of my structure lay-out](https://i.sstatic.net/rSTI2.png)
  
  **Tags:** templating, structure, navigation
  
  > **Comments:**
  > **username_1**: Not really a direct answer to your question, but for specialized menus I prefer using this plugin: https://github.com/am-impact/amnav  
  > **username_0**: Hi username_1, I know that plugin, but wanted to solve it native with Craft. I didn't want my users to do things on two places (first add content and then add it to a menu-item). Thanks for suggesting though! :-)  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2015-07-21. Score: 1 | Accepted answer
  
  This is something i've used, it should work for you, the only downside to it is there being a hardcoded `id`.
  
  ```
  {% set nav = craft.entries.section('yourStructureSection') %}
  
  {% set headerItems = nav.descendantOf(TopMenuId) %}
  
  {% set footerItems = nav.descendantOf(BottomMenuId) %}
  
  ```
  
  So you would just replace `TopMenuId` with the entry `id` of `Topmenu` and `BottomMenuId` with the entry id of `Bottommenu`
  
  Then you will be able to loop through each nav :)
  
  **Edit**
  
  ```
  <nav>
   {% nav entry in craft.entries.section('contentPages').descendantOf(13) %} 
      <li> <a href="{{ entry.url }}">{{ entry.title }} </a>
          {% ifchildren %}
              <ul> {% children %} </ul> 
          {% endifchildren %}
      </li> 
   {% endnav %}
  </nav>
  
  ```
  
  > **Comments:**
  > **username_0**: Thanks username_2, good suggestion. I tried this, but didn't work completely. What am i doing wrong? `{% set nav = craft.entries.section('contentPages') %}    {% set headerItems = nav.descendantOf('topmenu') %}    <nav>        <ul>           {% nav page in headerItems %}               <li>                   <a href="{{ page.singleEntrySelector.first().url | default }}">{{ page.title }}</a>               </li>              </ul>             </nav>`  
  > **username_2**: It looks like where you have `topmenu`, this needs to be the numerical `ID` of the entry  
  > **username_2**: I've updated my answer, it now has code based on your comment above, just a bit of refactoring. I can't see anything wrong with this snippet though? Are you missing an `{% endblock %}` or some other closing tag?  
  > **username_2**: Awesome, no worries :)  
  
  ---
  
  