Aitor, I for one would be very interested in your extension. I looking forward to seeing it soon..
saji * Aitor Garay-Romero <[EMAIL PROTECTED]> [2007-09-13 22:17:00 +0200]: > 12K articles, that's a mini wikipedia! > > Just one though. > > It depends on your requirements, but you don't need to go fully > "dynamic". I mean, you can do everything in Radiant (adjusting the admin UI > as you said) and then generate all the pages and store them to be served > statically. That is, something like making the current Radiant cache usable > by the web server directly. When something is updated, regenerate the > static content. May be all of it, or wisely only the modified parts, if > possible. > > I have been thinking on doing this with some Radiant projects i'm > working on. It allows to "use" Radiant in cheap-with-no-rails shared > hosting for example. It's probable that in the following weeks i develop a > Radiant extension for this purpose. > > A good friend has developed a high traffic site, updated daily, using > this technique (not in Radiant) and the customer was very satisfied with the > result. So it's possible to do it. > > /AITOR > > On 9/13/07, Loren Johnson <[EMAIL PROTECTED]> wrote: > > > > > > I've been enlisted to take a 12,000+ article site (static .html > > pages!) with 500k unique visitors a month and convert it to a dynamic > > site where the owner of the site can more readily flow advertising, > > among other things alongside the content. > > > > The HTML (not XHTML) is mostly all old bad stuff, the clean-up and > > conversion of which is a separate task and discussion entirely. > > > > > > My question for the other members of the core team and the community > > at large is: > > > > 1. Am I crazy to be considering Radiant as the starting point for > > this project? I know I will need to section-up and somewhat re-invent > > the admin page tree, at minimum, but despite the size and popularity > > of the site, there are not a lot of unique CMS features needed. > > > > It's definitely an option to go custom from ground-up and their may > > be just enough in their budget to accommodate the custom route, > > however because of the unique situation of this client (the site is > > soon to be sold) time is of the essence and for this reason starting > > with Radiant could be a valuable jump start. > > > > The questions in my mind now are about caching and the core > > performance of Radiant under what could be significant load. I don't > > have peak number of pages served per second or minute right now, but > > will have those numbers shortly. > > > > > > 2. Is there any precedence for such a thing. I seem to remember a > > discussion a while back about relative site size and thought I > > remembered seeing that someone is managing a 1-2k page site in it > > currently. > > > > > > _______________________________________________ > > Radiant mailing list > > Post: [email protected] > > Search: http://radiantcms.org/mailing-list/search/ > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > > _______________________________________________ > Radiant mailing list > Post: [email protected] > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- Saji N. Hameed APEC Climate Center +82 51 668 7470 National Pension Corporation Busan Building 12F Yeonsan 2-dong, Yeonje-gu, BUSAN 611705 [EMAIL PROTECTED] KOREA _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
