Revert "Add initial gradient support."

This reverts commit 0e276143b18922cd329e8f3a61416d87baf96f02.
Cleaning up the master branch since we will be developing on 'dev' branch. This
was an accidental push that should have been on the dev branch.
Revert "Fix gulp watch error."

This reverts commit 60114efdf708fd927092d442b8d9f789ac9b44c3.
Cleaning up the master branch since we will be developing on 'dev' branch. This
was an accidental push that should have been on the dev branch.
Revert "Revert "Fix gulp watch error.""

This reverts commit 15c4a211f3df50f706aa42e1cbe2beeab18189d8.

This is admitedly a mess now, but git is being stupid (in it's core
functionality). I had commited to master when I should have commited to 'dev'
so I wanted to move those commits to a new branch. I reverted the commits on
master (creating two new commits in the process), which of course meant that the
reversal of my initial changes were now the latest record. I only wanted to
change master to remove those commits, but in doing so I move the index forward
and now I must move the index forward even further on the dev branch so that it
can be merged into master later.

The lesson: don't push until your sure.
Revert "Revert "Add initial gradient support.""

This reverts commit 351b02a4dff745ac7b12117b49aa441df005a04e.

See last commit for explanation.