Radiant is alive!
It's sad, of course, that I have to insist that.
There's a lot of history in Radiant. Much of what Rails can now do
with engines could not be done when support for extensions were
created. This project was a pioneer for that stuff, but it wasn't kept
up to date with changes.
To
Yes, I do think better documentation is definitely a really, really, good idea.
The ruby CMS war is only between Refinery CMS and Radiant CMS. I've used both,
and I feel that Radiant is the better CMS, especially in terms of the interface
and the intuitive way you can utilise ruby code in the si
There's about 4 people on the irc, the project on github has build errors
and its dependancies are out of date, the last update of your average
extension is around *three years ago*, whenever I run the server I'm
greeted with dozens of warnings about insecure protocols and the like.
What's goin
