rubyonrailsin

RubyBox--

As the creator Radiant CMS I'll weigh in a little here. :)

Radiant CMS was never intended to meet all of your needs out of the
box. One of the original principles was the 80% window. I wanted to
build a CMS that would work well for 80% of the web sites out there. I
pulled that number out of thin air, but the idea was that most web
sites are content focused -- not weblogs or portals. A lot of content
management systems tend to focus on one of these two domains to their
own detriment. I wanted to build something that gave me infinite
flexibility over how the content was displayed. That allowed me script
simple things like content indexes. Something that gave me the raw
materials to build a blog if needed, but didn't constrain me in any
way.

Since it was initially released most of the work done on Radiant CMS
has gone into making the extension system extremely viable. There have
been very few interface changes or new "features" added to the core
product. As I look back on this, the extension system was a bit of a
stop gap measure so that I wouldn't have to add all of the things that
people wanted me to add. But it has grown into probably the biggest
reason to choose Radiant CMS vs. other Rails-based content management
systems. There are now over 200 extensions in the registry. Show me
another Rails-based system that even comes close to this!

And this is the great strength of Radiant CMS. It is not the core code
base (though there are lots of things that I'm proud of there). It's
the community. The community has come together and created awesome
extensions for asset management, blogging, access control, and version
control -- just to name a few. Because Radiant is small it allows you
to bolt on the stuff that the core doesn't provide.

We have great plans for the future of Radiant. No it's not moving as
fast as we would all like it to, but 0.9 is will be a huge leap
forward and 0.10 will be even better.

So yes you are right, Radiant still has a long way to go, but don't
underestimate the power of the community. I still have my sights set
on Wordpress and some of the other systems out there. Radiant is not
quite ready to compete with them feature for feature, but it will be.
And we need the support of people within the community to make that
happen. You could be one of those folks if you stick around.

As to the "best CMS for Ruby" jab, I'll leave that for other folks to
judge. If Refinery suits your needs better, enjoy it.

--
John Long
http://wiseheartdesign.com
http://recursivecreative.com

On Tue, Mar 16, 2010 at 5:15 AM, rubybox <voorruby@gmail.com> wrote:
> If you just look at
>
> http://demo.refinerycms.com/
>
> You see they have lots of usability out of the box, where Radiant is a
> do-it-yourself
> Its really lacking essential features like a theme feature, things
> like (page order) drag and drop,
> a solid multi_site implementation as part of the core and other
> lacking features.
>
> For example see
> http://github.com/resolve/refinerycms/blob/master/vendor/plugins/themes/themes.md
>
> In my opinion after coming across this today and really looking into
> it ( saw it before but just quickly passed by )
> Radiant cannot no longer deserve the "state of the art" ruby on rails
> cms, that title definitly goes to
> Refinery, untill radiant gets improved and there is some serious
> activity on the github repro. Multisites is incoperated and the
> many issues from issuelist are solved. I know harsh words but Im not
> upto it yet, else I would.
>
> If refinery have/has multi_site I would definitly choose it over
> radiant untill I can build my own CMS based on radius.
> Any ideas?
>
> --
> Radiant CMS Dev Mailing List
> Post:        radiantcms-dev@googlegroups.com
> Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
> Group Site:  http://groups.google.com/group/radiantcms-dev/

--
Radiant CMS Dev Mailing List
Post: radiantcms-dev@googlegroups.com
Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
Group Site: http://groups.google.com/group/radiantcms-dev/