rubyonrailsin

A Ruby and Rails talk

Wednesday, March 24, 2010


[Radiant-Dev] What is Radiant NOT suited for?

by rubyonrailsin 0 comments

Tag


Share this post:
Design Float
StumbleUpon
Reddit

I'm planning on doing a website with Radiant, but I read somewhere
that if your site is big and has a lot of articles, then it's best to
look elsewhere. Is this true? How big is too big for Radiant and what
is Radiant NOT suited for?

I really would like to use Radiant for my project for various reasons,
but I don't want to use the wrong tool for the job just because I'm
fond of the tool, if you know what I mean.

This new site is basically a big blog. There's going to be, oh,
probably hundreds of articles in, say, 10 categories with photos,
advertising, etc. There will be multiple authors publishing anywhere
from 5-10 articles a week when it really gets going, etc. All of the
content will be published through the site itself (nothing is being
pulled from outside sources). No comments, nothing fancy. The home
page will feature articles in all 10 categories while each category
will feature articles in that particular category. There will be a
tagging system and a search function and that's it.

One of my major concerns is performance. Should I be concerned about
that and what else should I be concerned about?

Thanks guys!

--
Radiant CMS Dev Mailing List
Post: radiantcms-dev@googlegroups.com
Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
Group Site: http://groups.google.com/group/radiantcms-dev/

To unsubscribe from this group, send email to radiantcms-dev+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.

No comments:

Post a Comment

Subscribe feeds via e-mail

Blog Archive