Day2 (#1386)

* Import @samuelayo's fork (don't have write access)

* Add pic, split up days

* Update 2019-03-28-30daystoliftoff-day3.md

website/src/_posts/2019-03-26-30daystoliftoff-day1.md

@@ -1,6 +1,7 @@
 ---
 title: "Day 1"
 author: [kvz, aj]
+date: 2019-03-26
 image: "https://uppy.io/images/blog/30daystoliftoff/inspace.jpg"
 series: 30 Days to Liftoff
 seriesSuffix: 'of 30'

website/src/_posts/2019-03-27-30daystoliftoff-day2.md

@@ -1,11 +1,34 @@
 ---
 title: "Day 2"
 date: 2019-03-27
-author: kvz
-image: "https://uppy.io/images/blog/0.30/robodog-assemble.jpg"
-published: false
+author: samuel
+image: "https://uppy.io/images/blog/30daystoliftoff/inspace2.jpg"
 series: 30 Days to Liftoff
 seriesSuffix: 'of 30'
 ---
 
-Howdy partners!
+Yesterday, marked the beginning of our thirty-day blog post challenge to keep you updated on **releasing Uppy 1.0 on April 25**. So here we are again already! 
+ 
+<!--more-->
+
+Our big coding speedrun towards for 1.0 starts April 1, so are are mostly busy with tying up lose ends, busting issues, and planning our work ahead.
+
+<center><img width="400" src="/images/blog/30daystoliftoff/inspace2.jpg"><br /></center>
+
+## Our roadmap for 1.0
+
+With so much still to do before Uppy 1.0 is ready go, it's important that we keep track of all the various tasks. We are doing this with help of an Uppy 1.0 project dashboard that we created in [Asana](https://asana.com). This lets us see in an instant what everyone is working on and what the current status is on specific tasks. 
+
+We currently have our tasks divided into five sections, which are: *Nice To Have*, *To Do*, *In Progress* and *Done*. The tasks in the *To Do* and *In Progress* lanes (and of course those that are *Done*) are planned to make the 1.0 release. And if we have time on our side before the launch date, we'll also try to get as many of the *Nice To Have* tasks checked off as well.
+
+We've discussed our [Changelog](https://github.com/transloadit/uppy/blob/master/CHANGELOG.md#10-goals)'s 1.0 goals and tried to re-prioritize and assign work. 
+
+We didn't manage to fit all of those *To Do*s in the picture, but here is a screenshot of what our board looks like at the moment:
+
+<center><img src="/images/blog/30daystoliftoff/2019-03-27-board02.png"></center>
+
+Aside from planning, we've also been busy onboarding [Evgenia](https://github.com/lakesare) so she can hit the ground running April 1st.
+
+And tomorrow, we'll look at the *To Do*s in more detail, so we can get a clearer idea of subtasks and who will do what, exactly.
+
+That's all the updates I have for you today. See you tomorrow for day 3 of our 30 Days to Liftoff!

website/src/_posts/2019-03-28-30daystoliftoff-day3.md

@@ -0,0 +1,41 @@
+---
+title: "Day 3"
+date: 2019-03-28
+author: samuel
+published: false
+image: "https://uppy.io/images/blog/30daystoliftoff/inspace2.jpg"
+series: 30 Days to Liftoff
+seriesSuffix: 'of 30'
+---
+
+Two days ago we started our thirty-day blog post challenge to keep you updated on **releasing Uppy 1.0 on April 25**. Here's day three for you!
+ 
+<!--more-->
+
+Our big coding speedrun towards for 1.0 starts April 1, so are are mostly busy with tying up lose ends, busting issues, and planning out our work.
+
+## What have we checked off our *To Do* list?
+
+Today marks the third day of our launch preparations, and we have quite a lot going on. 
+
+[Artur](https://github.com/arturi) started out by merging two pull requests from [Renée](https://github.com/goto-bus-stop). The [first](https://github.com/transloadit/uppy/pull/1375) one aims to use Transloadit Templates and demo keys for the `transloadit-textarea` example, and the [second](https://github.com/transloadit/uppy/pull/1374) one makes error reporting across different languages more flexible.
+
+[Ife](https://github.com/ifedapoolarewaju) then reviewed and merged this [pull request](https://github.com/transloadit/uppy/pull/1366), which updates the callback URIs to reflect their correct location in Companion. Thanks to [HughbertD](https://github.com/HughbertD) for that one!
+
+## What is the team working on today?
+
+Renée is working hard to fix outdated `ffmpeg_stack` warnings in our examples. Other than that, the team has been working on a Companion issue that invalid access tokens are given out when you select a provider to receive your file from. The aim is to return 401 for invalid access tokens, so that the `/authorized` endpoint can be deprecated. You can track the progress of this issue in its [pull request](https://github.com/transloadit/uppy/pull/1298).
+
+The biggest update that will be part of Uppy 1.0 is support for React Native. Today, Renée, Artur, Ife, [Evgenia](https://github.com/lakesare) and [Kevin](https://github.com/kvz) had a call about it and talked extensively about what we need for an MVP. The were kind enough to share their notes that i'll happy extend to you as-is :)
+
+- get a link provider example to work, including showing companion progress, and resumability
+- it gets its own UI, (re)written for RN
+- make websocket progress from Companion work (see: https://facebook.github.io/react-native/docs/network#websocket-support)
+- resumability support within 20min (easily tested by disabling wifi on your workstation while uploading to master.tus.io)
+- the example gets buttons for resumability & a progress bar
+- the example gets file previews (likely uppy RN itself does not offer previews)
+
+We also celebrated Evgenia also submitting her first two PRs: [one](https://github.com/transloadit/uppy/pull/1382) to make sure that tooltips can no longer overflow inside the Uppy container, and [another](https://github.com/transloadit/uppy/pull/1383) that removes the jumpiness when Uppy loads.
+
+That's all the updates I have for you today. See you tomorrow for day 4 of our 30 Days to Liftoff!
+