Skip to content
James OKelly edited this page Jun 23, 2011 · 6 revisions

Home

Table of Contents

RubySlippers solved a problem for me. How do I set up blogs quickly using the ruby stack I use every day without taking my time away from the work I have to do?

In the past I used typo, mephisto, enki, and a few more blog engines. It wasn't until I found toto that I knew what I wanted. I didn't want a rails stack. I wanted a simple rack application, and I wanted it fully tested.

Toto had some integration testing but was lacking severely in test coverage, and I focus on unit testing first, which it was missing completely. It was also missing very basic elements like sitemaps, tagging, and search.

I started with a fork, and quickly realized (after looking through their issue log) I didn't want to wait for pull requests to get accepted. So I spent a weekend on a rewrite that modularized everything, and added a grip of unit and functional tests, both for the gem and the blog template.

I will cover the testing and releasing process in detail here.

What is the Goal-Post for a v1?

Deploying a ruby based blog should be easy. Easy as pie. Easy as Stifler's Mom. Easy as a 1 click installer. Writing articles should be equally as easy. Want to add a plugin? That should be easy to.

When your Mom or Dad can install RubySlippers on heroku and write an article we will be 1.0.

Project Management

The whole project is managed on github and you can view the milestones and add your own issues and enhancements.

If you are interested in contributing you can submit a patch WITH tests. I will gladly accept 1-2 devs on the core team.