Asset Management for Rails

Turn your Rails actions/views into PDFs without a web browser

Peaberry is a clone of dotjs server(djsd) which can serve CoffeeScript(s).

Penguin is a tool for creating presentations.

Continous integration solution compatible with travis.ci

Rack server for rendering javascript apps for bots

Component based static site builder

Pinkman: a new way to orchestrate javascript in Rails.

Amazing libraries for developing games. Defines the main PixieEngine GameObject and includes mixins to easily augment their behavior.

Pollypost provides an interface for managing static sites via a webbrowser. Browser based inline editing is made possible by connecting editing tools to a compatible backend (e.g. nanoc-polly).

A tool to run a set of tasks after deploys

The sprockets-rails2 gem allows Rails 2.3 apps to use the same asset pipeline functionality introduced in Rails 3.1. It does this by integrating the Sprockets gem into a Rails 2.3 app

Pubba is a library designed to help you manage the static components of your site.

A gem to document components in Publishing Platform frontend applications

Customizable web interface for PulseMeter gem

Yahoo's purecss ported to SASS

CanvasOauth is a mountable engine for handling the oauth workflow with canvas and making api calls from your rails app.

Quby is a Rails engine that can render and update answers for questionnaires defined in a custom DSL.

Rack::Sprocketize is a piece of Rack Middleware which uses Sprockets to concatenate javascript files and then optionally compresses them. In a development environment, the files will be sprocketized on each request if there have been changes to the source files. In a production environment, the files will only be sprocketized one time, and only if there have been changes. Also, in a production environment, the files will be compressed by whichever javascript compressor is available.

Use rack middleware to handle sprockets preprocessing. Processing happens on requests to sprockets resources. This allows you to develop, check in, and deploy unprocessed sprockets resources and leave the processing to the middleware. Allows for optimizing by environment: never-cache, always-reprocess in development; cache, process-once in production (for example).