This is not intended as a flame or to cause controversy, please don’t
take it as such.
I just recommended a customer to adopt Typo3 instead of Radiant CMS,
- Mailer Behaviour is shaky at best.
- Print page to PDF/PS/CSV is not even completely supported by Rails.
- User roles.
Those were three of the most important things that they told me they
needed. They’re a small-ish (~15 people) company and are not planning
in having huge traffic on their site or anything. However, I had to
recommend the adoption of a CMS that is probably an overkill for what
they need, but with Radiant and its extensions being in such a
“puerile” stage, it’s too much risk telling them to adopt it.
The point I’m trying to drive home is that all of us that are in some
way or another involved in the development of Radiant (whether the
core, extensions, documentation, etc.) need to ramp up development of
Radiant if we really want to make it a production-grade CMS. I believe
for what I’ve read as of late that a whole lot of people is interested
in helping out and I sense the time is ripe for John and whoever else
leads Radiant to “manage” the momentum built up to help get this baby
out the door.
Sorry for soapboxing, but in closing I must echo the thoughts of a
list contributor who said something to the effect that if a project
stagnates for too long, it eventually fades away.