diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 000000000..ca1799631
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,73 @@
+# Contributing
+
+> We are working on a more thorough version of these contributing guidlines. For
+> the time being, we've documented our temporary dual-release setup that is
+> necessary for supporting Dart 1 and Dart 2 concurrently.
+
+## Dart 1 & Dart 2 Dual-Releases
+
+Long story short, we are unable to maintain a single codebase of over_react that
+is compatible with both Dart 1 and Dart 2. Transformers only work on Dart 1 and
+builders only work on Dart 2, and we can't maintain the transformer and builder
+together due to dependency conflicts.
+
+> For more information on our Dart 2 migration, [see this guide](/doc/dart2_migration.md).
+
+Fortunately, this problem can be shouldered entirely by the maintainers via a
+dual-release strategy (credit to the [dart2_constant](https://pub.dartlang.org/packages/dart2_constant)
+for the idea). The result is that consumers will depend on a version range of
+this library like they normally do and everything will _just work_.
+
+For every _version_ we want to release, we will actually release two releases -
+a Dart 1 (transformer) version and a Dart 2 (builder) version. These two
+releases will have the same semantic version, but will have unique build
+suffixes. The `pub` client will then decide which one to install based on their
+`environment.sdk` constraints and the active Dart SDK version.
+
+### Branches
+
+- `master`
+ - Dart2-only
+ - Provides a builder
+ - Environment constraint: `>=2.1.0 <3.0.0`
+
+- `master_dart1`
+ - Dart1-only
+ - Provides a transformer
+ - Environment constraint: `>=1.24.3 <2.0.0`
+
+### Release Process
+
+> Note that these steps are intended to be followed by Workiva employees, and as
+> such have some references to internal tooling.
+
+For every release, do the following:
+
+1. Ensure the next release versions exist in MARV:
+
+ Name | Branch
+ ---- | ------
+ over_react 2.x.x-dart1 | master_dart1
+ over_react 2.x.x | master
+
+1. Trigger the `over_react 2.x.x-dart1` release first and review the PR:
+
+ - Ensure the updated `pubspec.yaml` version is correct, including the
+ `-dart1` suffix.
+
+ - Ensure the build passes.
+
+1. Trigger the `over_react 2.x.x` release second and review the PR:
+
+ - Ensure the updated `pubspec.yaml` version is correct.
+
+ - Ensure the build passes.
+
+ - **Add any necessary changelog updates to the Dart 2 version.**
+
+1. **Merge the Dart 1 release first and publish it to pub.**
+
+1. Merge the Dart 2 release second and publish it to pub.
+
+1. Re-recreate the Dart 1 release in MARV (it does not get recreated
+ automatically like the default release does).
diff --git a/README.md b/README.md
index 51f3e0afc..74d8805d3 100644
--- a/README.md
+++ b/README.md
@@ -6,7 +6,6 @@
[![Build Status](https://travis-ci.org/Workiva/over_react.svg?branch=master)](https://travis-ci.org/Workiva/over_react)
[![Test Coverage](https://codecov.io/github/Workiva/over_react/coverage.svg?branch=master)](https://codecov.io/github/Workiva/over_react?branch=master)
-[![Strong Mode Compliant](https://img.shields.io/badge/strong_mode-on-brightgreen.svg)](https://github.com/Workiva/over_react/blob/master/analysis_options.yaml#L5)
> A library for building statically-typed React UI components using Dart.
@@ -15,7 +14,7 @@
> **Dart 2 Migration Guide**
>
> If you have existing over_react code written on Dart 1 and want to upgrade to
-> Dart 2, please read the [**Dart 2 Migration Guide**](/doc/dart2_migration.md)
+> Dart 2, please read the [**Dart 2 Migration Guide**](https://github.com/Workiva/over_react/blob/master/doc/dart2_migration.md)
---
@@ -51,22 +50,10 @@
```yaml
dependencies:
- over_react: ^1.29.0
+ over_react: ^2.0.0
```
-2. Add the `over_react` [transformer] to your `pubspec.yaml`.
-
- ```yaml
- transformers:
- - over_react
- # Reminder: dart2js should come after any other transformers that touch Dart code
- - $dart2js
- ```
-
- _Our transformer uses code generation to wire up the different pieces of your
- component declarations - and to create typed getters/setters for `props` and `state`._
-
-3. Include the native JavaScript `react` and `react_dom` libraries in your app’s `index.html` file,
+2. Include the native JavaScript `react` and `react_dom` libraries in your app’s `index.html` file,
and add an HTML element with a unique identifier where you’ll mount your OverReact UI component(s).
```html
@@ -81,8 +68,8 @@ and add an HTML element with a unique identifier where you’ll mount your OverR
-
-
+
+