diff --git a/images/speakers/eemeli.jpg b/images/speakers/eemeli.jpg
new file mode 100644
index 0000000..3767041
Binary files /dev/null and b/images/speakers/eemeli.jpg differ
diff --git a/src/speakers/eemeli-aro.js b/src/speakers/eemeli-aro.js
new file mode 100644
index 0000000..0150977
--- /dev/null
+++ b/src/speakers/eemeli-aro.js
@@ -0,0 +1,20 @@
+const keywords = require("../keywords");
+
+module.exports = {
+  name: "Eemeli Aro",
+  about: "Eemeli has been falling down the rabbit hole of JavaScript localization for about six years now, and keeps wondering at what the next level might be. For work he makes complicated systems seem simple, for fun he writes open-source libraries, and in his spare time he organises science fiction conventions.",
+  image: "speakers/eemeli.jpg",
+  social: {
+    homepage: "",
+    twitter: "eemeli_aro",
+    github: "eemeli",
+  },
+  location: {
+    country: {
+      name: "Finland",
+      code: "FI",
+    },
+    city: "Helsinki",
+  },
+  keywords: [keywords.TOOLING, keywords.REACT],
+};
diff --git a/src/talks/eemeli-aro.js b/src/talks/eemeli-aro.js
new file mode 100644
index 0000000..7d60d1c
--- /dev/null
+++ b/src/talks/eemeli-aro.js
@@ -0,0 +1,11 @@
+const enums = require("../enums");
+const keywords = require("../keywords");
+const speaker = require("../speakers/eemeli-aro");
+
+module.exports = {
+  speakers: [speaker],
+  title: "There's always a better way to handle localization",
+  description: "From the very first prototype to a global site with content in multiple languages, the textual content of your app or project will be a series of compromises, some of which you won't even notice making. Localization is a ridiculously difficult problem in the general case, but in the specific you can get away with really simple solutions, especially if you understand the compromises you're making.",
+  type: enums.LIGHTNING_TALK,
+  keywords: speaker.keywords,
+};