RailFrog CMS

• About
• Download
• Chronicle
• Pond
• Wiki

“Culture change—that big elusive goal—often starts with a single, small WOW! project.”

—Tom Peters

What is Rails?

Rails is a full-stack, open-source web framework in Ruby for writing real-world applications with joy and less code than most frameworks spend doing XML sit-ups.

So What’s a
Rail Frog?

Railroad frogs are the sections of railroad track that guide rail car wheels from one track to the other.

While the Railroad/Rails analogy doesn’t hold up perfectly, the name was short, memorable and unique, the domain name was available... and we like frogs!

Hosting for RailFrog has been generously donated by and

Version control and software project management provided by CVSDude

A modest proposal

I’m endeavoring to help jumpstart the development of an open-source CMS application, built using Ruby on Rails, that will will empower writers, editors, publishers, designers, developers, and site owners with the ability to make their websites work for them. Named RailFrog, this application will endeavor to be what Tom Peters calls a WOW! Project and help the Rails framework and community more quickly reach its “tipping point.”

It is my desire to get this project going and contribute in any appropriate way. I’m coming from a designer/developer’s perspective and I hope the Rails community and those already working on Rails CMS applications can benefit from this fledgling, but sincere effort. Let me know if you’d like to help with (or even lead) this effort.

What will RailFrog be?

Fulfilling Jeffery Veen’s CMS wishlist wouldn’t be a bad place to start. Here’s an adaptation of that list:

1. It will be easy to install.
2. It will be easy to get started.
3. It will be powerful, flexible and won’t impose any content or structural preconceptions on the designer/developer.
4. It will be easy to build a site that end users will never know (either visually or structurally) is powered by RailFrog (unless you want them to).
5. It will feature task-based tutorials (created first) backed up by comprehensive feature documentation.
6. It will make clear distinctions between the interfaces for content management users (writers, editors, publishers) and site development users (designers, developers, owners).
7. It will implement web user interface improvements using Ajax.
8. It will produce well-structured and standards compliant pages.

Short-Term Goals:

1. Develop this website to function as a full communication vehicle (ala rubyonrails.com)
2. Attract participants and organize interested people
3. Begin to clarify project scope and goals
4. Develop to the point where RailFrog.com becomes the first RailFrog site
5. Deploy beta version to users for feedback and testing

What is needed?

An organized effort made up of passionate, capable people is needed from the likes of:

1. Developers experienced with open-source projects (I’m not)
2. Ruby on Rails programmers (I’m not)
3. Web Designers and Developers
4. People with web-based CMS application experience
5. Anyone who believes they can contribute in a meaningful way

Why me, why now?

I am not a programmer, but I am a designer/developer (among other things). I think something great like RailFrog will only come about from the efforts of a cooperative team of programmers, developers, designers coming together to create something they can all be proud of. I’d like to be a part of such a team.

I believe that Rails is the best framework for such an effort and that the convergence of people, technology and events, is happening to make this an ideal time for this type of open-source effort.

Currently, I’m one of the stewards of a niche media company and I represent (what I believe is) the core target user of RailFrog. I wear many hats throughout the day (businessman, designer, videographer, web developer, editor, writer, publisher, etc.) and have been desparately looking for, and been frustrated in my efforts to find, a CMS that makes me smile (TextPattern has come closest). I want a solution that will help me create sites that support our efforts, without having to get deeply mired in all the intricacies of deployment, structure and all other complexities involved. I don’t believe a great solution exists yet.

I want to help create just such a solution.

Acknowledgements

• Although I’m a fairly early adopter in the Rails community (bought the beta-combo book, support via TextDrive, Rails List subscriber, etc.), there are those out there who are already well underway in their own Rails CMS development and adventures. For all of you: thanks, and I hope we can somehow consolidate efforts to make a great app (even if RailFrog falls by the wayside in favor of something better.)
• David Heinemeier Hansson for conceiving, coding and evangelizing Rails.
• Jason Fried and all the guys at 37 Signals for making some insanely great stuff (and for graciously putting up with my early support requests.)
• Jakob Lange Skjerning; apologies for ripping off your clean, excellent Ruby on Rails site design. I did it for initial momentum building sake and will change it if it’s inappropriate.
• My good friend, and fellow designer Ron Frank for knocking out a great frog cartoon in a few hours for me; based only on the instructions “how about a happy, satisfied frog, sitting on railroad tracks?”
• Jason Watkins for starting the Ruby on Rails CMS Wiki

Let’s Get the Ball Rolling

My motivation is to get the ball rolling. I’ve got a (more than) full-time work load already, a family of six to nurture, and various other time commitments; but I’m willing to spend time, energy and resources to help see this project develop. Let me know if you’d like to be involved.