Use tables again for talks

source/_talks/tdd-test-driven-drupal.md

@@ -1,11 +1,11 @@
 ---
 title: TDD - Test Driven Drupal
-slides:
+speakerdeck:
+    id: 088cb18033064f5cb18d1079795294a1
+    ratio: '1.77777777777778'
     url: 'https://speakerdeck.com/opdavies/tdd-test-driven-drupal'
-    embed: '<script async class="speakerdeck-embed" data-id="088cb18033064f5cb18d1079795294a1" data-ratio="1.77777777777778" src="//speakerdeck.com/assets/embed.js"></script>'
-video:
-    url: https://www.youtube.com/watch?v=fdbxXOi2HP4
-    embed: <iframe width="560" height="315" src="https://www.youtube.com/embed/fdbxXOi2HP4" frameborder="0" allowfullscreen></iframe>
+youtube:
+    id: fdbxXOi2HP4
 tags: [drupalcamp, simpletest, phpunit, testing]
 meta:
     og:
@@ -19,9 +19,14 @@ meta:
             type: image/png
 use: [talks]
 events:
-    - { event: drupalcamp-london-17, date: '2017-03-04', time: '16:15 - 17:00' }
-    - { event: drupalcamp-dublin-17, date: '2017-10-21', time: '12:00 - 12:40' }
-    - { event: drupal-bristol, date: '2017-11-22' }
+    - event: drupalcamp-london-17
+      date: '2017-03-04'
+      time: '16:15 - 17:00'
+    - event: drupalcamp-dublin-17
+      date: '2017-10-21'
+      time: '12:00 - 12:40'
+    - event: drupal-bristol
+      date: '2017-11-22'
 ---
 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.