diff --git a/README.md b/README.md
new file mode 100755
index 0000000..419aeac
--- /dev/null
+++ b/README.md
@@ -0,0 +1,97 @@
+Current state of Features for Drupal 8
+--------------------------------------
+
+For Drupal 8, we've rewritten Features from the ground up. 
+If you're coming from a previous version of Drupal, you'll find some great new 
+enhancements but also a familiar user interface for editing features. 
+A beta version of Features 8.x-3.x is available. If you are updating from a 
+previous alpha release, please make sure to read the release notes carefully 
+for updating instructions. If you simply need to export and deploy simple site configuration, 
+the D8 configuration management system should be used instead of Features. 
+You will use Features in D8 to export bundled functionality (like a "photo gallery feature").
+
+Installation
+------------
+Features can be installed like any other Drupal module -- place it in the
+modules directory for your site and enable it on the `admin/modules` page.
+To take full advantage of some of the workflow benefits provided by Features,
+you should install Drush.
+
+REQUIREMENTS
+------------
+ * config (Configuration Manager)
+ * config_update(Configuration Update Manager : https://www.drupal.org/project/config_update)
+
+Basic usage
+-----------
+Features is geared toward usage by developers and site builders. It
+is not intended to be used by the general audience of your Drupal site.
+Features provides tools for accomplishing two important tasks:
+
+### Task 1: Export features
+
+You can build features in Drupal by using site building tools that are supported
+(see a short list under the *Compatibility* section).
+
+Once you've built and configured functionality on a site, you can export it into
+a feature module by using the feature create page at
+`admin/config/development/features/edit`.
+
+### Task 2: Manage features
+
+The features module also provides a way to manage features through a more
+targeted interface than `admin/modules`. The interface at
+`admin/structure/features` shows you only feature modules, and will also inform you
+if any of their components have been overridden. If this is the case, you can
+also re-create features to bring the module code up to date with any changes
+that have occurred in the database.
+
+You can also configure bundles 
+ Use the form (admin/config/development/features/bundle) to manage bundles. 
+ Each bundle comes with a set of assignment methods. 
+ By configuring and ordering the assignment methods, 
+ you can set the defaults for what does and doesn't get packaged into features for your bundle. 
+ Use the Bundle select to choose which bundle to edit, or chose --New-- to create a new bundle. 
+ The Default bundle does not include a namespace and cannot be deleted.
+ Including custom code and adding to your feature
+
+And import the changes you selected into the active configuration through 
+admin/config/development/features/diff.
+
+------------------------------------------------
+Once you've exported your feature you will see that you have several files:
+
+    myfeature.info.yml
+    myfeature.features.yml
+    config (folder)
+
+
+Using Features to manage development
+------------------------------------
+Because Features provides a centralized way to manage exportable components and
+write them to code it can be used during development in conjunction with a
+version control like SVN or git as a way to manage changes between development,
+staging and production sites. An example workflow for a developer using Features
+is to:
+
+1. Make configuration changes to a feature on her local development site.
+2. Update her local feature codebase using `drush features-update`.
+3. Commit those changes using `svn commit`.
+4. Roll out her changes to the development site codebase by running `svn update`
+  on the server. Other collaborating developers can also get her changes with
+  `svn update`.
+5. Reverting any configuration on the staging site to match the updated codebase
+by running `drush features-revert`.
+6. Rinse, repeat.
+
+Security Concerns
+-----------------
+If you are using Features to export Roles and also use those Roles in other
+exportable code (like Views filters) you can wind up with an unintended
+security hole.  When you import your Feature, if the Roles do not get created
+with the exact same Role IDs then your Views filters (or other component) will
+be referencing a different Role than you intended.
+
+For developers
+--------------
+Please read `features_ui` and interface for more information.