Skip to content
Functionality of the bike binder and departed bikes binder
Ruby HTML JavaScript CSS Shell
Find file
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
app
bin
config
db
doc
lib
log
public
script
spec
surveys
vendor
.gitignore
.rspec
Gemfile
Gemfile.lock
Guardfile
MIT-LICENSE
README.markdown
Rakefile
config.ru

README.markdown

BikeBinder for Free Ride

Objective

Reproduce all functionality that exists with the current paper bike binder and departed bikes binder system.

Getting up and running

Afther the first clone

Take the following actions to get a cloned/pulled version to run locally

  • rename "config/database.yml.sample" to "config/database.yml"
  • run "bundle install"
  • run "rake db:populate"

After each time you pull updates

  • Run "bundle install"
  • run "rake db:populate"

Running tests

  • run "rake db:test_setup"
  • "bundle exec guard"

(See http://guides.rubyonrails.org/testing.html#preparing-your-application-for-testing)


Feature Scope

In order to get a functional prototype running, we need to adhere to a limit scope. We can add features later. If a feature is desired, but not in scope, it can be added to the outside scope list.

Scope for Milestone 1

  • Bike info sheet: Location, Characteristic (Size, mfg, model, color), Notes, Value, Departure & Arrival Dates
  • Youth projects sheet: Program name, State (Active/inactive)
  • Bike location tracking: Hook associations to bikes

Complete Features

  • Bike info sheet: Location, Some characteristic, Notes, Departure Dates
  • Youth projects sheet: Program name, State (Active/inactive), Inspection
  • Bike location tracking: Hook associations to bikes
  • Bike state
  • Safety inspection
  • Project progress
  • Youth Project: repair log
  • Hook: hook lookup

Remaining features

  • Bike info sheet: Characteristic (Size, mfg, model, color), Value, Arrival Date

Features for future milestones

  • User permissions
  • Searching & filtering: bikes, hooks, projects
  • Bike demographics (replacing hand-typed characteristics with suggestions or other databased backed data entry)

UI Considerations

While we do not have an official guideline for the UI, I want feedback and suggestions to go here. I will start listing ideas and notes I have about what will keep our interface uncluttered and what will make it intuitive and easy to use.

UI Todos

-standardize visual elements to represent different interactions with the bike binder. eg, a blue underline link represents a Navigational action such as going to the Bikes index page. -rounded buttons represent actions that have to to with creating and editing data eg, The Submit Note, Create New Bike buttons represent instantiating new comment or bike objects -use icons effectively. We want them to help guide the user experience and not act only as eye candy. eg, a blue, underlined anchor may represent an action that manipulates data, so an icon can cue the user of the extra option. See one in use on the single bike overview page. -sensible color scheme. Bootstrap is too minimalist.

Future inspirations

-visual diagrams/photos demonstrating bike measurement jargon? -display the bike color when rendering a bike view

  • bike/freeride branding elements? bike with wings logo faded in background of header on certain pages?

Project Milestones

Mileston 1: Youth project implementation to be fully functional

  • All of the necessary features and interations to be able to successfully user the application for youth projects.

Milestone 2: Searching/Sorting and User roles and authorization

  • UI elements to search the site
  • Ability to sort filter and get basic reports for bikes and projects ** Bike demographic data implemented to assist with searching/sorting/filtering
  • Mechanism implemented to provide user roles
  • Locks in place to require different role based authorization ** Roles and authorization to allow application to go live without risk to data being corrupt

Milestone 3: All project types implemented and fully functional

  • Youth, Earn-a-bike, Fix-for-sale, Scrap, As-is purchases
  • Inspections customized for each project
  • Role based authorization for each project type as needed

Milestone 4: Deployment and support infrastructure

  • Site is live and in-use
  • Infrastructure support for ** Back-ups and restore ** Monitoring & notifying system status ** Admin functionality to fix problems/take care of unexpected issues

Copywrite

(c) 2012 Free Ride Bicycle Project, See license for details

Something went wrong with that request. Please try again.