Init rewrite branch

Author: kale-stew

.eslintrc

@@ -42,7 +42,12 @@
     "func-style": "off",
     "arrow-parens": "off",
     "no-use-before-define": "off",
-    "no-undef": ["error", { "typeof": true }],
+    "no-undef": [
+      "error",
+      {
+        "typeof": true
+      }
+    ],
     "react/jsx-filename-extension": "off",
     "react/require-extension": "off",
     "react/no-multi-comp": "off",
@@ -60,4 +65,4 @@
       }
     ]
   }
-}
+}

.gitignore

@@ -1,8 +1,2 @@
 node_modules
-package-lock.json
-dist
-lib
-es
-*.log
-.DS_Store
-.vscode
+yarn.lock

.prettierignore

@@ -1,7 +1,5 @@
-package-lock.json
+yarn.lock
 package.json
 node_modules
-dist
 es
 lib
-example/assets

CONTRIBUTING.md

@@ -4,35 +4,21 @@ Thanks for contributing!
 
 ### Installing dependencies
 
+We use [`yarn`](https://yarnpkg.com/en/docs/getting-started).
+
+Install all dependencies by running
+
 ```sh
-yarn install
+yarn
 ```
 
-You will find all building blocks that make up Spectacle in the [`src`](src) folder.
-
 ### Testing
 
-You will find tests for files colocated with `*.test.js` suffixes. Whenever making any changes, ensure that all existing tests pass by running `yarn run test`.
-
-If you are adding a new feature or some extra functionality, you should also make sure to accompany those changes with appropriate tests.
+@TODO
 
 ### Linting and Formatting
 
-Before committing any changes, be sure to do `yarn run lint`; this will lint all relevant files using [ESLint](http://eslint.org/) and report on any changes that you need to make.
-
-You will also want to ensure your code meets the prettier formatting guidelines by running `yarn run prettier -l <filename>` on a specific file. If there are differences the script errors out. You can also specify a glob `yarn run prettier -l "src/**/*.js"` which will return a list of files that do not conform.
-
-Alternatively, install the Prettier [editor plugin](https://prettier.io/docs/en/editors.html) in your favorite editor. This is the preferred method.
-
-There is also a pre-commit hook in place to lint all staged files. If any of the staged files do not conform to the eslint rules or the [prettier](https://prettier.io/) formatting guidelines, your commit will fail until you resolve all outstanding issues.
-
-To resolve/fix prettier formatting problems from the CLI:
-
-```sh
-yarn prettier-fix && yarn lint-fix
-```
-
-This will modify your file in place. You will need to `git add` the file again and re-commit.
+@TODO
 
 ### Before submitting a PR...
 
@@ -43,12 +29,6 @@ Thanks for taking the time to help us make Spectacle even better! Before you go
 - Update the [type definitions](./index.d.ts) for anything that modifies the Spectacle API, like breaking changes or new features.
 - Everything else included in our [pull request checklist](https://github.com/FormidableLabs/spectacle/blob/master/.github/PULL_REQUEST_TEMPLATE.md#checklist-feel-free-to-delete-this-section-upon-completion)
 
-## Releasing a new version to NPM (only for project administrators)
-
-1.  Run `npm version patch` (or `minor`, `major` as appropriate) to run tests and lint, build the `lib` and `dist` directories, and automatically update the `package.json` with a new git tag.
-2.  Run `npm publish` and publish to npm if all is well.
-3.  Run `git push && git push --tags`
-
 ## Contributor Covenant Code of Conduct
 
 ### Our Pledge