addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrosseditemptyheartexportfacebookfolderfullheartglobegmailgoogleimageimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

Re: [ruby-75] Ruby CMSs-- which to choose?

From: Matthew J.
Sent on: Sunday, July 26, 2009 12:12 PM
I've reviewed the open CMS offerings for rails
the current offerings for CMS solutions in Ruby all have weaknesses of
integration, flexibility, and or styling. Depending on your core
business offering you may need to spend enough time and effort coding
to accommodate a CMS solution that it would be best to choose the best
of breed components that comprise a CMS and assemble a lightweight

That said we will most likely have a lively discussion about this at
the upcoming meetup this week. I'm sure you will hear all the good and
bad points from the group then.


On Sun, Jul 26, 2009 at 10:50 AM, Beverly May<[address removed]> wrote:
> Hello Ruby NYC lists,
> I just joined both the NYC Ruby lists as my team is developing a RoR based
> web service this summer. We need to choose a (free) CMS to integrate with
> the platform. We've been reviewing our options based on what seem to be the
> major ones-- Radiant, Mephisto, Typo, Comatose, Railfrog-- but would be
> great to hear from real, live, local developers about pros/cons/warnings
> with any of these and which are most recommended.
> Some details about our service and our cms needs:
> -- Ruby user login and authentication integration
> -- in addition to our core generic service, we will be doing customized
> branded instances/ CSS skins for each new institutional client we receive.
> Each one will need some of their own content... to be powered by the CMS--
> pulling in custom CSS per instance
> -- "editorial" blogs and CMS content pages as well as multi-author
> registered user blog/tip/FAQ/message­ board capability
> -- registered user ratings/reviews on some content
> -- ideal if has newsletter, xml sitemap, ad-serving and other useful
> widgets/ modules readily available from a dev user community?
> Thoughts? Thanks in advance!
> -- Beverly
> --
> Please Note: If you hit "REPLY", your message will be sent to everyone on
> this mailing list ([address removed])
> This message was sent by Beverly May ([address removed]) from NYC.rb - Ruby
> & Ruby on Rails Meetup.
> To learn more about Beverly May, visit his/her member profile
> To unsubscribe or to update your mailing list settings, click here
> Meetup Support: [address removed]
> 632 Broadway, New York, NY 10012 USA

Matthew Jording
[address removed]

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy