I have been getting into Radiant, and its a pretty good option if
you're a Ruby developer
and your clients just need a simple admin interface to edit a brochure
site, but with the
massive customisation ability that Ruby tends to provide. Its also
highly efficient as
content is cached and served statically eg. by Apache, not Rails.
Radiant is deliberately
bare-bones; without plugins there is no WYSIWYG editor (I chose the
FCKEditor plugin), and
you can't even rearrange content in the sitemap. Also checkout the
Chronicle plugin for
workflow and versioning.

However I just discovered BrowserCMS, and I reckon its a pretty big
deal for the
Ruby/Rails world. This is a commercially-backed product still selling
for $20K in Java,
being Open Sourced and rewritten in Rails. Even though its only left
beta this week,
its already way ahead of Radiant. Regarding browser versions, they
only apply to the backend
(the front end is up to you), and they acknowledge the backend issues
with Safari,
and are to be addressing that in the next release.

BrowserCMS seems to have most of the positives of Radiant plus
FCKEditor builtin,
workflow, user permissions, drag and drop sitemap rearranging, inline
editing and
a very slick looking admin interface (though not so obvious to use).
Being Ruby, I would expect all sorts of extensions to appear.

I have no connection with them, I'm just glad to see this almost-void
in the Ruby
ecosystem filled with a serious looking product.

p.s. for anyone trying the demo of BrowserCMS, they seem to have
forgotten to set the template
of the home page correctly. Set it to the Home Page template, and
things make a lot more sense.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/rails-oceania?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to