Bootstrap Theme

README.md

@@ -11,6 +11,12 @@ gem 'radius-rails', github: "RadiusNetworks/radius-rails"
 
 ```
 
+Note: If the app you are using doesn't use the updated Twitter Bootstrap Theme, then you will want to use the tag `v0.1.0`:
+
+```ruby
+gem 'radius-rails', github: "RadiusNetworks/radius-rails", tag: "v0.1.0"
+```
+
 ## Usage
 
 This will give you access to the common Radius Networks assets needed in most web apps.
@@ -20,10 +26,8 @@ This will give you access to the common Radius Networks assets needed in most we
 Stylesheets can be pulled in with the [asset pipeline](http://guides.rubyonrails.org/asset_pipeline.html) or using [Sass](http://sass-lang.com/):
 
 ```scss
-@import "normalize";
-@import "font-awesome";
-@import "bonveno-webfont";
-@import "environment-ribbon";
+@import "radius-theme";
+@import "corporate-bar";
 ```
 
 You can pull in the favicon by adding the image to the header of your layout:
@@ -56,28 +60,9 @@ body
   == render 'radius/environment_ribbon'
 ```
 
-#### Corporate Bar Header
-
-Add the `corporate_bar` partial right after the opening body tag.
-
-```slim
-body
-  == render 'radius/corporate_bar'
-```
-
 #### Google Analytics
 
 ```slim
 == render 'radius/ga'
 ```
 
-#### Zendesk Support Tab
-
-Most of the time you only want this on some views, so you can optionally include it by checking the `controller_name`.
-
-```slim
-- if !(controller_name == "static" && action_name == "index")
-  == render 'radius/zendesk'
-```
-
-

app/assets/components/Chart.js/.bower.json

@@ -0,0 +1,20 @@
+{
+  "name": "Chart.js",
+  "version": "1.0.2",
+  "description": "Simple HTML5 Charts using the canvas element",
+  "homepage": "https://github.com/nnnick/Chart.js",
+  "author": "nnnick",
+  "main": [
+    "Chart.js"
+  ],
+  "dependencies": {},
+  "_release": "1.0.2",
+  "_resolution": {
+    "type": "version",
+    "tag": "v1.0.2",
+    "commit": "930b16a0af59201dcfcd1594b0e7540db4d04c9f"
+  },
+  "_source": "git://github.com/nnnick/Chart.js.git",
+  "_target": "1.0.2",
+  "_originalSource": "Chart.js"
+}

app/assets/components/Chart.js/.travis.yml

@@ -0,0 +1,13 @@
+language: node_js
+node_js:
+  - "0.11"
+  - "0.10"
+
+before_script:
+  - npm install
+
+script:
+  - gulp test
+
+notifications:
+  slack: chartjs:pcfCZR6ugg5TEcaLtmIfQYuA

app/assets/components/Chart.js/CONTRIBUTING.md

@@ -0,0 +1,55 @@
+Contributing to Chart.js
+========================
+
+Contributions to Chart.js are welcome and encouraged, but please have a look through the guidelines in this document before raising an issue, or writing code for the project.
+
+
+Using issues
+------------
+
+The [issue tracker](https://github.com/nnnick/Chart.js/issues) is the preferred channel for reporting bugs, requesting new features and submitting pull requests.
+
+If you're suggesting a new chart type, please take a look at [writing new chart types](https://github.com/nnnick/Chart.js/blob/master/docs/06-Advanced.md#writing-new-chart-types) in the documentation, and some of the [community extensions](https://github.com/nnnick/Chart.js/blob/master/docs/06-Advanced.md#community-extensions) that have been created already.
+
+To keep the library lightweight for everyone, it's unlikely we'll add many more chart types to the core of Chart.js, but issues are a good medium to design and spec out how new chart types could work and look.
+
+Please do not use issues for support requests. For help using Chart.js, please take a look at the [`chartjs`](http://stackoverflow.com/questions/tagged/chartjs) tag on Stack Overflow.
+
+
+Reporting bugs
+--------------
+
+Well structured, detailed bug reports are hugely valuable for the project.
+
+Guidlines for reporting bugs:
+
+ - Check the issue search to see if it has already been reported
+ - Isolate the problem to a simple test case
+ - Provide a demonstration of the problem on [JS Bin](http://jsbin.com) or similar
+
+Please provide any additional details associated with the bug, if it's browser or screen density specific, or only happens with a certain configuration or data.
+
+
+Pull requests
+-------------
+
+Clear, concise pull requests are excellent at continuing the project's community driven growth. But please review [these guidelines](https://github.com/blog/1943-how-to-write-the-perfect-pull-request) and the guidelines below before starting work on the project.
+
+Guidlines:
+
+ - Please create an issue first:
+   - For bugs, we can discuss the fixing approach
+   - For enhancements, we can discuss if it is within the project scope and avoid duplicate effort
+ - Please make changes to the files in [`/src`](https://github.com/nnnick/Chart.js/tree/master/src), not `Chart.js` or `Chart.min.js` in the repo root directory, this avoids merge conflicts
+ - Tabs for indentation, not spaces please
+ - If adding new functionality, please also update the relevant `.md` file in [`/docs`](https://github.com/nnnick/Chart.js/tree/master/docs)
+ - Please make your commits in logical sections with clear commit messages
+
+Joining the Project
+-------------
+ - Active committers and contributors are invited to introduce yourself and request commit access to this project.  Please send an email to hello@nickdownie.com or file an issue. 
+
+License
+-------
+
+By contributing your code, you agree to license your contribution under the [MIT license](https://github.com/nnnick/Chart.js/blob/master/LICENSE.md).