rubyonrailsin

i have a few remarks here;

first, Re Jonathan Kinney about using the index page extension to
organise a page's children.
I think you misunderstood the idea of the extension. All the index-
page extension does, is redirect requests to a certain page to it's
first child when it does not have content on itself. This will not
solve the problem of having too many pages to render in the backend
nor the front-end.

What you (mr jake) probably wìll want to implement, is the
functionality of what used to be the admin-tree-extension. This
extension was once put on the mailing list when we were still on
radiant 0.6.something, and has pretty much dissapeared since. However,
I have copied it's functionality into my gorilla-blog extension at
http://github.com/jomz/radiant-gorilla-blog-extension
This will change the behavior of pages with the ArchivePage class, so
that, when you expand them in the backend, you get a list of years and
under those months, that on their turn expand with the pages posted in
their timelapse (am i making sense?).
So, instead of getting a very long list of possibly thousands of
pages, you drill down to a certain month and only get the pages posted
in that month.

We use this on a site that fits your description but is probably
bigger and a little bit more complex: see http://belmodo.tv/
There you have live proof that a "big blog" can certainly be done with
Radiant.
I must honestly say, that when our clients are creating or updating
content on high traffic moments, we do sometimes have performance
hits. The problem being that for every page save, the entire cache is
cleared, so in the minutes after that we get a lot of requests to
uncached pages.
Another thing that sometimes lowers performance is when we are under
commentspam-attack, but that's not a Radiant issue since you always
have to evaluate POSTs to a CommentsController.
The site is now about 1.5 years old and building traffic, it now
handles well over 80k page-views per month, and is running on a VDS
with 256 MB Ram.

I'll be happy to provide you with more details if you like, but I just
attended a (scotland ruby) conference and have loads of work waiting
for me next week, so it may take me a while to respond. Anyways, if
you ask me, go go go!

Regards,
Benny

On 26 mrt, 09:48, William Ross <w...@spanner.org> wrote:
> On 26 Mar 2010, at 03:49, mr_jake wrote:
>
> > So, I still need to figure out if I should use Radiant for this
> > project. I'm willing to try to build an extension that makes Radiant
> > able to handle large amounts of pages, but I really don't have any
> > idea what I'd be getting myself into. Would this simply be another
> > extension or something that goes beyond what Radiant is meant to do
> > and is going to require some heavy lifting?
>
> No, it's purely an interface question. The underlying machinery of radiant can easily handle a large and busy site, but the interface decisions have all been towards simplicity and obviousness. The main view is not optimised for a broad or a very deep page tree, so if that's what you've got then you might want to change the view a bit. You can either do that superficially, by restyling long lists so that they display in a more compact way, or in a more profound way by providing more ways to find the page you want.
>
> For my own purposes I've been working on a blog extension that will give an alternative to treating a blog as a collection of pages. I think in many cases blog entries should be treated as content to be displayed in a consistent way, not as separate pages. I haven't got far with it because of other work, but in the admin interface it would probably involve both a separate list page and a special treatment of that node in the page tree to show some recent entries.
>
> best,
>
> will

--
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.