starts to create the test files

it's needed to have files that are not all min'd out and can be used for
tests, more so for javascript work.   This html file will be the start
of it.
test info for the test page
notes for the test page
removes the meta version of the contact RichData

This block was not going to work, here is the test output of the old
block.
http://www.google.com/webmasters/tools/richsnippets?q=https%3A%2F%2Fraw.github.com%2FjeremyBass%2FWSU-spine%2Fmaster%2Fspine.html
and the current block,
http://www.google.com/webmasters/tools/richsnippets?q=https%3A%2F%2Fraw.github.com%2FjeremyBass%2FWSU-spine%2Fmaster%2Ftest%2Ftest.html
.  Also there are comments in the html above the new corrected example
block.. This block is only an example as the attributes are what we will
be drawing for the look up as we do the html generation in javascript
for the contact tab.
switch to the span for the logo for zero content

note per the white papers on google and bing the data can't be on hidden
html, so the css should throw it off the viewport.  Also better comment
above sample block
starts to abstract out the auto complete

We shouldn't have the controller mixed in with the plugins so directly.
moves the auto complete to it's own file

This apart of moving all plugin parts out of the controller file
adds preprocess to grunt

previous builds were including a function that is meant only for
debugging
sets up the initial file for the spine plugin
the general jquery pattern that will be used

I'm going to test a few more just to be sure but this is the pattern i
believe will let us be the most flexible later on
sets the test page to point at the build js
adds a debug script to the build
removes the debug from the controller file
Adds call to the spine plugin in the controller
lets us keep the selector option open

this is for future use
adds the debug to the build

also setting it to debug for the dev cycle, but will be released later.
A test folder would be the solution
relocates the search setup to the plugin
sets up the option patterns desired to be used
set up a basic outline of the options needed
adds prototype generation