Sean Cribbs wrote: > It depends highly on your desired style of managing the site. If the > focus is more on dynamic user-generated content, then Radiant may not > be the best choice. If the focus is on highly style-able, > quasi-static content or brochureware, then Radiant may just be for > you. > > That said, there are a myriad of different combinations you could > conceive of for the site... Radiant can support many of your needs > with extensions if you're willing to write some Rails code. > > Sean Hi Sean,
I'm not the OP but have a similar question. I'm thinking of using Radiant for a site that has manuals and API documentation in HTML format (something like the PHP documentation site). The base of the site is the HTML version of the documents - these are updated occasionally when a new version is released. Closely linked to these documents is the dynamic portion that consists of code examples, comments from engineers, etc. (exactly like the PHP documentation site). All portions of the site are in multiple languages. On the other hand, I want to also have directly generated user content - a Wiki and a Forum/ BBS, an events calendar for events relating to this technology and perhaps a job board. I feel that for the Wiki & BBS, I'd like to integrate with other technologies (possibly Rails based) though I still need to work out some kind of single-sign-on. It seems to me that Radiant, with some work, would fit the bill. What do you feel? Cheers Mohit. _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
