Radiant on Crack is my experimental branch of the Radiant CMS project.
I’ve been making experimenting with a few things that need some fairly
fundamental changes to the underlying codebase of radiant, and my
immediate needs are somewhat different to those of the core developers.
The primary goal of what I’m doing here is to make Radiant powerful
enough to run The Groggy Squirrel http://www.thegroggysquirrel.com ,
which is currently powered by a hand-rolled and very unfriendly cms-like
I’m hoping to have implemented within the couple of weeks: Images,
Attachments, Comments and some other goodies.
Before you ask, this is not a political fork of the project, it’s a
practical one. I’m extending the capabilities of Radiant in ways that
are going to break things, but in ways that I need it to change. I need
to track my changes anyway, so I might as well do it publicly rather
than turn up in 2 months time with a pile of patches.
I look forward to most of my changes working their way into core in some
way, shape or form - probably with a better implementation than I can
come up with. I’m happy for others to cherry-pick changes from R.O.C.
and patch them into core, or to ask for my help to do so.
- I Do Not Recommend Running Radiant On Crack on your live site *
I’ve given it a stupid name for a good reason. I don’t want anybody
basing their livelihood on it. I will have no qualms about ripping out
implementations and completely reworking things in a possibly backward
incompatibly manner. Unless you’re willing and able to dive into both
ruby and sql to hack it about to fix it and make it work, don’t use it.
Consider yourself warned.