more polish, added intro and “featured in”

website/src/_posts/2019-04-1.0.md

@@ -1,11 +1,17 @@
 ---
-title: "Uppy 1.0: Man’s best friend in file uploading"
+title: "Uppy 1.0: Your best friend in file uploading"
 date: 2019-04-25
 author: arturi
-image: "https://uppy.io/images/blog/1.0/robodog-assemble.jpg"
-published: false
+image: "https://uppy.io/images/blog/1.0/uppy-dashboard-1.png"
+published: true
 ---
 
+Today, after 3 years of development, we are now launching version 1.0 of Uppy, our file uploader for web browsers.
+
+<img src="/images/blog/1.0/uppy-dashboard-1.png">
+
+## A little history
+
 Three years ago, Transloadit was ready to replace their jQuery-based file uploading & processing plugin for browsers with something more modern. They posted a [job ad](https://transloadit.com/jobs/2015-10-front-end-developer/) in search for people to build it:
 
 > In general, we're looking for polished, well tested, carefully crafted products that are delightful to work with and use. So for this job it's not only important that you know JavaScript, but also how to make things look stunning and work well for end users.
@@ -16,9 +22,7 @@ Shortly after, I saw a retweet of this vacancy come across my time line and I de
 
 Initially, the idea was to build a proprietary uploader that would work exclusively with Transloadit’s commercial service, but we quickly turned around on it. We felt our version of a file uploader could have a real impact if we made it more widely available. So, just like Transloadit had done before with [Tus](https://tus.io/), we decided to make Uppy an open-source solution — free for anyone to use and hack on. Transloadit support became an optional plugin.
 
-Three years, [16.000 stargazers](https://github.com/transloadit/uppy/stargazers) and a thriving community later — and we could not be happier to finally launch Uppy 1.0!
-
-<img src="/images/blog/1.0/uppy-dashboard-1.png">
+Three years, [16.000 stargazers](https://github.com/transloadit/uppy/stargazers), getting featured on [Smashing Magazine](https://www.smashingmagazine.com/the-smashing-newsletter/smashing-newsletter-issue-197/), [JavaScript Daily](https://twitter.com/JavaScriptDaily/status/950348390268919809), [Product Hunt](https://www.producthunt.com/posts/uppy-io), [SurviveJS](https://survivejs.com/blog/uppy-interview/), and a thriving community later — and we could not be happier to finally launch Uppy 1.0!
 
 <!--more-->
 
@@ -60,16 +64,18 @@ Read more [about Golden Retriever and that team meetup](https://uppy.io/blog/201
 
 We had been postponing the 1.0 release for quite some time. There’s always just one more feature you'd like to add or another bug you want to fix, before calling something ready for a 1.0 release. Truth be told, Uppy has been [used in production](https://github.com/transloadit/uppy#used-by) for a while already, and even though we iterate and change things frequently, the API had mostly stabilized.
 
-So, about a month ago, we decided to pull the trigger and [announced an Uppy Month](https://uppy.io/blog/2019/03/liftoff-01/) within Transloadit. This meant that all team members, including those not working primarily on Uppy — the Tus core team, our SDK teams, as well as our infra and API engineers, designers, content writers, and the founders themselves — all chipped in and did their part to ensure liftoff in thirty days. We also asked [Evgenia](http://github.com/lakesare) to join us for the month to lend a hand with frontend work. Every week, we had a call where we looked at the [Asana](https://asana.com/) Uppy 1.0 project board and talked about our progress.
+So, about a month ago, we decided to pull the trigger and [announced an Uppy Month](https://uppy.io/blog/2019/03/liftoff-01/) within Transloadit. This meant that all team members, including those not working primarily on Uppy — the Tus core team, our SDK teams, as well as our infra and API engineers, designers, content writers, and the founders themselves — all chipped in and did their part to ensure liftoff in thirty days. We also asked [Evgenia](http://github.com/lakesare) to join us for the month to lend a hand with frontend work. Every week, we had a call where we looked at the Uppy 1.0 project board and talked about our progress:
+
+<img src="/images/blog/30daystoliftoff/15-dashboard.png">
 
 Here are some highlights of what we’ve managed to deliver during one month of Everything Uppy:
 
-- A new Uppy website design
+- A new Uppy website design.
 - [Localization support and language packs](https://github.com/transloadit/uppy/pull/1443) for Russian, German, Dutch and French (with more coming from the community). [Kevin](https://github.com/kvz) and I wrote a script that loops through all Uppy plugins in the repo and generates one canonical `en_US` that can be used as a basis for other translations. The script even checks for missing strings accross all translations, so you know which ones to update.
 - [Drag and Drop in the Dashboard](https://github.com/transloadit/uppy/pull/1440), being an important part of Uppy, has been significantly improved with support for pasting files and links from both the browser and the device. So you can now, say, drag a link or an image from a different tab to Uppy!
 - [Basic React Native support (Beta)](https://github.com/transloadit/uppy/pull/988): Uppy runs in a React Native environment, we have an example with resumable uploads via tus, and `@uppy/react-native` Expo-component support for picking images, videos, documents, and files from remote URLs with the help of Companion.
 - [Design facelift](https://github.com/transloadit/uppy/pull/1442): the Dashboard UI has been significantly improved in the past days: new icons have been added, as well as typography polishing, better color organization, enlarged clickable areas, and more.
-- Many accessibility issues uncovered
+- Many accessibility issues uncovered.
 - [Robodog gained support for an inline Dashboard](https://github.com/transloadit/uppy/pull/1450).
 - [The documentation structure has been reworked](https://github.com/transloadit/uppy/pull/1405).
 - [Transloadit Assemblies can now be properly canceled](https://github.com/transloadit/uppy/pull/1431).
@@ -78,16 +84,22 @@ Here are some highlights of what we’ve managed to deliver during one month of
 - [npm scripts have been refactored](https://github.com/transloadit/uppy/pull/1392) — yes, that's important!
 - And craziest of all: our content team has been on a roll and [released a post *every day*](https://uppy.io/blog/2019/03/liftoff-01/) for the past thirty days to keep you updated on our day-to-day progress.
 
-## Which features made it into 1.0? And which didn't (yet)?
+## Which features made it into 1.0? And which didn’t (yet)?
 
 Uppy 1.0 feature list:
 
+- Sleek user interface
 - Lightweight and easy on dependencies
 - A small core with modular architecture: everything is a plugin
 - Uses modern JavaScript with transpiled ES5 versions available in `lib`, and minified versions for direct use by browsers in `dist`
 - Usable as a bundle straight from a CDN, as well as a module to import
 - Resumable file uploads via the open Tus standard
-- Robust: retries for all-the-things, no showing of ‘weird errors’
+- Direct uploads to S3
+- Webcam support
+- Picking files from Dropbox, Google Drive and Instagram, while letting servers do the heavy lifting via Companion
+- Robust: retries for all-the-things
+- Built with accessibility in mind (not perfect yet, but we constantly improve)
+- File recovery (after a browser crash or accidental navigation) via Golden Retriever
 - Locale support: easily switch languages or supply your own copy
 - Compatible with React (React Native in beta)
 - Works great on mobile
@@ -95,15 +107,15 @@ Uppy 1.0 feature list:
 
 We also left two features "behind":
 
-> Offering sugared shortcuts for novice users (presets) 
+> Offering sugared shortcuts for novice users (presets)
 
-We felt that Uppy is straightforward enough to use, and presets could end up making this less clear. Robodog does offer less 'boilerplatey' integrations, but this was done as a wrapper instead of a preset.
+We felt that Uppy is straightforward enough to use, and presets could end up making this less clear. Robodog does offer less “boilerplatey” integrations, but this was done as a wrapper instead of a preset.
 
-> Themable UI with a beautiful default 
+> Themable UI with a beautiful default
 
 Instead of going for `{ theme: 'dark' }`, we only offer theming via CSS. It is, of course, very feasible to create a `dark.css` file, and maybe we can come up with a section on the site for easily sharing and distributing such files, but we let go of this desire for Uppy 1.0.
 
-Lastly, our 'picking files from remote sources' feature isn't quite as full fledged as we maybe would have liked, since support for, e.g., Google Photos is currently not included. We hope these are things that the community can help with. So, while we didn't tick all the boxes, for a three-year gameplan, we are very happy with this result.
+Lastly, our “picking files from remote sources” feature isn’t quite as full fledged as we maybe would have liked, since support for, e.g., Google Photos is currently not included. We hope these are things that the community can help with. So, while we didn’t tick all the boxes, for a three-year gameplan, we are very happy with this result.
 
 ## What’s next for Uppy?