Hello,

Last week, I sat down in front of my computer to work through the very promising tutorials at:


http://www.grabageek.net/makingofgrabageek_part1.htm

http://www.grabageek.net/makingofgrabageek_part2.htm

(I found the links to these on this site), when the grabageek.net site went down!

Does anybody know why, and more importantly, whether the tutorials are available anywhere else?

If somone has a copy, I could try to put them up on my site.

Thanks.

This is one of those postings, perhaps a bit different than others, designed to help people decide whether XOOPS is right for them (or not).

I'm a developer - the "back-end" half of a small web development partnership (my partner is a front-end graphic artist and page producer). I'm thus a relatively "technical" (potential) XOOPS user. I've built the back-end of sites using Perl (CGI), Java Servlets, and PHP (using Smarty and mySQL). Here are three questions I have about Xoops:

I'm attracted to XOOPS because it seems like a good content management system development framework. In other words, it provides a set of classes, libraries, and tools that can be useful to CMS developers for creating customized CMS sites.

(1) Is it correct to say that XOOPS is more like a development framework than a CMS itself? Is it thus more flexible and powerful for developing custom CMS sites than other CMS's (such as Mambo or Drupal), that are not geared towards developers?

More correctly, perhaps XOOPS is very good "right out of the box" for CMS site development for non-technical users, but (2) is it also better than others (e.g., Mambo, Drupal) for customization (e.g., developing custom modules and themes/templates)?

(3) Does this explain why XOOPS has a smaller number of users than Mambo and Drupal, for example?

I know this post is a bit vague, but I'm trying to assess the suitability of XOOPS as a "developer's CMS."

Thanks in advance for your thoughts on this.