Start adding event data, rebuild talks page

source/_talks/2017-02-08-it-all-started-with-a-patch-phpsw.md

@@ -6,5 +6,7 @@ slides: https://speakerdeck.com/opdavies/it-all-started-with-a-patch-phpsw
 slides_embed: <script async class="speakerdeck-embed" data-id="5862bdecb7a24cfaa5fc844696fafa0c" data-ratio="1.37081659973226" src="//speakerdeck.com/assets/embed.js"></script>
 logo: assets/images/talks/logos/phpsw.png
 logo_link: http://phpsw.uk/talks/it-started-with-a-patch
+events:
+    - { title: PHPSW, date: 2017-02-08 }
 ---
 A crash course of why and how to get involved with open source.

source/_talks/2017-03-04-getting-your-data-into-drupal-8-drupalcamp-london-2017.md

@@ -6,6 +6,9 @@ logo_link: http://drupalcamp.london/session/getting-your-data-drupal-8
 slides: https://speakerdeck.com/opdavies/getting-your-data-into-drupal-8-drupal-bristol
 slides_embed: <script async class="speakerdeck-embed" data-id="63e5dfce996e46699e304d50e896477b" data-ratio="1.37081659973226" src="//speakerdeck.com/assets/embed.js"></script>
 tags: [drupalcamp, migration, drupal-8]
+events:
+    - { title: DrupalCamp London 2017, date: 2017-03-05 }
+    - { title: Drupal Bristol, date: 2017-01-18 }
 ---
 If you’ve moved a site from Drupal 6 to 7, the chances are that you’ve either used the upgrade path to update your old site in-place, or you built a new site from scratch and used the Migrate module from contrib to migrate your data from the old database.
 

source/_talks/2017-03-04-test-driven-drupal-simpletest-phpunit-drupalcamp-london-2017.md

@@ -6,6 +6,8 @@ logo_link: http://drupalcamp.london/session/test-driven-drupal-development-simpl
 slides: https://speakerdeck.com/opdavies/test-driven-drupal-development-with-simpletest-and-phpunit-drupalcamp-london-2017
 slides_embed: <script async class="speakerdeck-embed" data-id="4f12722ed400468b93ebb32a23b3c757" data-ratio="1.37081659973226" src="//speakerdeck.com/assets/embed.js"></script>
 tags: [drupalcamp, simpletest, phpunit, testing]
+events:
+    - { title: DrupalCamp London 2017, date: 2017-03-05 }
 ---
 Testing is important. Why? It allows developers to add new features and edit and refactor existing code without the worry of adding regressions, reduces the reliance on manual testing to discover bugs, and by taking a test driven approach, your implementation code is leaner as you only write what is needed for your tests to pass.
 

source/talks.html.twig

@@ -7,37 +7,18 @@ use: [talks, posts]
 ---
 <h1>Talks</h1>
 
-<p>I regularly speak at conferences and user groups about a range of subjects including Drupal, Sculpin and Git. If you would like to me to speak at your group or conference, please <a href="/contact/">get in touch</a>.</p>
+{% set events = [] %}
 
-<p>There is also information about events that I’ve attended and spoken at on my <a href="{{ site.lanyrd.url }}">Lanyrd</a> and <a href="{{ site.joindin.url }}">Joind.in</a> profiles.</p>
+{% for talk in data.talks %}
+    {% for event in talk.events %}
+        {% set event = event|merge({ talk: talk }) %}
+        {% set events = events|merge([event]) %}
+    {% endfor %}
+{% endfor %}
 
-{% set now = 'now'|date('U') %}
-
-{% include "talks-table" with { talks: data.talks } %}
-
-<!-- <table class="table table-striped">
-    <thead>
-        <tr>
-            <th>Date</th>
-            <th>Talk</th>
-            <th>Event</th>
-        </tr>
-    </thead>
-    <tbody>
-        {% for talk in data.talks if talk.date < now %}
-            <tr>
-                <td>
-                    {{ talk.date|date(site.default_date_format) }}
-                </td>
-
-                <td>
-                    <a href="{{ talk.url }}">
-                        {{ talk.title }}
-                    </a>
-                </td>
-
-                <td>{{ talk.event.name }}</td>
-            </tr>
-        {% endfor %}
-    </tbody>
-</table> -->
+{% for event in events|sortbyfield('date')|reverse %}
+    {{ event.title }}<br>
+    {{ event.date }}<br>
+    {{ event.talk.title }}<br>
+    {{ event.talk.url }}<br><br>
+{% endfor %}