add markdown linting using remark (#2181)

* build: add markdown linting

* build: support markdown front matter

* build: fail remark lint on warnings

* Fix markdown lint warnings

* changelog: fix markdown errors, allow literal URLs

* ci: add markdown lint step

* website: regenerate contributing.md

* build: properly ignore vendor and built files from remark-lint

* build: add private packages to lerna config

.github/CONTRIBUTING.md

@@ -145,7 +145,7 @@ To quickly summarize:
 
 #### Utilities
 
-Syntax: u-[sm-|md-|lg-]<utilityName>
+Syntax: `u-[sm-|md-|lg-]<utilityName>`
 
 ```css
 .u-utilityName
@@ -155,7 +155,7 @@ Syntax: u-[sm-|md-|lg-]<utilityName>
 
 #### Components
 
-Syntax: [<namespace>-]<ComponentName>[-descendentName][--modifierName]
+Syntax: `[<namespace>-]<ComponentName>[-descendentName][--modifierName]`
 
 ```css
 .twt-Button /* Namespaced component */

.gitignore

@@ -13,6 +13,7 @@ dist/
 lib/
 coverage/
 examples/dev/bundle.js
+examples/aws-presigned-url/vendor/*
 test/endtoend/create-react-app/build/
 test/endtoend/create-react-app/coverage/
 uppy-*.tgz

.travis.yml

@@ -37,10 +37,17 @@ jobs:
     - name: 'Run unit tests on Node.js 10'
       node_js: 10
       script: npm run test:unit
-    - name: 'Run Linting and type tests'
+    - name: 'Run Linting'
       node_js: 10
       script:
         - npm run lint
+    - name: 'Run Markdown Linting'
+      node_js: 10
+      script:
+        - npm run lint:markdown
+    - name: 'Run type tests'
+      node_js: 10
+      script:
         # Need to do a bunch of work to generate the locale typings 🙃
         - npm run build:lib
         - npm run build:companion

CHANGELOG.md

@@ -1,3 +1,7 @@
+# Changelog
+
+<!--lint disable no-literal-urls-->
+
 Our combined changelog and roadmap. It contains todos as well as dones.
 
 Items can be optionally be tagged tagged by GitHub owner issue if discussion
@@ -319,7 +323,7 @@ This release adds `@uppy/onedrive` to `uppy`’s `package.json`, fixing the bug
 - build: Actually check types. Use tsd so our typings test files can actually assert that types are correct (#1918 / @goto-bus-stop )
 - @uppy/companion: Only set cookies for providers that need it (#2055 / @ifedapoolarewaju)
 - docs: Add Content-Type header to presigned url example (#2061 / @scherroman)
-- uppy: Add onedrive to uppy package.json ([349247607513bc6b33bf2a90ab0b82f8f2e81d78](https://github.com/transloadit/uppy/commit/349247607513bc6b33bf2a90ab0b82f8f2e81d78 / @arturi))
+- uppy: Add onedrive to uppy package.json ([349247607513bc6b33bf2a90ab0b82f8f2e81d78](https://github.com/transloadit/uppy/commit/349247607513bc6b33bf2a90ab0b82f8f2e81d78) / @arturi)
 
 ## 1.9.1
 
@@ -1269,7 +1273,7 @@ New versions in this release:
 
 Changes:
 
-- build: Add initial version table script [skip ci] (@goto-bus-stop)
+- build: Add initial version table script (@goto-bus-stop)
 - build: Add more checks to release script (#1050 / @goto-bus-stop)
 - build: start companion once in tests (#1052 / @ifedapoolarewaju)
 - buid: set companion config values when running test (@ifedapoolarewaju)
@@ -1524,7 +1528,7 @@ Changed strings:
 
 Released: 2018-05-14.
 
-- core: Pass `allowedFileTypes` and `maxNumberOfFiles` to input[type=file] in UI components: Dashboard, DragDrop, FileInput (#814 / @arturi)
+- core: Pass `allowedFileTypes` and `maxNumberOfFiles` to `input[type=file]` in UI components: Dashboard, DragDrop, FileInput (#814 / @arturi)
 - transloadit: Update Transloadit plugin's Uppy Server handling (#804 / @goto-bus-stop)
 - tus: respect `limit` option for upload parameter requests (#817 / @ap--)
 - docs: Explain name `metadata` vs. `$_FILES[]["name"]` (#1c1bf2e / @goto-bus-stop)
@@ -1987,7 +1991,7 @@ Favorite Uppy Server version: 0.5.0.
 - website: try on a Github ribbon http://tholman.com/github-corners/ (@arturi / #150)
 - website: different meta description for pages and post (@arturi)
 - server: well documented README (@ifedapoolarewaju)
-- react: [WIP] High-level React Components (@goto-bus-stop / #170)
+- react: High-level React Components (@goto-bus-stop / #170)
 - core: add `uppy.close()` for tearing down an Uppy instance (@goto-bus-stop / #182)
 - core: replace `babel-preset-es2015-loose` by standard es2015 preset with `loose` option (@goto-bus-stop / #174)
 

lerna.json

@@ -4,6 +4,7 @@
     "website",
     "examples/*",
     "packages/*",
-    "packages/@uppy/*"
+    "packages/@uppy/*",
+    "private/*"
   ]
 }

package.json

@@ -4,7 +4,13 @@
   "version": "0.0.0",
   "description": "Extensible JavaScript file upload widget with support for drag&drop, resumable uploads, previews, restrictions, file processing/encoding, remote providers like Instagram, Dropbox, Google Drive, S3 and more :dog:",
   "lint-staged": {
-    "*.js": "eslint"
+    "*.js": "eslint",
+    "*.md": "remark -f -q -i .gitignore"
+  },
+  "remarkConfig": {
+    "plugins": [
+      "remark-lint-uppy"
+    ]
   },
   "size-limit": [
     {
@@ -65,6 +71,7 @@
     "@uppy/utils": "file:packages/@uppy/utils",
     "@uppy/webcam": "file:packages/@uppy/webcam",
     "@uppy/xhr-upload": "file:packages/@uppy/xhr-upload",
+    "remark-lint-uppy": "file:private/remark-lint-uppy",
     "uppy": "file:packages/uppy",
     "uppy.io": "file:website"
   },
@@ -169,6 +176,7 @@
     "react": "16.12.0",
     "react-dom": "16.12.0",
     "redux": "4.0.5",
+    "remark-cli": "^8.0.0",
     "replace-x": "1.7.2",
     "rimraf": "2.7.1",
     "stringify-object": "3.3.0",
@@ -204,6 +212,7 @@
     "dev": "npm-run-all --parallel dev:watch-sandbox watch:js:lib watch:css dev:browsersync",
     "example": "node bin/run-example",
     "lint:fix": "npm run lint -- --fix",
+    "lint:markdown": "remark -f -q . -i .gitignore",
     "lint:staged": "lint-staged",
     "lint": "eslint . --cache",
     "release": "./bin/release",

packages/@uppy/companion/ARCHITECTURE.md

@@ -5,7 +5,7 @@ The purpose of Companion is to interface with third party APIs and handle remote
 
 ## oAuth with Grant, Sessions
 Companion uses an oAuth middleware library called `Grant` to simplify oAuth authentication.
-Inside of `config/grant.js`, you configure the oAuth providers you wish to use, providing things like client key, 
+Inside of `config/grant.js`, you configure the oAuth providers you wish to use, providing things like client key,
 client secret, scopes, and the callback URL you wish to use.  For example:
 
 ```
@@ -20,11 +20,11 @@ client secret, scopes, and the callback URL you wish to use.  For example:
   }
 ```
 
-Once this `google` config is added to `config/grant.js`, Grant automatically creates a route `/connect/google` that 
+Once this `google` config is added to `config/grant.js`, Grant automatically creates a route `/connect/google` that
 redirects to Google's oAuth page.  So on the client side, you just need to link the user to `https://your-server/connect/google`.
 
 After the user completes the oAuth flow, they should always be redirected to `https://your-server/:provider/callback`.
-The `/:provider/callback` routes are handled by the `callback` controller at `server/controllers/callback.js`.  
+The `/:provider/callback` routes are handled by the `callback` controller at `server/controllers/callback.js`.
 This controller receives the oAuth token, generates a json web token with it, and sends the generated json web token to the client by adding it to the cookies. This way companion doesn't have to save users' oAuth tokens (which is good from the security perspective).
 This json web token would be sent to companion in subsequent requests and the oAuth token can be read from it.
 
@@ -61,10 +61,10 @@ Since each API works differently, we need to describe how to `download` and `lis
 
 **Note:** As of right now, you only need to implement `YourProvider.prototype.list` and `YourProvider.prototype.download` for each provider, I believe.  `stats` seems to be used by Dropbox to get a list of files, so that's required there, but `upload` is optional unless you all decide to allow uploading to third parties.  I got that code from an example.
 
-This whole approach was inspired by an example from `purest 2.x`.  Keep in mind that we're using `3.x`, so the API is different, but here is the example for reference: https://github.com/simov/purest/tree/2.x/examples/storage
+This whole approach was inspired by an example from `purest 2.x`.  Keep in mind that we're using `3.x`, so the API is different, but here is the example for reference: <https://github.com/simov/purest/tree/2.x/examples/storage>
 
 ## WebSockets
-Companion uses WebSockets to transfer `progress` events to the client during file transfers.  It's currently only set up to transfer progress during Tus uploads to the target server.  
+Companion uses WebSockets to transfer `progress` events to the client during file transfers.  It's currently only set up to transfer progress during Tus uploads to the target server.
 
 When a request is made to `/:provider/get` to start a transfer, a token is generated and sent back to the client in response.  The client then connects to `wss://your-server/whatever-their-token-is`.  Any events that are emitted using the token as the name (i.e. `emitter.emit('whatever-their-token-is', progressData)`) are sent back to the client.
 

packages/@uppy/companion/KUBERNETES.md

@@ -1,10 +1,12 @@
 ### Run companion on kuberenetes
 
 You can use our docker container to run companion on kubernetes with the following configuration.
+
 ```bash
 kubectl create ns uppy
 ```
-We will need a Redis container that we can get through [helm](https://github.com/kubernetes/helm)
+
+We will need a Redis container that we can get through [helm](https://github.com/kubernetes/helm):
 
 ```bash
  helm install --name redis \
@@ -13,7 +15,9 @@ We will need a Redis container that we can get through [helm](https://github.com
     stable/redis
 ```
 
-> companion-env.yml
+
+#### `companion-env.yml`
+
 ```yaml
 apiVersion: v1
 data:
@@ -43,7 +47,8 @@ metadata:
 type: Opaque
 ```
 
-> companion-deployment.yml
+#### `companion-deployment.yml`
+
 ```yaml
 apiVersion: extensions/v1beta1
 kind: Deployment
@@ -66,7 +71,7 @@ spec:
       containers:
       - image: docker.io/transloadit/companion:latest
         imagePullPolicy: ifNotPresent
-        name: companion        
+        name: companion
         resources:
           limits:
             memory: 150Mi
@@ -85,9 +90,11 @@ spec:
         emptyDir: {}
 ```
 
-`kubectl apply -f companion-deployment.yml`
+```bash
+kubectl apply -f companion-deployment.yml
+```
 
-> companion-service.yml
+#### `companion-service.yml`
 
 ```yaml
 apiVersion: v1
@@ -104,12 +111,14 @@ spec:
     app: companion
 ```
 
-`kubectl apply -f companion-service.yml`
+```bash
+kubectl apply -f companion-service.yml
+```
 
 ## Logging
 
-You can check the production logs for the production pod using: 
+You can check the production logs for the production pod using:
 
 ```bash
-kubectl logs my-pod-name 
+kubectl logs my-pod-name
 ```

packages/@uppy/utils/src/getDroppedFiles/README.md

@@ -1,10 +1,10 @@
 Influenced by:
-  - https://github.com/leonadler/drag-and-drop-across-browsers
-  - https://github.com/silverwind/uppie/blob/master/uppie.js
-  - https://stackoverflow.com/a/50030399/3192470
+  - <https://github.com/leonadler/drag-and-drop-across-browsers>
+  - <https://github.com/silverwind/uppie/blob/master/uppie.js>
+  - <https://stackoverflow.com/a/50030399/3192470>
 
 ### Why do we not use `getFilesAndDirectories()` api?
 
 It's a proposed spec that seems to be barely implemented anywhere.
 Supposed to work in Firefox and Edge, but it doesn't work in Firefox, and both Firefox and Edge support `.webkitGetAsEntry()` api anyway.
-This page e.g. shows how this spec is supposed to function: https://wicg.github.io/directory-upload/, but it only works because of the polyfill.js that uses `.webkitGetAsEntry()` internally.
+This page e.g. shows how this spec is supposed to function: <https://wicg.github.io/directory-upload/>, but it only works because of the polyfill.js that uses `.webkitGetAsEntry()` internally.

private/README.md

@@ -0,0 +1,2 @@
+# Private packages
+Node.js packages for internal use by Uppy, like build tooling. These are not published to npm.

private/remark-lint-uppy/README.md

@@ -0,0 +1,14 @@
+# remark-lint-uppy
+remark-lint preset derived from [`remark-preset-lint-recommended`][remark-preset-lint-recommended].
+
+Differences:
+- The `list-item-bullet-indent` rule is disabled.
+- The `list-item-indent` rule is disabled.
+
+The reason for the differences is that these "wrong" patterns are ubiquitous in our markdown files and we don't want to do these huge changes after adding the linter.
+
+## License
+[MIT][].
+
+[remark-preset-lint-recommended]: https://github.com/remarkjs/remark-lint/blob/master/packages/remark-preset-lint-recommended
+[MIT]: ./LICENSE

private/remark-lint-uppy/index.js

@@ -0,0 +1,23 @@
+'use strict'
+
+exports.plugins = [
+  require('remark-frontmatter'),
+  // Do a lint.
+  require('remark-lint'),
+  // Unix compatibility.
+  require('remark-lint-final-newline'),
+  // Differs or unsupported across vendors.
+  require('remark-lint-no-auto-link-without-protocol'),
+  require('remark-lint-no-blockquote-without-marker'),
+  require('remark-lint-no-literal-urls'),
+  [require('remark-lint-ordered-list-marker-style'), '.'],
+  // Mistakes.
+  require('remark-lint-hard-break-spaces'),
+  require('remark-lint-no-duplicate-definitions'),
+  require('remark-lint-no-heading-content-indent'),
+  require('remark-lint-no-inline-padding'),
+  require('remark-lint-no-shortcut-reference-image'),
+  require('remark-lint-no-shortcut-reference-link'),
+  require('remark-lint-no-undefined-references'),
+  require('remark-lint-no-unused-definitions')
+]

private/remark-lint-uppy/package.json

@@ -0,0 +1,22 @@
+{
+  "name": "remark-lint-uppy",
+  "version": "0.0.0",
+  "dependencies": {
+    "remark-frontmatter": "^2.0.0",
+    "remark-lint": "^7.0.0",
+    "remark-lint-final-newline": "^1.0.4",
+    "remark-lint-hard-break-spaces": "^2.0.0",
+    "remark-lint-no-auto-link-without-protocol": "^2.0.0",
+    "remark-lint-no-blockquote-without-marker": "^3.0.0",
+    "remark-lint-no-duplicate-definitions": "^2.0.0",
+    "remark-lint-no-heading-content-indent": "^2.0.0",
+    "remark-lint-no-inline-padding": "^2.0.0",
+    "remark-lint-no-literal-urls": "^2.0.0",
+    "remark-lint-no-shortcut-reference-image": "^2.0.0",
+    "remark-lint-no-shortcut-reference-link": "^2.0.0",
+    "remark-lint-no-undefined-references": "^2.0.0",
+    "remark-lint-no-unused-definitions": "^2.0.0",
+    "remark-lint-ordered-list-marker-style": "^2.0.0"
+  },
+  "private": true
+}

website/src/_posts/2016-08-0.8.0.md

@@ -72,7 +72,7 @@ Here is the full list of changes for version 0.8.0.
 - meta: release “Uppy Begins” post ([@arturi](https://github.com/arturi) [@kvz](https://github.com/kvz))
 - meta: better readme on GitHub and NPM ([@arturi](https://github.com/arturi))
 - test: add pre-commit & lint-staged ([@arturi](https://github.com/arturi))
-- test: add next-update https://www.npmjs.com/package/next-update to check if packages we use can be safely updated ([@arturi](https://github.com/arturi))
+- test: add next-update <https://www.npmjs.com/package/next-update> to check if packages we use can be safely updated ([@arturi](https://github.com/arturi))
 - website: blog polish — add post authors and their gravatars ([@arturi](https://github.com/arturi))
 - dashboard: UI revamp, more prototypes, background image, make dashboard nicer ([@arturi](https://github.com/arturi))
 - dashboard: try a workflow where import from external service slides over and takes up the whole dashboard screen ([@arturi](https://github.com/arturi))

website/src/_posts/2016-08-0.9.0.md

@@ -46,17 +46,17 @@ Under the hood, we have made some changes to how the UI is structured.  We are t
 Here is the full list of changes for version 0.9.0.:
 
 - dashboard: informer interface: message when all uploads are "done" ([@arturi](https://github.com/arturi))
-- dashboard: improve file paste — not really possible — no file names, weird API, Chrome-only http://stackoverflow.com/a/22940020 ([@arturi](https://github.com/arturi))
+- dashboard: improve file paste — not really possible — no file names, weird API, Chrome-only <http://stackoverflow.com/a/22940020> ([@arturi](https://github.com/arturi))
 - meta: add google demo account [@kvz](https://github.com/kvz))
 - meta: Set up a Google testing account that people can use to try the demo ([@hedgerh](https://github.com/hedgerh))
 - meta: write 0.9 release blog post ([@hedgerh](https://github.com/hedgerh))
 - webcam: a barely working webcam snapshot & upload ([@hedgerh](https://github.com/hedgerh))
-- metadata: Uppy + tus empty metadata value issue in Safari https://github.com/tus/tus-js-client/issues/41 --> tus issue — nailed down, passed to @account (@arturi, @account)
+- metadata: Uppy + tus empty metadata value issue in Safari <https://github.com/tus/tus-js-client/issues/41> --> tus issue — nailed down, passed to @account (@arturi, @account)
 - core: experiment with switching to `virtual-dom` in a separate branch; experiment with rollup again ([@arturi](https://github.com/arturi))
-- core: figure out race conditions (animations not completing because file div gets re-added to the dom each time) with `yo-yo`/`morphdom` https://github.com/shama/bel/issues/26#issuecomment-238004130 ([@arturi](https://github.com/arturi))
-- core: switch to https://github.com/sethvincent/namespace-emitter — smaller, allows for `on('*')` ([@arturi](https://github.com/arturi))
+- core: figure out race conditions (animations not completing because file div gets re-added to the dom each time) with `yo-yo`/`morphdom` <https://github.com/shama/bel/issues/26#issuecomment-238004130> ([@arturi](https://github.com/arturi))
+- core: switch to <https://github.com/sethvincent/namespace-emitter> — smaller, allows for `on('*')` ([@arturi](https://github.com/arturi))
 - dashboard: add aria-labels and titles everywhere to improve accessibility #114 ([@arturi](https://github.com/arturi))
-- dashboard: file name + extension should fit on two lines, truncate in the middle (maybe https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/measureText) ([@arturi](https://github.com/arturi))
+- dashboard: file name + extension should fit on two lines, truncate in the middle (maybe <https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/measureText>) ([@arturi](https://github.com/arturi))
 - dashboard: implement a circular progress indicator on top of the fileItem with play/pause ([@arturi](https://github.com/arturi))
 - dashboard: refactor to smaller components, as discussed in #110 ([@arturi](https://github.com/arturi))
 - google drive: refactor to smaller components, as discussed in #110 ([@hedgerh](https://github.com/hedgerh))
@@ -65,7 +65,7 @@ Here is the full list of changes for version 0.9.0.:
 - metadata: the aftermath — better UI ([@arturi](https://github.com/arturi))
 - test: Get IE6 on Win XP to run Uppy and see it fall back to regular form upload #108 ([@arturi](https://github.com/arturi))
 - test: refactor tests, add DragDrop back ([@arturi](https://github.com/arturi))
-- tus: update uppy to tus-js-client@1.2.1, test on requirebin ([@arturi](https://github.com/arturi))
+- tus: update uppy to `tus-js-client@1.2.1`, test on requirebin ([@arturi](https://github.com/arturi))
 - tus: add ability to pause/resume all uploads at once ([@arturi](https://github.com/arturi))
 - tus: add ability to pause/resume upload ([@arturi](https://github.com/arturi))
 

website/src/_posts/2016-09-0.10.md

@@ -75,23 +75,23 @@ Here is the full list of changes for version 0.10.0:
 
 - core: expose some events/APIs/callbacks to the user: `onFileUploaded`, `onFileSelected`, `onAllUploaded`, `addFile` (or `parseFile`), open modal... (@arturi, @hedgerh)
 - core: how would Uppy work without the UI, if one wants to Uppy to just add files and upload, while rendering preview and UI by themselves #116 — discussion Part 1 (@arturi, @hedgerh)
-- core: refactor towards react compatibility as discussed in https://github.com/transloadit/uppy/issues/110 (@hedgerh)
-- core: CSS modules? allow bundling of CSS in JS for simple use in NPM? See #120#issuecomment-242455042, try https://github.com/rtsao/csjs — verdict: not yet, try again later (@arturi, @hedgerh)
+- core: refactor towards react compatibility as discussed in <https://github.com/transloadit/uppy/issues/110> (@hedgerh)
+- core: CSS modules? allow bundling of CSS in JS for simple use in NPM? See <https://github.com/transloadit/uppy/issues/120#issuecomment-242455042>, try <https://github.com/rtsao/csjs> — verdict: not yet, try again later (@arturi, @hedgerh)
 - core: try Web Workers and FileReaderSync for image resizing again — still slow, probably message payload between webworker and regular thread is huge (@arturi)
-- core: i18n strings should extend default en_US dictionary — if a certain string in not available in German, English should be displayed (@arturi)
+- core: i18n strings should extend default `en_US` dictionary — if a certain string in not available in German, English should be displayed (@arturi)
 - dashboard: refactor to smaller components, pass props down (@arturi)
 - dashboard: option to render Dashboard inline instead of a modal dialog (@arturi)
 - dashboard: global circular progress bar, try out different designs for total upload speed and ETA (@arturi)
 - dashboard: show total upload speed and ETA, for all files (@arturi)
-- dashboard: copy link to uploaded file button, cross-browser (@arturi) (http://i.imgur.com/b1Io34n.png) (@arturi)
+- dashboard: copy link to uploaded file button, cross-browser (@arturi) (<http://i.imgur.com/b1Io34n.png>) (@arturi)
 - dashobard: refreshed design and grand refactor (@arturi)
-- dashboard: improve file paste the best we can http://stackoverflow.com/a/22940020 (@arturi)
+- dashboard: improve file paste the best we can <http://stackoverflow.com/a/22940020> (@arturi)
 - provider: abstract google drive into provider plugin for reuse (@hedgerh)
 - google drive: improve UI (@hedgerh)
 - tus: add `resumable` capability flag (@arturi)
 - tus: start fixing pause/resume issues and race conditions (@arturi)
-- test: working Uppy example on Require Bin — latest version straight from NPM http://requirebin.com/?gist=54e076cccc929cc567cb0aba38815105 (@arturi @account)
-- meta: update readme docs, add unpkg CDN links (https://unpkg.com/uppy/dist/uppy.min.css) (@arturi)
+- test: working Uppy example on Require Bin — latest version straight from NPM <http://requirebin.com/?gist=54e076cccc929cc567cb0aba38815105> (@arturi @account)
+- meta: update readme docs, add unpkg CDN links (<https://unpkg.com/uppy/dist/uppy.min.css>) (@arturi)
 - meta: write 0.10 release blog post (@arturi)
 
 We’ll see you in about a month!

website/src/_posts/2016-11-0.11.md

@@ -56,7 +56,7 @@ Here is the full list of changes for version 0.11:
 
 - core: log method should have an option to throw error in addition to just logging (@arturi)
 - experimental: PersistentState plugin that saves state to localStorage — useful for development (@arturi)
-- dashboard: implement new StatusBar with progress and pause/resume buttons https://github.com/transloadit/uppy/issues/96#issuecomment-249401532 (@arturi)
+- dashboard: implement new StatusBar with progress and pause/resume buttons <https://github.com/transloadit/uppy/issues/96#issuecomment-249401532> (@arturi)
 - dashboard: attempt to throttle StatusBar, so it doesn’t re-render too often (@arturi)
 - dashboard: refactor — only load one acquire panel at a time (activeAcquirer or empty), change focus behavior, utilize onload/onunload
 - experimental: create a Dashboard UI for Redux refactor (@hedgerh)

website/src/_posts/2016-12-0.12.md

@@ -31,7 +31,7 @@ Uppy server has undergone a quite a few changes, including the build setup:
 
 ## And
 
-- The website now features a video demo of Uppy in action, check it out: http://uppy.io.
+- The website now features a video demo of Uppy in action, check it out: <http://uppy.io>.
 - Fixed a bug where the Webcam would continue to be active (green light on) even after the picture was taken — all good now.
 - Improved import/require support for ES2015 and CommonJS modules. Basically, we don’t recommend ES2015 spread imports as a default option just yet — no tree shaking in Browserify and Webpack 1. Both `import DragDrop from 'uppy/lib/plugin/DragDrop'` and `const DragDrop = require('uppy/lib/plugin/DragDrop')` are now supported. We’ve added `add-module-exports` babel plugin that replaces `export default` with `module.exports` for backwards compatibility.
 - Optimized dependencies a little: removed the ones we don’t use, upgraded some that we do.
@@ -42,12 +42,12 @@ Here is the full list of changes for version 0.12:
 
 - meta: write 0.12 release blog post (@arturi)
 - core: figure out import/require for core and plugins — just don’t use spread for plugins (@arturi)
-- meta: create a demo GIF, showcasing Uppy Dashboard for the main page, like https://zeit.co/blog/next (@arturi)
+- meta: create a demo GIF, showcasing Uppy Dashboard for the main page, like <https://zeit.co/blog/next> (@arturi)
 - meta: update Readme, update screenshot (@arturi)
 - server: add pre-commit and lint-staged (@arturi)
 - server: re-do build setup: building at `deploy` and `prepublish` when typing `npm run release:patch` 0.0.1 -> 0.0.2 (@ifedapoolarewaju)
 - server: re-do build setup: es6 `src` -> es5 `lib` (use plugin packs from Uppy)
-- server: re-do build setup: `eslint --fix ./src` via http://standardjs.com (@ifedapoolarewaju)
+- server: re-do build setup: `eslint --fix ./src` via <http://standardjs.com> (@ifedapoolarewaju)
 - server: re-do build setup: `babel-node` or `babel-require` could do realtime transpiling for development (how does that hook in with e.g. `nodemon`?) (@ifedapoolarewaju)
 - server: refacor: remove/reduce file redundancy (@ifedapoolarewaju)
 - server: error handling: 404 and 401 error handler (@ifedapoolarewaju)

website/src/_posts/2017-02-0.14.md

@@ -24,7 +24,7 @@ We’ve switched to Express from Koa. It’s more widely adopted and supported,
 Uppy Server can now be plugged into your existing Express/Koa server app, but you can also still run it as a standalone server. [See here](https://github.com/transloadit/uppy-server#run-as-standalone-server) for further instructions.
 
 **Smooth authentication**
-It used to be the case that when you clicked that stylish “authenticate” [with Google Drive] button, you were taken away from the page, and things tended to get lost. That has now all been made silky smooth: upon clicking the button, a fresh tab will open in your browser, which will take you to the authentication page – be it on Google Drive, Dropbox, or somewhere else. When you are done, this tab is automagically closed, and you are back where you were, authenticated, with all your remote files at hand.
+It used to be the case that when you clicked that stylish “authenticate” \[with Google Drive] button, you were taken away from the page, and things tended to get lost. That has now all been made silky smooth: upon clicking the button, a fresh tab will open in your browser, which will take you to the authentication page – be it on Google Drive, Dropbox, or somewhere else. When you are done, this tab is automagically closed, and you are back where you were, authenticated, with all your remote files at hand.
 
 <img class="border" src="/images/blog/0.14/smooth-auth.png">
 
@@ -99,7 +99,7 @@ Here is the full list of changes for version 0.14:
 - dashboard: more icons for file types (@arturi)
 - dashboard: add totalSize and totalUploadedSize to StatusBar (@arturi)
 - dashboard: figure out where to place Informer, accounting for StatusBar — over the StatusBar for now (@arturi)
-- dashboard: add `<progress>` element for progress bar, like here https://overcast.fm/+BtuxMygVg/. Added hidden for now, for semantics/accessibility (@arturi)
+- dashboard: add `<progress>` element for progress bar, like here <https://overcast.fm/+BtuxMygVg/>. Added hidden for now, for semantics/accessibility (@arturi)
 - dragdrop: show number of selected files, remove upload btn (@arturi)
 - build: exclude locales from build (@arturi)
 - core: i18n for each plugin in options — local instead of global (@arturi)

website/src/_posts/2017-03-0.15.md

@@ -13,7 +13,7 @@ Spring is in the air and Uppy is feeling particularly full of life. In this post
 
 In [`0.14`](http://localhost:4000/blog/2017/02/0.14/), we added `yo-yoify` transform to give Uppy some extra speed and eliminate `Function.caller` issues. As it turned out, we [forgot](https://github.com/transloadit/uppy/issues/158) about our Babel-transpiled `lib` version of Uppy that gets published to NPM 🙀. We then spent some time creating a standalone version of `yo-yoify` that would be able to parse `yo-yo` template strings before Babel-transpilation, only to discover that there already is a [`babel-plugin-yo-yoify`](https://www.npmjs.com/package/babel-plugin-yo-yoify) that not only does precisely that, but also frees us from jumping through a lot of unnecessary hoops. It did [have](https://github.com/goto-bus-stop/babel-plugin-yo-yoify/issues/9) [a few](https://github.com/goto-bus-stop/babel-plugin-yo-yoify/pull/8) [issues](https://github.com/goto-bus-stop/babel-plugin-yo-yoify/issues/11) at first, but luckily our friend [Renée](https://github.com/goto-bus-stop) was available to colaborate with us on this. Renée has also agreed to join Uppy for a while to help us with other pressing issues. So, silver linings — bugs can sometimes lead to new friends and wonderful beginnings. We are very excited about what this all means for Uppy in the months to come.
 
-Uppy from NPM is now good to go and the issue has been completely resolved. You can update at: https://www.npmjs.com/package/uppy. And yeah, if you use `yo-yo`, give [`babel-plugin-yo-yoify`](https://www.npmjs.com/package/babel-plugin-yo-yoify) a try.
+Uppy from NPM is now good to go and the issue has been completely resolved. You can update at: <https://www.npmjs.com/package/uppy>. And yeah, if you use `yo-yo`, give [`babel-plugin-yo-yoify`](https://www.npmjs.com/package/babel-plugin-yo-yoify) a try.
 
 ## Pause & Resume Remote Uploads
 
@@ -53,7 +53,7 @@ Here is the full list of changes for version 0.15:
 
 - build: update dependencies and eslint-plugin-standard, nodemon --> onchange, because simpler and better options (@arturi)
 - build: fix `Function.caller` issue in `lib` which gets published to NPM package, add babel-plugin-yo-yoify (@arturi #158 #163)
-- provider: show error view for things like not being able to connect to uppy server, should this be happening when uppy-server is unavailable http://i.imgur.com/cYJakc9.png (@arturi, @ifedapoolarewaju)
+- provider: show error view for things like not being able to connect to uppy server, should this be happening when uppy-server is unavailable <http://i.imgur.com/cYJakc9.png> (@arturi, @ifedapoolarewaju)
 - provider: loading indicator while files from GoogleDrive / Dropbox are loading (@arturi, @ifedapoolarewaju)
 - provider: logout link/button (@arturi, @ifedapoolarewaju)
 - provider: fix breadcrumbs (@ifedapoolarewaju)

website/src/_posts/2017-05-0.16.md

@@ -35,7 +35,7 @@ The new `.close()` method on the Uppy instance cleans up all of Uppy's event han
 
 We got everything covered - front-to-back-end - so you can be sure we also got some things going on the server side.
 
-- parallelizing downloading/uploading remote files: start uploading chunks right away, while still downloading the file on disk. Even though the server may download files relatively faster, it is good to know that you don't have to wait out the download before the upload begins. 
+- parallelizing downloading/uploading remote files: start uploading chunks right away, while still downloading the file on disk. Even though the server may download files relatively faster, it is good to know that you don't have to wait out the download before the upload begins.
 - Image thumbnails are now also shown for remote files.
 - Automated tests have been added using the test library, [jest](https://facebook.github.io/jest/).
 - Remote files are now deleted from local disk immediately after a successful upload.
@@ -54,7 +54,7 @@ Multiple necessary chores (the kind you don’t like to talk about at parties),
 ## Release Notes
 
 Here is the full list of changes for version 0.16:
-- uploaders: make sure uploads retry/resume if started when offline or disconnected, retry when back online / failed https://github.com/transloadit/uppy/pull/135 (@arturi, @ifedapoolarewaju)
+- uploaders: make sure uploads retry/resume if started when offline or disconnected, retry when back online / failed <https://github.com/transloadit/uppy/pull/135> (@arturi, @ifedapoolarewaju)
 - transloadit: add basic (beta) version of Transloadit plugin (@goto-bus-stop, @kvz, @tim-kos / #28)
 - transloadit: emit an upload event w/ tl data when a file upload is complete (#191 @goto-bus-stop)
 - webcam: implement reading audio+video from webcam (@goto-bus-stop / #175)
@@ -67,14 +67,14 @@ Here is the full list of changes for version 0.16:
 - core: Remove the last few potentially buggy uses of `document.querySelector` (@goto-bus-stop)
 - dashboard: Fix dashboard width when multiple instances exist (@goto-bus-stop / #184)
 - dashboard: add service logo / name to the selected file in file list (@arturi)
-- server: begin adding automated tests, maybe try https://facebook.github.io/jest (@ifedapoolarewaju)
+- server: begin adding automated tests, maybe try <https://facebook.github.io/jest> (@ifedapoolarewaju)
 - server: add image preview / thumbnail for remote files, if its in the API of services (@ifedapoolarewaju)
 - server: research parallelizing downloading/uploading remote files: start uploading chunks right away, while still storing the file on disk (@ifedapoolarewaju)
 - server: delete file from local disk after upload is successful (@ifedapoolarewaju)
-- website: try on a Github ribbon http://tholman.com/github-corners/ (@arturi / #150)
+- website: try on a Github ribbon <http://tholman.com/github-corners/> (@arturi / #150)
 - website: different meta description for pages and post (@arturi)
 - server: well-documented README (@ifedapoolarewaju)
-- react: [WIP] High-level React Components (@goto-bus-stop / #170)
+- react: \[WIP] High-level React Components (@goto-bus-stop / #170)
 - core: add `uppy.close()` for tearing down an Uppy instance (@goto-bus-stop / #182)
 - core: replace `babel-preset-es2015-loose` by standard es2015 preset with `loose` option (@goto-bus-stop / #174)
 

website/src/_posts/2017-05-0.17.md

@@ -9,7 +9,7 @@ Hi! We are back with yet another Uppy release that contains some often requested
 
 <!-- more -->
 
-## ⚠️ File Restrictions 
+## ⚠️ File Restrictions
 
 Something that a few of our biggest fans were asking for, is finally here! Here's the gist of it:
 
@@ -95,7 +95,7 @@ Details: [#217](https://github.com/transloadit/uppy/pull/217)
 
 ## Better file type detection
 
-We’ve added a [`file-type`](https://github.com/sindresorhus/file-type) module that helps with figuring out the file type by reading the first magic bytes of the file. If that doesn’t work, we try to use the mime-type provided by the system/browser, and if that is still a dead end, we attempt to figure it out by extension. All in all, this leads to a more robust file type detecting experience. Personally, I’m just happy my Sex and the City 🍸 `.avi` files are now recognized as `video` on a Mac! 
+We’ve added a [`file-type`](https://github.com/sindresorhus/file-type) module that helps with figuring out the file type by reading the first magic bytes of the file. If that doesn’t work, we try to use the mime-type provided by the system/browser, and if that is still a dead end, we attempt to figure it out by extension. All in all, this leads to a more robust file type detecting experience. Personally, I’m just happy my Sex and the City 🍸 `.avi` files are now recognized as `video` on a Mac!
 
 Further details can be found here: [#219](https://github.com/transloadit/uppy/pull/219)
 
@@ -105,7 +105,7 @@ If a plugin’s `target` is a `form` element, we are going to try to extract all
 
 Uppy’s core options have received a new `meta` property, where you can define some metadata from the start, as well as a new `setMeta` method that can be called at any time.
 
-See here for more details: [#238](https://github.com/transloadit/uppy/pull/238) 
+See here for more details: [#238](https://github.com/transloadit/uppy/pull/238)
 
 ## More
 
@@ -121,9 +121,9 @@ Here is the full list of changes for version 0.17:
 - provider: improved UI: improve overall look, breadcrumbs, more responsive (@arturi)
 - core: css-in-js demos, try template-css (@arturi @goto-bus-stop #239)
 - core: added `uppy.reset()` as discussed in #179 (@arturi)
-- core: added nanoraf https://github.com/yoshuawuyts/choo/pull/135/files?diff=unified (@goto-bus-stop, @arturi)
-- core: file type detection: archives, markdown (possible modules: file-type, identify-filetype) example: http://requirebin.com/?gist=f9bea9602030f1320a227cf7f140c45f, http://stackoverflow.com/a/29672957 (@arturi)
-- dashboard: made file icons prettier: https://uppy.io/images/blog/0.16/service-logos.png (@arturi, @nqst / #215)
+- core: added nanoraf <https://github.com/yoshuawuyts/choo/pull/135/files?diff=unified> (@goto-bus-stop, @arturi)
+- core: file type detection: archives, markdown (possible modules: file-type, identify-filetype) example: <http://requirebin.com/?gist=f9bea9602030f1320a227cf7f140c45f>, <http://stackoverflow.com/a/29672957> (@arturi)
+- dashboard: made file icons prettier: <https://uppy.io/images/blog/0.16/service-logos.png> (@arturi, @nqst / #215)
 - fileinput: allow retrieving fields/options from form (@arturi #153)
 - server: configurable server port (@ifedapoolarewaju)
 - server: added support for custom providers (@ifedapoolarewaju)
@@ -137,14 +137,14 @@ Here is the full list of changes for version 0.17:
 - uppy/uppy-server: allow google drive/dropbox non-tus (i.e multipart) remote uploads (@arturi, @ifedapoolarewaju / #205)
 - uppy/uppy-server: do not show files that cannot be downloaded from Google Drive (@ifedapoolarewaju)
 - uppy: fixed Google Drive uploads on mobile (double click issue) (@arturi)
-- core: updated prettier-bytes to fix the IE support issue https://github.com/Flet/prettier-bytes/issues/3 (@arturi)
+- core: updated prettier-bytes to fix the IE support issue <https://github.com/Flet/prettier-bytes/issues/3> (@arturi)
 - core: use URL.createObjectURL instead of resizing thumbnails (@arturi, @goto-bus-stop / #199)
 - dashboard: fixed ETA when multiple files are being uploaded (@goto-bus-stop, #197)
 - transloadit: fixed receiving assembly results that are not related to an input file (@arturi, @goto-bus-stop / #201)
 - transloadit: use the `tus_upload_url` to reliably link assembly results with their input files (@goto-bus-stop / #207)
-- transloadit: moved user-facing strings into locale option (@goto-bus-stop / https://github.com/transloadit/uppy/commit/87a22e7ee37b6fa3754fa34868516a6700306b60)
+- transloadit: moved user-facing strings into locale option (@goto-bus-stop / <https://github.com/transloadit/uppy/commit/87a22e7ee37b6fa3754fa34868516a6700306b60>)
 - webcam: mute audio in realtime playback (@goto-bus-stop / #196)
-- temporarily downgrade yo-yoify, until shama/yo-yoify#45 is resolved (@arturi / https://github.com/transloadit/uppy/commit/6292b96)
+- temporarily downgrade yo-yoify, until shama/yo-yoify#45 is resolved (@arturi / <https://github.com/transloadit/uppy/commit/6292b96>)
 
 Enjoy!
 

website/src/_posts/2017-08-0.18.md

@@ -12,7 +12,7 @@ Hi! Another month — a new Uppy release 🎉
 
 ## New documentation
 
-Documentation for Uppy has been re-written, and now features chapters on Uppy’s settings and API, using various plugins, and running Uppy Server. Check it out: https://uppy.io/docs/. More chapters to come!
+Documentation for Uppy has been re-written, and now features chapters on Uppy’s settings and API, using various plugins, and running Uppy Server. Check it out: <https://uppy.io/docs/>. More chapters to come!
 
 ## The GoldenRetriever
 

website/src/_posts/2018-02-0.23.md

@@ -105,18 +105,25 @@ On how to set up Uppy with [Shrine](http://shrinerb.com/), a file attachment too
 > There are many popular JavaScript file upload libraries out there – jQuery-File-Upload, Dropzone.js, FineUploader etc. – but the one you should use with Shrine is definitely Uppy 🐶. Uppy is a modular library that knows how to upload files to a custom endpoint on your app, to Amazon S3, or even to a resumable endpoint, providing progress bars, drag & drop functionality, image previews, file validations etc, all while making as few assumptions as possible.
 
 2\. **Featured [in Javascript Daily](https://twitter.com/JavaScriptDaily/status/950348390268919809)**:
+
 > Uppy: A Powerful, Modular JavaScript File Uploader
+
 <cite>— JavaScript Daily</cite>
 
 3\. **[#1 Trending on GitHub](https://twitter.com/uppy_io/status/946485101541683201) accross all languages**:
+
 > Today our open source efforts are outpacing those of MSFT GOOG FB combined :D
+
 <cite>— kvz, transloadit</cite>
 
 4\. **[#2 Product of the Week](https://www.producthunt.com/posts/uppy-io) on ProductHunt**:
-> You literally solved my biggest problem, thank you for developing such a great project. 
+
+> You literally solved my biggest problem, thank you for developing such a great project.
+
 <cite>— Chetan Menaria</cite>
 
 > Writing file upload functionality is always a pain in the arse. I’ll be checking this out today and integrating into SongBox if it’s good.
+
 <cite>— Mick</cite>
 
 5\. **[#2 New Tool of The Year](https://stackshare.io/posts/top-developer-tools-2017) on Stackshare**:
@@ -132,7 +139,7 @@ Here is the full list of changes for version `0.23.0` (and patches `0.22.1`—`0
 - core: Allow chanining after .on() and .off() to improve ergonomics (#597 / @arturi)
 - core: Allow user to override sass variables (#555 / @chao)
 - core: Move preview generation to separate plugin, add queuing (#431 / @richardwillars)
-- core: Third-party extension, uppy-store-ngrx https://github.com/rimlin/uppy-store-ngrx/ (#532 / @rimlin)
+- core: Third-party extension, uppy-store-ngrx <https://github.com/rimlin/uppy-store-ngrx/> (#532 / @rimlin)
 - core: Warn, not error, when file cannot be added due to restrictions? (#604, #492 / @goto-bus-stop)
 - dashboard: Add more i18n strings (#565 / @arturi)
 - dashboard: Fix modal and page scroll (#564 / @arturi)

website/src/_posts/2018-10-0.28.md

@@ -26,7 +26,7 @@ Speaking of the Dashboard, it now also shows more statuses in the title bar: “
 
 ## Status Bar improvements
 
-- ⚠️ **breaking** We’ve added separate options for hiding pause/resume and cancel buttons. So now there are several options for buttons: `hideUploadButton`, `hideRetryButton`, `hidePauseResumeButton` and `hideCancelButton`. These options can be passed from the Dashboard, if you are not using Status Bar separately (most common case). See the docs for more info: https://uppy.io/docs/status-bar/.
+- ⚠️ **breaking** We’ve added separate options for hiding pause/resume and cancel buttons. So now there are several options for buttons: `hideUploadButton`, `hideRetryButton`, `hidePauseResumeButton` and `hideCancelButton`. These options can be passed from the Dashboard, if you are not using Status Bar separately (most common case). See the docs for more info: <https://uppy.io/docs/status-bar/>.
 - The Status Bar now features a spinner animation when upload is in progress.
 - Encoding (with the Transloadit plugin, for example) and uploading progress now get different colors, so it’s easier to tell what’s happening, visually.
 

website/src/_posts/2019-03-0.30.md

@@ -38,7 +38,7 @@ Here’s a demo:
 You can install Robodog from NPM:
 
 ```sh
-npm install @uppy/robodog --save 
+npm install @uppy/robodog --save
 ```
 
 Or import it by using an HTML script tag:
@@ -104,5 +104,5 @@ uppy.on('upload-error', (file, responseObject) => {
 - @uppy/react: Allow changing instance in `uppy` prop (#1247 / @goto-bus-stop)
 - @uppy/react: Typescript: Make DashboardModal.target prop optional (#1254 / @mattes3)
 - @uppy/aws-s3: Use user-provided filename / type for uploaded object, fixes #1238 (#1257 / @goto-bus-stop)
-- @uppy/tus: Update to tus-js-client@1.6.0 with React Native support (#1250 / @arturi)
+- @uppy/tus: Update to `tus-js-client@1.6.0` with React Native support (#1250 / @arturi)
 - build: Improve dev npm script: use Parcel for bundled example, re-build lib automatically, don’t open browser and no ghosts mode, start companion when developing (but there’s optional npm run dev:no-companion) (#1280 / @arturi)

website/src/_posts/2019-03-liftoff-01.md

@@ -8,13 +8,13 @@ seriesSuffix: 'of 30'
 alias: '/blog/2019/03/26-30daystoliftoff-day1/'
 ---
 
-When we [started working on Uppy](/blog/2016/07/uppy-begins/) back in early 2016, all we had was an idea and the shared desire to launch file uploading into a new age. We had already been laying the groundwork with the development of [tus.io](https://tus.io/) and felt that its robust back-end deserved a front-end just as robust, modern and user-friendly. 
+When we [started working on Uppy](/blog/2016/07/uppy-begins/) back in early 2016, all we had was an idea and the shared desire to launch file uploading into a new age. We had already been laying the groundwork with the development of [tus.io](https://tus.io/) and felt that its robust back-end deserved a front-end just as robust, modern and user-friendly.
 
 <!--more-->
 
-But what about open? We initially thought about building a proprietary uploader that would work exclusively with Transloadit's commercial service, but we quickly turned around on it. We knew this could have a real impact. So, just like we did with Tus, we decided to make our new project open source. Three years, [16.000 stargazers](https://github.com/transloadit/uppy/stargazers) and a thriving community later — and we could not be happier. Well, apart from one thing: **getting Uppy 1.0 out the door** has proven harder than expected. Issues keep piling up, which led us down countless sidetracks and hurt our capacity to hammer out those final design goals. 
+But what about open? We initially thought about building a proprietary uploader that would work exclusively with Transloadit's commercial service, but we quickly turned around on it. We knew this could have a real impact. So, just like we did with Tus, we decided to make our new project open source. Three years, [16.000 stargazers](https://github.com/transloadit/uppy/stargazers) and a thriving community later — and we could not be happier. Well, apart from one thing: **getting Uppy 1.0 out the door** has proven harder than expected. Issues keep piling up, which led us down countless sidetracks and hurt our capacity to hammer out those final design goals.
 
-But now it's time for all that to change. That's why, starting today, we are allocating all of Transloadit's resources into making a big final push and getting Uppy ready for liftoff. Our goal is to launch on **April 25**, exactly thirty days from now. 
+But now it's time for all that to change. That's why, starting today, we are allocating all of Transloadit's resources into making a big final push and getting Uppy ready for liftoff. Our goal is to launch on **April 25**, exactly thirty days from now.
 
 <center><img width="400" src="https://media.giphy.com/media/kvw01ozJ06TxS/giphy.gif"><br /><br /></center>
 
@@ -28,7 +28,7 @@ A post each day may prove hard to do, but we think it's worth a try. It really f
 
 ## What's Uppy with you?
 
-We'd love to hear what you think. Whether it is about Uppy in general, or specific issues you feel cannot be forgotten before 1.0, or maybe even about this blog post challenge itself — leave a comment here, use our [forum](https://community.transloadit.com/c/uppy) directly (it also hosts the comments), or let us know on Twitter via [@uppy_io](http://twitter.com/uppy_io/) or [@transloadit](http://twitter.com/transloadit/). 
+We'd love to hear what you think. Whether it is about Uppy in general, or specific issues you feel cannot be forgotten before 1.0, or maybe even about this blog post challenge itself — leave a comment here, use our [forum](https://community.transloadit.com/c/uppy) directly (it also hosts the comments), or let us know on Twitter via [@uppy_io](http://twitter.com/uppy_io/) or [@transloadit](http://twitter.com/transloadit/).
 
 <!-- <center><img width="400"  class="dropshadow" src="https://media.giphy.com/media/RnX4q6yYDoYCI/giphy.gif"></center> -->
 <center><img width="400"  class="dropshadow" src="https://media.giphy.com/media/SjInxhAJTzU7S/giphy.gif"><br /><br /></center>
@@ -38,4 +38,4 @@ We can use your help! As we've said, we're looking to spread the word so any ret
 
 See you tomorrow for the first progress update on [Day 2](/blog/2019/03/liftoff-02/) of our 30 Days to Liftoff!
 
-PS If you don't want to miss an update, consider [good ol' RSS](https://uppy.io/atom.xml) :)
+PS If you don't want to miss an update, consider [good ol' RSS](https://uppy.io/atom.xml) :)

website/src/_posts/2019-03-liftoff-02.md

@@ -8,8 +8,8 @@ seriesSuffix: 'of 30'
 alias: /blog/2019/03/27-30daystoliftoff-day2/
 ---
 
-Yesterday, marked the beginning of our thirty-day blog post challenge to keep you updated on our preparations for **releasing Uppy 1.0 on April 25**. So here we are again already! 
- 
+Yesterday, marked the beginning of our thirty-day blog post challenge to keep you updated on our preparations for **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 we are mostly busy with tying up loose ends, busting issues, and planning our work ahead.
@@ -18,11 +18,11 @@ Our big coding speedrun towards for 1.0 starts April 1, so we are mostly busy wi
 
 ## 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. 
+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'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:
 
@@ -34,4 +34,4 @@ And tomorrow, we'll look at the *To Do*s in more detail, so we can get a clearer
 
 That's all the updates I have for you today. See you tomorrow for [Day 3](/blog/2019/03/liftoff-03/) of our 30 Days to Liftoff!
 
-PS If you don't want to miss an update, consider [good ol' RSS](https://uppy.io/atom.xml) :)
+PS If you don't want to miss an update, consider [good ol' RSS](https://uppy.io/atom.xml) :)

website/src/_posts/2019-04-liftoff-09.md

@@ -22,7 +22,7 @@ Tasks completed by the team since yesterday's update include:
 - Our React Native team (that's [Artur](https://github.com/arturi), [Ife](https://github.com/ifedapoolarewaju), and [Kevin](https://github.com/kvz)) has been working together most of the day and gave an update on the current completed features for implementing Uppy support. Here's a list of completed tasks directly from the team:
     - [x] Make the 'Import from URL' example work in RN
     - [x] Give it its own UI, (re)written for RN
-    - [x] Make websocket progress from Companion work (see: https://facebook.github.io/react-native/docs/network#websocket-support)
+    - [x] Make websocket progress from Companion work (see: <https://facebook.github.io/react-native/docs/network#websocket-support>)
     - [x] Have an example with buttons for resumability and a progress bar
     - [x] Have 20 min resumability support, proof that fingerprinting works for different local file uploads, fix it if not
 
@@ -36,7 +36,7 @@ Meanwhile, on the progress side of things:
 
 - Renée is going to spend the day on getting Transloadit Assemblies to actually cancel when the Cancel button in the UI is pressed. As it stands, the upload cancels, but the Assembly keeps running until it eventually times out by itself.
 
-- [Tim](https://github.com/tim-kos) has started working on fixing an API problem that caused one of our end-to-end tests to intermittently fail and eventually turn off entirely. 
+- [Tim](https://github.com/tim-kos) has started working on fixing an API problem that caused one of our end-to-end tests to intermittently fail and eventually turn off entirely.
 
 - Finally, the React Native team has already completed an impressive amount of tasks, but they aren't slowing down anytime soon. Development marches on as the team begins tackling the following tasks:
     - [ ] Add basic file preview to react native example. Can use `file.uri` for images, can use icons for `file.type===video/audio/document` (Artur Paikin)

website/src/_posts/2019-10-1.5.md

@@ -144,7 +144,7 @@ See [#1843](https://github.com/transloadit/uppy/pull/1843) for details.
 - @uppy/locales: improve Swedish translation (@marcusforberg, #1859)
 - @uppy/thumbnail-generator: add waitForThumbnailsBeforeUpload option, false by default (@arturi, #1803)
 - @uppy/transloadit: add limit option, warn about using limit when it’s set to 0. In Uppy 2.0 we’ll set the limit to something sensible (like 10 files) by default. (#1789 / @arturi)
-- @uppy/transloadit: pin socket.io version to ES5 compatible one (@goto-bus-stop, https://github.com/transloadit/uppy/commit/5839b655f093edaa778d49b719f7dda063ef79cb)
+- @uppy/transloadit: pin socket.io version to ES5 compatible one (@goto-bus-stop, <https://github.com/transloadit/uppy/commit/5839b655f093edaa778d49b719f7dda063ef79cb>)
 - @uppy/xhr-upload: Throw an error when trying to upload a remote file with `bundle: true` (#1769 / @arturi)
 - build: Fix statefulset update: statefulsets image only should be updated. (#1821 / @kiloreux)
 - build: Update eslint to v6 (#1777 / @goto-bus-stop)

website/src/_posts/2020-04-1.10.md

@@ -26,7 +26,7 @@ Try the live demos on [Transloadit.com](https://transloadit.com): import your fi
 
 (Uppy demos are below the description and steps, under “Live Demo. See for yourself” ;-)
 
-You can also play with an interactive demo, enabling different Uppy options and providers on the fly: https://uppy.io/examples/dashboard
+You can also play with an interactive demo, enabling different Uppy options and providers on the fly: <https://uppy.io/examples/dashboard>
 
 OneDrive:
 

website/src/_template/contributing.md

@@ -147,7 +147,7 @@ To quickly summarize:
 
 #### Utilities
 
-Syntax: u-[sm-|md-|lg-]<utilityName>
+Syntax: `u-[sm-|md-|lg-]<utilityName>`
 
 ```css
 .u-utilityName
@@ -157,7 +157,7 @@ Syntax: u-[sm-|md-|lg-]<utilityName>
 
 #### Components
 
-Syntax: [<namespace>-]<ComponentName>[-descendentName][--modifierName]
+Syntax: `[<namespace>-]<ComponentName>[-descendentName][--modifierName]`
 
 ```css
 .twt-Button /* Namespaced component */

website/src/docs/companion.md

@@ -99,6 +99,7 @@ This takes your `server` instance and your Uppy [Options](#Options) as parameter
 ### Running as a standalone server
 
 > Please ensure that the required environment variables are set before running/using Companion as a standalone server. See [Configure Standalone](#Configuring-a-standalone-server) for the variables required.
+
 Set environment variables first:
 
 ```bash
@@ -354,7 +355,7 @@ The default implementation returns the `filename`, so all files will be uploaded
 
 ### Running in Kubernetes
 
-We have [a detailed guide on running Companion in Kubernetes](https://github.com/transloadit/uppy/blob/master/packages/%40uppy/companion/KUBERNETES.md) for you, that’s how we currently run our example server at https://companion.uppy.io.
+We have [a detailed guide on running Companion in Kubernetes](https://github.com/transloadit/uppy/blob/master/packages/%40uppy/companion/KUBERNETES.md) for you, that’s how we currently run our example server at <https://companion.uppy.io>.
 
 ### Adding custom providers
 
@@ -422,7 +423,7 @@ This would get the Companion instance running on `http://localhost:3020`. It use
 
 ## Live example
 
-An example server is running at https://companion.uppy.io, which is deployed with [Kubernetes](https://github.com/transloadit/uppy/blob/master/packages/%40uppy/companion/KUBERNETES.md)
+An example server is running at <https://companion.uppy.io>, which is deployed with [Kubernetes](https://github.com/transloadit/uppy/blob/master/packages/%40uppy/companion/KUBERNETES.md)
 
 
 ## How the Authentication and Token mechanism works

website/src/docs/index.md

@@ -137,7 +137,7 @@ You can also use a pre-built bundle from Transloadit's CDN: Edgly. `Uppy` will a
 - [Plugins](/docs/plugins/) — list of Uppy plugins and their options.
 - [Server](/docs/companion/) — setting up and running a Companion instance, which adds support for Instagram, Dropbox, Google Drive, direct links, and other remote sources.
 - [React](/docs/react/) — components to integrate Uppy UI plugins with React apps.
-- [Writing Plugins](/docs/writing-plugins) — how to write a plugin for Uppy [documentation in progress].
+- [Writing Plugins](/docs/writing-plugins) — how to write a plugin for Uppy (documentation in progress).
 
 ## Browser Support
 

website/src/docs/robodog-form.md

@@ -263,5 +263,4 @@ There are no `on*()` _options_ anymore, but `.on('...')` methods are provided in
 | `onDisconnect` | Currently unavailable, use something like [`is-offline`](https://www.npmjs.com/package/is-offline) |
 | `onReconnect` | Currently unavailable, use something like [`is-offline`](https://www.npmjs.com/package/is-offline) |
 
-[transloadit]: https://transloadit.com
 [transloadit plugin]: https://uppy.io/docs/transloadit/

website/src/docs/thumbnail-generator.md

@@ -75,7 +75,7 @@ If both width and height are given, only width is taken into account.
 >
 > uppy.use(ThumbnailGenerator, { thumbnailWidth: 300, thumbnailHeight: 300 }) will produce a 300px width thumbnail with calculated height to match ratio (and ignore the given height).
 >
-> See https://github.com/transloadit/uppy/issues/979 and https://github.com/transloadit/uppy/pull/1096 for details on this feature.
+> See issue [#979](https://github.com/transloadit/uppy/issues/979) and [#1096](https://github.com/transloadit/uppy/pull/1096) for details on this feature.
 
 ### `waitForThumbnailsBeforeUpload: false`
 

website/src/docs/uppy.md

@@ -615,8 +615,8 @@ uppy.log('[Dashboard] adding files...')
 #### Parameters
 
 - **message** *{(string|object)}* — `'info message'` or `{ message: 'Oh no!', details: 'File couldn’t be uploaded' }`
-- **type** *{string} [type='info']* — `info`, `warning`, `success` or `error`
-- **duration** *{number} [duration = 3000]* — in milliseconds
+- **type** *{string} \[type='info']* — `info`, `warning`, `success` or `error`
+- **duration** *{number} \[duration = 3000]* — in milliseconds
 
 Sets a message in state, with optional details, that can be shown by notification UI plugins. Currently, that means just the [Informer](/docs/informer/) plugin, included by default in Dashboard.
 

website/src/privacy.md

@@ -23,7 +23,7 @@ We receive the following **data** from you:
 3. Data entered on our website
 4. The browser session (identified through a cookie)
 5. Information used to analyze usage of our platform (through cookies from Google Analytics. More on cookies is explained below)
-6. Files you can optionally upload in example demos. Those files are stored temporarily for 24–72 hours, on uppy.io, tus.io or transloadit.com servers, and then deleted. See also Transloadit’s Privacy Policy: https://transloadit.com/legal/privacy/.
+6. Files you can optionally upload in example demos. Those files are stored temporarily for 24–72 hours, on uppy.io, tus.io or transloadit.com servers, and then deleted. See also Transloadit’s Privacy Policy: <https://transloadit.com/legal/privacy/>.
 
 All data that passes through demos is only used for demo purposes, and never sold or otherwise given away.
 
@@ -89,10 +89,10 @@ Our platform uses Google Analytics, which uses cookies. The information created
 
 Google will use this information to analyze your usage of our platform and to create reports about the activities on our platform. The IP address that will be sent to Google as a result of Google Analytics will not be connected to any other data on Google.
 
-You can avoid any cookies being saved by changing the settings in your browser accordingly. Please be aware that if you choose to do so, you might not be able to make full use of our website and all of its features. You can also prevent the analysis of your browsing behavior on our platform through Google Analytics by installing the following browser plugin: http://tools.google.com/dlpage/gaoptout.
+You can avoid any cookies being saved by changing the settings in your browser accordingly. Please be aware that if you choose to do so, you might not be able to make full use of our website and all of its features. You can also prevent the analysis of your browsing behavior on our platform through Google Analytics by installing the following browser plugin: <http://tools.google.com/dlpage/gaoptout>.
 
 Google, Inc. (“Google”) head quarters are located at "1600 Amphitheatre Parkway Mountain View, California 94043, USA".
-Their privacy policy is located here: https://policies.google.com/privacy.
+Their privacy policy is located here: <https://policies.google.com/privacy>.
 
 ## How to disable cookies