spinebox

h2. Spinebox

A ready to use spine.js rack skeleton builder with development server, routes, config and precompile support.

• Ideal for single or few page applications
• Fully setup, ready to go spine.js environment
• Develop in coffee-script and sass with fantastic sprockets asset serving
• Use generators and scaffolding just like with rails
• Compile assets and serve the whole app completely static
• Use partials and helpers in your view just like in rails
• Compilation only updates actually changed files. This is a premise for delta deployment.

h3. Installation

bc.. $ gem install spinebox

h3. Usage

Create your javascript app or HTML files just as you're used to it.

h4. Create New Project

bc.. # Create new project an start developing $ spinebox new blog $ cd blog $ spinebox server $ open http://localhost:3000/index.html

h4. Use Partials and Helpers

Partials are prefixed with a @_@ to declare them a partial. So you can create a @_navigation.html.erb@ and use it, e.g. in the @index.html.erb@ with:

bc.. <%= render :partial => "index.html" %>

p. Helpers are in the helper folder and included by default in any view. So if you want to create special links, etc. that you reuse throughout your project simply create a method named @link_to@ in the helper, any any view and partial will have it accessible.

h4. Generate models, views and controllers

bc.. # Generate a model view and a controller $ spinebox generate model post title author body $ spinebox generate controller posts $ spinebox generate view post

h4. Scaffold

bc.. # Or scaffold all three of them $ spinebox generate scaffold post title author body

h4. Compile project

bc.. # Compile project for static serving $ spinebox compile

h3. Contributing

• Fork it
• Create your feature branch (git checkout -b my-new-feature)
• Commit your changes (git commit -am 'Added some feature')
• Push to the branch (git push origin my-new-feature)
• Create new Pull Request