A library of cucumber step definitions, which allow you to use a human to assert conditions during acceptance tests. Some requirements are simple for a human to confirm, but are very difficult to assert using automation. Farmer allows us to include human confirmation into our normal testing flow. For example, we needed to verify that certain portions of an image were 'blacked out'.

Nondestructive cucumber testing without using the rails stack setup for Hudson/Jenkins integration

Columbia-specific Fedora libraries

ruby based tools for developing javascript libraries

Picks up where Rails current_page? helper leaves off

A Hash with indifferent access and CouchDB persistence layer

makes the error callbacks on your rails forms a bit prettier when you are using the bootstrap css

This plugin allows you to omit the attribute name for specific messages. All you have to do is begin the message with a '^' character.

Plugin to generate SASS on the fly instead of before each request.

Based pn Lucene implementation

Daftos is a server running HTML5 application, providing them your local filesystem via API.

Reporting application

This gem implements pure Levenshtein algorithm, Damerau modification (where 2 character transposition counts as 1 edit distance). It also includes Boehmer & Rees 2008 modification, to handle transposition in blocks with more than 2 characters (Boehmer & Rees 2008).

This gem implements pure Levenshtein algorithm, Damerau modification (where 2 character transposition counts as 1 edit distance). It also includes Boehmer & Rees 2008 modification, to handle transposition in blocks with more than 2 characters (Boehmer & Rees 2008).

A simple client library to remotely access the Sailthru REST API. Updated with latest git master.

Trying out jeweler to make a gem for the first time.

A simple framework for creating sites from 3rd party data and services

Gem for finding and listing ISO codes for countries, currencies and languages

Expands sinatra with standard helpers and tools to allow for complex applications

**Non Functional / Still in Planning Stage** Here's the high-level (brain dump): * Site content is organized in collections * Collections are serialized * Each have support for next, previous, first, last, etc * The content files are HTML * Templates are object based (each content type can be rendered with their own templates) * Templates are HTML with interspersed Liquid markup * All meta data is described using HTML meta tags * You custom meta data tags in a content objects * You can specify 'prototype' content objects in a collection with a _proto folder in the collection