Update README.md

Author: joshribakoff

README.md

@@ -3,7 +3,7 @@
 
 Metator
 =======
-A unit tested shopping cart. Check out the [demo site](http://demo.metator.com/).
+[A unit tested shopping cart](http://metator.com). Check out the [demo site](http://demo.metator.com/).
 
 #Install
 ````
@@ -24,27 +24,5 @@ All Done. Took 33.8217s
 ````
 Anything non numeric in the number flag is stripped. Run `./metator` without flags for comprehensive usage information.
 
-#About
-
-###Why yet another open source shopping cart?###
-There is a need for online retailers to sell complex products in today's marketplace. Configurable products that come in different colors & sizes like a T-Shirt, and groups of these configurable products like a product representing a T-Shirt & Pants sold together.
-
-Existing solutions for this like Magento lack the ability to import this complex data, and are hard to modify beyond it's cookie cutter functionality.
-
-Metator aims to utilize unit testing with a philosophy that import/export comes before GUI, with an emphasis on providing command line utilities for common operations.
-
-###Why the emphasis on Import?###
-Existing solutions like Magento provide great features that aren't supported by their import/export. You can have multiple images per product in Magento, but there's no way to import or export them. You can add configurable options like "color" & "size", but only if you do so by hand one product at a time.
-
-This point & click style of setting up the store is fine for smaller stores, but when there are large amounts of products to be loaded it poses multiple problems. First, is the cost of "man hours" to input the data, secondly the nature of humans is to make mistakes. When data accuracy is of upmost importance, store owners would rather rely on the computer to import their data quickly & accurately.
-
-###Performance###
-An emphasis will be placed upon performance. Page load times, importing, & exporting will be quick, even with large datasets. The goal is 1/4 second per page load & 1k products per second import/export.
-
-Even if you are just using simple products, Magento takes 1-2 seconds per product to import. If you have 1 Million products that need to have their prices updated every week, you couldn't do it in Magento because it would take ~12 days to finish an import!
-
-###What about export?###
-That is important too. If you imported it, you need to be able to export it. An export from within the application should be a substitute for backing up the database. If you export all data from within the app, then delete your database, importing it back in should restore you to a working state with no data loss. Exports & backups should be synonymous.
-
 #Performance Tuning
-It dumps user uploaded images for products into `./data/images`. By default, this is served through the front controller, but I've symlinked it from `./public/images` so that we're not involving PHP to serve these images, I just let the web server handle the caching & serving of these images. Ensure your server is set to follow symlinks for the `./public` directory to get this speed boost.
+There is a symlink from `./public/images` to `./data/images`. The application works without this, but configure your server to follow symlinks for a performance boost.