diff --git a/source/_talks/deploying-php-with-fabric.md b/source/_talks/deploying-php-with-fabric.md index e121d9db..f95c27a4 100644 --- a/source/_talks/deploying-php-with-fabric.md +++ b/source/_talks/deploying-php-with-fabric.md @@ -6,7 +6,7 @@ slides: ~ slides_embed: ~ tags: [meetup, php, fabric] events: - - { id: nomad_php, date: '2017-04-20', time: '19:00 CEST' } + - { id: nomad_php, date: '2017-04-20', time: '19:00 (CET)' } --- You’ve built your application, and now you just need to deploy it. There are various ways that this could be done – from (S)FTP, to SCP and rsync, to running commands like “git pull” and “composer install” directly on the server (not recommended). diff --git a/source/_talks/getting-your-data-into-drupal-8.md b/source/_talks/getting-your-data-into-drupal-8.md index bca01c3a..72fb2363 100644 --- a/source/_talks/getting-your-data-into-drupal-8.md +++ b/source/_talks/getting-your-data-into-drupal-8.md @@ -7,7 +7,7 @@ slides: tags: [drupalcamp, migration, drupal-8] events: - { id: drupal-bristol, date: '2017-01-18' } - - { id: drupalcamp-london-17, date: '2017-03-04' } + - { id: drupalcamp-london-17, date: '2017-03-04', time: '12:05 - 12:50' } --- 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. diff --git a/source/_talks/test-driven-drupal-simpletest-phpunit.md b/source/_talks/test-driven-drupal-simpletest-phpunit.md index 498fa2d3..afb198e9 100644 --- a/source/_talks/test-driven-drupal-simpletest-phpunit.md +++ b/source/_talks/test-driven-drupal-simpletest-phpunit.md @@ -6,7 +6,7 @@ slides: embed: tags: [drupalcamp, simpletest, phpunit, testing] events: - - { id: drupalcamp-london-17, date: '2017-03-04' } + - { id: drupalcamp-london-17, date: '2017-03-04', time: '16:15 - 17:00' } --- 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.