From 4753202b4a1f6aef97476609f2f527f290d3d9dc Mon Sep 17 00:00:00 2001
From: Oliver Davies <oliver@oliverdavies.uk>
Date: Fri, 13 Sep 2019 13:56:43 +0100
Subject: [PATCH] Live blogging from SymfonyLive London 2019

---
 source/_posts/2019-09-13-live-blogging-symfonylive-london.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/source/_posts/2019-09-13-live-blogging-symfonylive-london.md b/source/_posts/2019-09-13-live-blogging-symfonylive-london.md
index b8f159510..f438b5d83 100644
--- a/source/_posts/2019-09-13-live-blogging-symfonylive-london.md
+++ b/source/_posts/2019-09-13-live-blogging-symfonylive-london.md
@@ -333,6 +333,7 @@ A way on the front-end JS, CSS, images at the beginning of the request, sends a
 - Blurred responsibilities == tightly coupled teams
 - harder to debug, bugs fall between systems and teams. Huge gap between front-end and back-end, passing responsibilites.
 - You can fix these problems in SPAs, but is it worth it?
+    + Examples of good SPAs - Trello, Flickr
 
 ## Using Twig as an alternative to an SPA?