Answers.Body: <p>I'd just put whatever you want to share into an include. Also you shouldn't need the <code>.html</code> either as craft should find the file</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-13T13:52:08.400Z
Answers.Text: The solution was putting it all in a "set" variable and worked out fine now but it actually needs the `.html` because it is searching for just `.html` files in the blocks folder which is good because i have other types of files there some of them with the same name. Thanks for the answer though :D
Answers.UserDisplayName: Justin Dekkers
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-13T15:14:08.760Z
Answers.Text: Right on! Glad you were able to get it sorted out!
Answers.UserDisplayName: Mark Busnelli Jr
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-06T17:00:27.500Z
Answers.LastActivityDate: 2015-08-06T17:00:27.500Z
Answers.UserDisplayName: Mark Busnelli Jr
Body: <p>My orignal website is a Onepager but I am creating a individual news page.</p>
  
  <p>Is it possible to extend a block to another page taking over the content from that single? I have a block filled with a really big Matrix field which I cant have on my other page cause I only need a small amount of content from it. This content is placed inside a block so I need to extend just that block.</p>
  
  <p><strong>What I need is to extend the {% block navigation %} and not the entire page</strong></p>
  
  <p>See it as this:</p>
  
  <pre><code>{% block navigation %}
    {% for block in entry.blokken %}
      {% if block['opnemenInNavigatie'] is defined and block.opnemenInNavigatie %}
         &lt;li&gt;
          {% if block.navigatieNaam | slugify == 'news' %}
           &lt;a href="/{{ block.navigatieNaam | slugify }}"&gt;          
            {{ block.navigatieNaam }} 
          &lt;/a&gt;
         {% endif %}
        &lt;/li&gt;
      {% endif %}
    {% endfor %}
  {% endblock %}
  </code></pre>
  
  <p>And also this:</p>
  
  <pre><code>{% block content %}
      {% for block in entry.blokken %}
          {% include 'blocks/' ~ block.type ~ '.html' %}
      {% endfor %}
  {% endblock %}
  </code></pre>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-08-06T10:13:32.390Z
Comments.Text: I'm not 100% following your question, but take a look at the Twig extend tag, I think that might be what you need http://twig.sensiolabs.org/doc/tags/extends.html
Comments.UserDisplayName: Jamie Wade
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-08-06T10:20:45.897Z
Comments.Text: Let me say it different because a posibillity might be setting a block in a variable that would do the deal too
Comments.UserDisplayName: Justin Dekkers
Tags: <templating><matrix><block-types>
Title: Extending a block from another page
ThreadText: # Extending a block from another page
  
  (Asked by: username_0 on 2015-08-06)
  
  My orignal website is a Onepager but I am creating a individual news page.
  
  Is it possible to extend a block to another page taking over the content from that single? I have a block filled with a really big Matrix field which I cant have on my other page cause I only need a small amount of content from it. This content is placed inside a block so I need to extend just that block.
  
  **What I need is to extend the {% block navigation %} and not the entire page**
  
  See it as this:
  
  ```
  {% block navigation %}
    {% for block in entry.blokken %}
      {% if block['opnemenInNavigatie'] is defined and block.opnemenInNavigatie %}
         <li>
          {% if block.navigatieNaam | slugify == 'news' %}
           <a href="/{{ block.navigatieNaam | slugify }}">          
            {{ block.navigatieNaam }} 
          </a>
         {% endif %}
        </li>
      {% endif %}
    {% endfor %}
  {% endblock %}
  
  ```
  
  And also this:
  
  ```
  {% block content %}
      {% for block in entry.blokken %}
          {% include 'blocks/' ~ block.type ~ '.html' %}
      {% endfor %}
  {% endblock %}
  
  ```
  
  **Tags:** templating, matrix, block-types
  
  > **Comments:**
  > **username_1**: I'm not 100% following your question, but take a look at the Twig extend tag, I think that might be what you need http://twig.sensiolabs.org/doc/tags/extends.html  
  > **username_0**: Let me say it different because a posibillity might be setting a block in a variable that would do the deal too  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2015-08-06. Score: 3 | Accepted answer
  
  I'd just put whatever you want to share into an include. Also you shouldn't need the `.html` either as craft should find the file
  
  > **Comments:**
  > **username_0**: The solution was putting it all in a "set" variable and worked out fine now but it actually needs the `.html` because it is searching for just `.html` files in the blocks folder which is good because i have other types of files there some of them with the same name. Thanks for the answer though :D  
  > **username_2**: Right on! Glad you were able to get it sorted out!  
  
  ---
  
  