I know this has been asked before, but I couldn’t find something
directly useful. I was just wondering if someone has written a guide
(it’ll be useful for the documentation project) or if someone could just
point me to the main things I need to use for it. So far, I’ve been
looking at using Radiant for stand-alone CMS like projects, but I want
to now try integrating it with other things that I’m doing.
With Radiant 0.6.7, I believe that some of the current extensions can’t
be used. What are people using? Just a few lines would help me get
started.
I know this has been asked before, but I couldn’t find something directly
useful. I was just wondering if someone has written a guide (it’ll be
useful for the documentation project) or if someone could just point me to
the main things I need to use for it. So far, I’ve been looking at using
Radiant for stand-alone CMS like projects, but I want to now try integrating
it with other things that I’m doing.
With Radiant 0.6.7, I believe that some of the current extensions can’t be
used. What are people using? Just a few lines would help me get started.
All of those extensions work with 0.6.7. http://0.6.7. If you’re
integrating Radiant with another Rails project, the share_layouts
extension is where you’ll start.
Thanks Tim
The list you provided is very useful! I had mean to only ask about what
people are using for “Rails + Radiant” but your reply is a bonus!
So, share_layouts is the way to go. Can I clarify a couple of things?
[1] This would allow me to embed Radiant into a Rails application,
right? So, I could build a site around Rails and then use Radiant to
manage the relatively static content, page caching, layouts,
stylesheets, etc. If so, this might be the perfect thing for one of the
projects I have in mind.
[2] On the other hand, I’m planning to build an information site that
stores manuals, etc. in HTML and lets people add comments, sign up as
users, etc. I guess my confusion is because really, the relatively
static content is the core of the site, meaning that Radiant should be
at the centre of the action! Any guidance would be enlightening
[1] This would allow me to embed Radiant into a Rails application,
right? So, I could build a site around Rails and then use Radiant to
manage the relatively static content, page caching, layouts,
stylesheets, etc. If so, this might be the perfect thing for one of
the projects I have in mind.
No, the other way around. It would let you build your application
inside Radiant as an extension. However, you still have incredible
freedom because any routes you define will override Radiant’s routes.
In general, though, as long as you don’t do anything complicated, it’s
pretty straightforward to convert an existing Rails app into a Radiant
extension.
[2] On the other hand, I’m planning to build an information site that
stores manuals, etc. in HTML and lets people add comments, sign up as
users, etc. I guess my confusion is because really, the relatively
static content is the core of the site, meaning that Radiant should be
at the centre of the action! Any guidance would be enlightening
That’s all very possible. As long as your site visitors are not editing
content (but really only adding comments), Radiant would be a viable
choice.
convert an existing Rails app into a Radiant extension.
Yeah, it’s a lot easier to build your app inside Radiant. I found
share_layouts because I wanted to use Radiant’s user system and admin
space
to manage a directory of organization members, but display them with my
own
controllers. I made an extension for the admin part (it’s a lot easier
than
you might thing… execute “script/generate extension” from RADIANT_ROOT
to
see an explanation, and then follow the tutorial [ http://wiki.radiantcms.org/Creating_Radiant_Extensions]), and then
dropped
some controllers and views in vendor/radiant/app… Sean can correct me
here, but I think you should be able to create the app directory in
RADIANT_ROOT to get the same effect.
[2] On the other hand, I’m planning to build an information site that
stores manuals, etc. in HTML and lets people add comments, sign up as users,
etc. I guess my confusion is because really, the relatively static content
is the core of the site, meaning that Radiant should be at the centre of the
action! Any guidance would be enlightening
That’s all very possible. As long as your site visitors are not editing
content (but really only adding comments), Radiant would be a viable choice.
