update the uranium version on the download page

.gitignore

@@ -7,3 +7,4 @@ doc/*.html
 examples/site/_site/*
 .sass-cache/
 
+build/.remote/

CNAME

@@ -1 +1 @@
-uraniumjs.com
+uranium.io

Gemfile

@@ -1,6 +1,7 @@
-source "http://gems.moovweb.org"
+source "http://gems.moovweb.net"
+source "http://rubygems.org"
 
 gem "rake"
 gem "manhattan_uploader", "0.2.24"
 gem "fusion", "0.0.5"
-gem "rdiscount"
+gem "rdiscount"

Gemfile.lock

@@ -1,5 +1,6 @@
 GEM
-  remote: http://gems.moovweb.org/
+  remote: http://gems.moovweb.net/
+  remote: http://rubygems.org/
   specs:
     domain_name (0.5.2)
       unf (~> 0.0.3)

README.md

@@ -1,134 +1,125 @@
-# Overview
+# Uranium
 
-Uranium is meant to be :
+## Overview
+
+Uranium is a simple Javascript interaction library written in jQuery. It's meant to be...
 
 -  Lightweight
--  Easy to use
+-  Declarative
+-  Interface Focused
 
 That's it!
 
-If given the choice between easy to use and powerful, ease of use is the greater goal. If you find yourself wanting something that a given widget will not do, you're encouraged to extend the widget yourself.
+If given the choice between easy to use and powerful, ease of use is the greater goal. 
 
-It should be noted that since Uranium extends xui -- this library is geared for widgets that are useful on mobile devices. It also is designed to support mobile browsers (for now just webkit, but you can build it for blackberry/mobile IE as well).
+View the [website](http://uranium.io/) for more details and demos.
 
-View the [website](http://uraniumjs.com/) for more details and demos.
 
 ---
 
-# Lightweight
-
-**The whole library is 15 KB gzipped (including all widgets and xui) !**
-
--  Uranium is based on [xui](http://xuijs.com/) -- the featherweight mobile js library
--  Uranium is bundled with xui to make just one javascript file(uranium/raw/master/build/src/uranium.js).
--  If you want it even lighter, you can make a custom [build](uranium/blob/master/doc/dev/build.md) yourself. Follow the instructions below.
-
----
-
-# Easy to Use
+## Easy to Use
 
 **Uranium requires ZERO programming on your part.**
 
-Uranium adopts the 'declarative' javascript style. Because of this, you can use the widgets without touching a single line of javascript.
+Uranium adopts the 'declarative' Javascript style. Because of this, you can use the interactions just by editing your HTML and CSS, without touching a single line of Javascript.
 
-**What is declarative javascript?**
+**What is declarative Javascript?**
 
-Declarative javascript is a model that looks for how html elements are formatted to construct all the necessary js magic to make those elements come to life. 
+Declarative Javascript is a model that looks for how html elements are formatted to construct all the necessary js magic to make those elements come to life. 
 
 ---
 
-# Get Started
 
-There are two primary steps to make a widget:
+## Uranium is not ...
+
+**...designed for executing logic or site functions**
 
--  Add special attributes to the html element you wish to make a widget
--  Include [uranium.js](uranium/raw/master/build/src/uranium.js)
+The declarative Javascript in Uranium is not designed for performing functions, but for enabling interactions. It's a bad idea to add attributes to an element to perform some Javascript logic. This is exactly why onclicks should be avoided. If you want to execute site logic or perform functions, that's what events / listeners / callbacks are for. The declarative approach promoted by Uranium makes the view (your UI/UX) rely on the model (your HTML). 
 
-View the [website](http://uraniumjs.com/) for a [tutorial](http://uraniumjs.com/tutorials.html) (we have videos!), more details, and awesome [demos](http://uraniumjs.com/widget_list.html).
+**But I need to do x/y/z functions that Uranium doesn't handle !**
+
+You're in luck! Uranium is designed to work with [jQuery](http://www.jquery.com) – which (we think) provides a great set of convenient Javascript functions along with some very useful cross-browser compatibility features. With this in mind, using Uranium gives you the best of both worlds – its primary purpose is to make it easy to add great interaction – but if you need to do something fancy, it makes sure the tools you need to do so concisely are also available.
 
--  Read our [philosophy](http://uraniumjs.com/more.html) to understand our design goals and see how to implement a widget.
--  Admire all the [widgets](http://uraniumjs.com/widget_list.html) available.
 
 ---
 
-# Uranium is not ...
+## Building Uranium
 
-**... designed for executing logic or site functions**
+If you're contributing to the code base, you need to test your changes and update the bundled Javascript.
 
-Uranium makes the view (your UI/UX) rely on the model (your HTML). The declarative aspect is not designed for performing functions. You wouldn't want to add attributes to an element to perform some js logic (this is exactly why onclicks should be avoided) -- thats what events / listeners / callbacks are for.
+**Bundling**
 
-**But I need to do x/y/z functions that Uranium doesn't handle !**
+Bundling uses [fusion](http://rubygems.org/gems/fusion) to bundle the Javascript. This means you have to install the fusion ruby gem before you can run the build process. To perform the default build from inside your local copy of the Uranium repository, just do:
+
+		gem install fusion
+    cd build
+    rake
+
+This will read in the full Javascript source in the lib/jquery.uranium.js file, and place both full-source and minified copies of Uranium in build/src/.
 
-You're in luck! Uranium bundles with xui -- which (we think) provides a great minimal set of convenient javascript functions (query, add-listeners, ajax, iterate, etc). With this in mind, Uranium is the best of both worlds -- its primary purpose is to make it easy to create great widgets UI/UX -- but if you need to do something fancy, it gives you the tools you need to do so concisely.
+**Testing**
 
+You need to go through all of the test cases in the /examples/index.html file and make sure that all the interactions still work. Of course, if you've added functionality, or a new interaction, you need to make a test example for your new cases as well and make sure those pass. It should be an example file that can be shown on the website.
 
 ---
 
-# Building Uranium
+## Building an Interaction
 
-If you're contributing to the code base, you need to test your changes and update the bundled javascript.
+Fork Uranium. Build your interaction. Issue a Pull Request. Revel in glory.
 
-**Bundling**
+If you're contributing to the code base, you need to test your changes and update the bundled Javascript.
 
-Bundling uses the Google Closure Compiler to bundle the javascript. Don't worry -- part of the rake task is to install if for you! To perform the default build, just do:
+**Technical**
 
-    cd build
-    rake
+TODO: Information on how the code base should be structured, conventions, etc...
 
-This will compile all the widgets with each flavor (BB/IE/webkit) of xui.
+To get the examples running locally, start the jekyll server with:
 
-**Custom Bundling**
+`jekyll serve --watch`
 
-The rake task really just reads the config files (e.g. webkit.yaml) to know how to bundle the javascript. The different versions also have different widget lists to reflect those widgets compatabile with that browser flavor.
+In a separate terminal process, run  
 
-If you want to omit certain widgets or make a custom build, you're welcome to do so locally (and can do so by making your own custom yaml file / build task). This is a great way to only build a smaller version of the specific widgets that you'll need.
+`sass --watch examples/scss:_examples/css --line-comments --compass`
 
-**Testing**
+on the stylesheets folder to compile your Sass files.
 
-You need to go through all of the test cases under /examples and make sure that all the widgets still work. Of course, if you've added functionality or a new widget, you need to make a test example for your new cases as well and make sure those pass. It should be an example file that can be shown on the website.
+You will be able to navigate to [localhost:4000](localhost:4000) to see the examples running in your browser.
 
----
+**Documentation**
 
-# Building a Widget
+You'll need to generate a .html file demonstrating the use of your new interaction. It goes in the examples folder, and should do the following things
 
-Fork Uranium. Build your widget. Issue a Pull Request. Revel in glory.
+* Provide documentation of all the attributes, CSS, and JS required to make the interaction go.
+* At least one example of how the interaction can be used.
 
-If you're contributing to the code base, you need to test your changes and update the bundled javascript.
+**Important Note**
 
-**Technical**
+If there are two versions of jQuery on a page, Uranium will break.  To avoid this, try to only use 1 instance of jQuery. If that is not possible, you will need to use jQuery.noConflict() on both instances.
 
-TODO: Information on how the code base should be structured, conventions, etc...
+---
 
-Start the jekyll server with `jekyll --server --pygments`
+## Future Wishlist
 
-Run `sass --watch stylesheets/sass:stylesheets --line-comments --compass` onteh stylesheets folder to compile your SASS files. 
+Uranium is an ongoing project and we're constantly looking to add useful features (that are within the scope of the ideals above).
 
-**Documentation**
+Additional features to current interactions:
+
+  - *Carousel*: "Stop autoscroll" button 
+  - *Carousel*: Auto-populate clones on infinite scroll when container is larger than actual items
+  - *Geocode*: Entering zipcode should find address
 
-You'll need to generate an .html file that goes in the _site/widgets folder that should do the following things
+New interactions:
 
-* Provide documentation of all the attributes, CSS, and JS required to make the widget go.
-* At least one example of how the widget can be used.
+  - Validation interaction for form inputs
 
 ---
 
-# MIT License
+## MIT License
 
-Copyright (C) 2011 by Moov Corporation (aka Moovweb)
+Copyright (C) 2011-2013 by Moov Corporation (aka Moovweb)
 
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
 
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Rakefile

@@ -49,3 +49,4 @@ task :upload => [:enrich] do
 end
 
 task :default => [:enrich]
+

VERSION

@@ -1 +1 @@
-0.1
+1.0

_config.yml

@@ -1,4 +1,4 @@
-# url: "http://moovweb.github.com/uranium/"
-source: "examples/site"
-destination: "examples/site/_site"
-auto: "true"
+url: "http://moovweb.github.com/uranium/"
+source: "examples/"
+destination: "_examples"
+pygments: true