WIP, initial summary and readme text. Borrowing from the rules doc for contributing section, still needs edits

Author: Josh Miller

.gitignore

@@ -13,4 +13,6 @@ _book
 # eBook build output
 *.epub
 *.mobi
-*.pdf
+*.pdf
+
+.DS_Store

README.md

@@ -1,11 +1,15 @@
-# Drupal Commerce Documentation
+# Drupal Commerce 2.x Documentation
 
 This documentation is rendered online at http://docs.drupalcommerce.org
 
 ## Contribute
 
 We love contributors! Please help us improve or fix the documentation by opening Pull Request. Each Pull Request is automatically built by [Platform.sh](https://platform.sh).
 
+If you have trouble understanding any part of the documentation, please notify those of us who work on this section by creating an issue on our [Drupal Commerce 2.x documentation repository](https://github.com/commercegus/commerce-docs) and clearly explain what you don't understand and why - we're happy to hear from you, your contribution helps everyone at Drupal!
+
+You can also contribute directly on our [Drupal Commerce 2.x documentation repository](https://github.com/commerceguys/commerce-docs) by editing the files through the [GitHub](https://github.com/) interface directly in your browser. Alternatively, you can clone the repository and edit the book in your favorite text editor or in the official [GitBook desktop app](https://github.com/GitbookIO/editor).
+
 ## Hosting
 
 This site is hosted on [Platform.sh](https://platform.sh).

SUMMARY.md

@@ -1,3 +1,19 @@
 # Summary
 
-* [First Chapter](chapter1.md)
+* [Introduction](README.md)
+* [Commerce 1.x](commerce-1/README.md)
+* [Commerce 2.x](commerce-2/README.md)
+  * [Contributing](commerce-2/contributing/README.md)
+    * [Setting up the environment](commerce-2/contributing/environment.md)
+    * [Executing the automated tests](commerce-2/contributing/testing.md)
+    * [Developing](commerce-2/contributing/start_developing.md)
+  * [Installing](commerce-2/install/README.md)
+  * [Dependencies](commerce-2/dependencies/README.md)
+    * [Address](commerce-2/dependencies/address/README.md)
+      * [Zones](commerce-2/dependencies/address/zones.md)
+    * [Profile](commerce-2/dependencies/profile.md)
+    * [Inline Entity Form](commerce-2/dependencies/ief.md)
+  * [Currency](commerce-2/currency/README.md)
+  * [Store](commerce-2/store/README.md)
+  * [Product](commerce-2/product/README.md)
+  

book.json

@@ -0,0 +1,9 @@
+{
+    "name": "Drupal Commerce 2.x Documentation",
+    "version": "0.0.1",
+    "description": "Drupal Commerce is an open source eCommerce framework that is designed to enable flexible eCommerce for websites and applications based on Drupal.",
+    "repository": {
+        "type": "git",
+        "url": "https://github.com/commerceguys/commerce-docs"
+    }
+}

chapter1.md

@@ -0,0 +1,8 @@
+# Contributing
+
+For some time development will happen on GitHub and will be using the pull
+request model: In case you are not familiar with that, please take a few minutes
+to read the [GitHub article](https://help.github.com/articles/using-pull-requests)
+about that topic.
+
+Please take a moment to read the [Development Guide](start_developing.md) to learn about the process and the conventions used in this project.

commerce-2/contributing/README.md

@@ -0,0 +1,58 @@
+# Setting up the environment
+
+### LAMP
+
+The very first step for starting contributing to Drupal Commerce is to setup a classic
+"LAMP" environment: that's a bit out of the scope of this document, so please
+take a look at [Drupal Installation Guide](https://drupal.org/documentation/install)
+and especially at its [System requirements section](https://drupal.org/requirements).
+
+### Drush
+
+Installing the powerful Drupal Shell is not mandatory but it can definitely be helpful during development. The recommended way to install it is through composer. Unfortunately, due to a (temporary?) dependency-clash between Drupal 8 and Drush 7, it's not possible to just install it within your Drupal 8's vendors directory.
+So fire the following in your terminal:
+
+    composer global require drush/drush=dev-master
+
+### Drupal 8
+
+Once you've got your system ready to host Drupal 8, the next step is to go and
+clone its repository in the directory where your web server will expect it to be
+by using the following command, being careful to replace "MINOR_VERSION" and "DESTINATION_DIRECTORY" as needed:
+
+    git clone --branch 8.MINOR_VERSION.x http://git.drupal.org/project/drupal.git DESTINATION_DIRECTORY
+
+Please look at the [Drupal Git Instructions](https://drupal.org/project/drupal/git-instructions)
+for more information about how to clone Drupal.
+
+Once you finished cloning Drupal, set up a database for it and proceed with the
+installation: after it's completed, the only thing's missing is the Drupal Commerce
+module.
+
+### Drupal Commerce 2.x
+
+#### NOTE: you will need a working GitHub account for contributing.
+
+In order to start working on Drupal Commerce 2.x, you have to visit its
+[module page on GitHub](https://github.com/commerceguys/commerce) and click the **fork**
+button.
+
+![Forking Drupal Commerce repository](images/original-repository.jpg)
+
+That will create a copy of the Drupal Commerce repository on your GitHub account. At this
+point you're ready to clone it in your working environment in a directory of your choice by using the following command (don't forget to replace YOUR_USER with
+the name of your GitHub user):
+
+    git clone [email protected]:YOUR_USER/commerce.git
+
+Once you did all of that, symlink the cloned commerce directory under the Drupal's ``modules``
+directory.
+
+**NOTE: directly cloning Drupal Commerce within Drupal's ``modules`` directory is discouraged for development.**
+
+![Drupal 8 modules page](images/forked-repository.jpg)
+
+The only thing left to do now is to head to the module page clicking on the
+**Extend** button in the top menu and enable Drupal Commerce.
+
+![Drupal 8 modules page](images/enable-module.jpg)

commerce-2/contributing/environment.md

@@ -0,0 +1,46 @@
+# Developing
+
+Once you verified everything's working properly by [running the tests](testing.md), you're ready to go!
+
+
+### Taking a look at the issue queue
+
+While the coding is done on github, the issue queue is still taken care of on drupal.org: you can take a look at [the open issues](https://www.drupal.org/project/issues/search/rules?assigned=&submitted=&project_issue_followers=&status[0]=Open&version[0]=8.x&issue_tags_op=%3D&issue_tags=&text=&&&&order=field_issue_priority&sort=desc
+), pick one you like and **assign it to you**.
+
+### Coding and Pull Request-ing
+
+Remember to create a branch before start developing! It's name should contain the issue id and a slug to tell what the thing you're working on is about, for example: **2276369-readme**.
+
+Once you're done with the development, push your commits and [create a Pull Request](https://help.github.com/articles/using-pull-requests#initiating-the-pull-request) on github.
+
+After your code has been reviewed, you might be asked to perform some changes and then have them reviewed again. After a number of iterations, you should get your code merged into the main repository. Hurray!
+
+### Keeping your fork up to date
+
+After some time your forked repository and the original one(called *upstream*) will eventually get out of sync leaving you with an old, unsupported version. In order to keep that up to date, you'll need to *fetch* (i.e: downloading without touching the code on your computer) the latest commits and then *merge* them in the branch you need, which most likely will be **8.x-3.x**. So enter your Rules module's directory and type:
+
+    git remote add upstream [email protected]:fago/rules.git
+
+
+This command will add the original Rules' repository reference to your local repository(you don't have to repeat it all the time, just the first one will do).
+Then you can proceed with the download and merge on the wanted branch:
+
+    git fetch upstream
+    git checkout 8.x-3.x
+    git merge upstream/8.x-3.x
+
+And that's it! Your repository is up to date again so that you can start developing a new feature right away! Please check [Github's guide on how to sync a fork](https://help.github.com/articles/syncing-a-fork) for more information
+
+### Keep the conventions in mind
+
+* Always create an issue in the [drupal.org Rules issue queue](http://drupal.org/project/issues/rules)
+  for every pull request you are working on.
+* Always cross-reference the Issue in the Pull Request and the Pull Request in
+  the Issue.
+* Always create a new branch for every pull request: its name should contain a
+  brief summary of the ticket and its issue id, e.g **2276369-readme**.
+* Try to keep the history of your pull request as clean as possible by squashing
+  your commits: you can look at the [Symfony documentation](http://symfony.com/doc/current/cmf/contributing/commits.html)
+  or at the [Git book](http://git-scm.com/book/en/Git-Tools-Rewriting-History#Changing-Multiple-Commit-Messages)
+  for more information on how to do that.

commerce-2/contributing/images/enable-module.jpg

@@ -0,0 +1,22 @@
+# Executing the automated tests
+
+This module comes with PHPUnit and SimpleTest tests. You need a working Drupal 8
+installation and a checkout of the Rules module in the modules folder.
+
+#### PHPUnit
+
+    ./core/vendor/phpunit/phpunit/phpunit -c ./core/phpunit.xml.dist ./modules/rules
+
+#### Simpletest
+
+Make sure simpletest is enabled:
+
+    drush en -y simpletest rules
+
+And then run the tests
+
+    drush test-run 'Rules, Rules conditions'
+
+    php ./core/scripts/run-tests.sh --verbose --color "rules"
+
+You can also execute the test cases from the web interface at ``/admin/config/development/testing``.