The radiant-code-extension didn’t seem to work for me. Kept giving me an “Invalid id = ’’ given” error. I’ve abandoned it and forked the radiant-code_ray-extension. It seems to work well and the coderay highlight library seems, in my quick research, to be the easiest to setup and most useable library.
Posted on Dec 11, 2010
So my first Radiant CMS site is for my feature-length documentary film BLAZE FOLEY: DUCT TAPE MESSIAH.
Here’s a list of extensions that look like a promising fit for the site and what I want it to do.
Posted on Dec 13, 2010
An extension README will sometimes say you can configure it, but it’s not clear in which you’re supposed to put the configuration settings.
For example, in Alexey Noskov’s radiant-code-extension code syntax highlighting extension, the README says you can specify your preferred code processor in the code.processor setting. This is typical shorthand and one of the things that makes Radiant a bit difficult to approach for a new user.
Posted on Dec 11, 2010
I’ve successfully set up two Radiant v0.9.1 sites now and need to document what I did so that I can remember all this when I go to create another couple of Radiant sites.
All this stuff may be old by the time you read it, so take into account the date of this post and the Radiant version I’m working with (v0.9). If you’re reading this and you notice an error, please email me and request that I make a correction (I’ll try to add a comment extension to this site).
Also, keep in mind that this post is more for me to remember what I did than to be used as a cut and paste recipe for setting up a new site. We all have our own working environment. But maybe this will help someone else to figure out what has to happen to create and deploy an initial site.
Posted on Dec 04, 2010