What XOOPS needs (and probably a lot of other CMS) is a kind of frames module, that allows XOOPS to wrap around existing web pages. I'm also working on a school website, and I'm thinking of just creating a new template for all my pages that looks like the one I'm using with Xoops. Then I'll probably use iMenu for the links.

imenue

The user won't know the difference.

You can also create your own mod see here. You may have to register to see this link.

I made a very simple "mod". Simply a folder with index.php and xoops_version.php. The index.php file contained a few links, nothing more. What would be nice is if upon pressing a link, the content stayed inside xoops. Anyone?

Which brings me to a general question. XOOPS is great as it links together some important things: forum, calendar (like Agenda-x), faq, etc., which are all searchable as they are part of the same system. However, most of the CMS that I've looked at don't account for site with lots of pages. For example: On a school site we might want to have pages for every class, club and program. What's the best way to get these pages up?

Sections is content, but mostly text.

Freecontent, etc., seems like a good alternative, but what if my content has child pages? Do those stay in the XOOPS wrap?

Quote:

First, did you begin with a fresh template theme? Or did you modify the default?

Second, shop question already answered.

But mainly, the link action in the main menu, is that part of the CCS?

Really nice; looks original. Please give us some pointers on how you did it.

Mark

I'm getting this message:

Quote:

What do I set these to?
DMS Page Title: <anything, I get it>
Document storage path: <this is what I put: var/www/html/modules/dms/repository>
Document Storage Tuning: 1000
Template Root Directory ID: <what do I type here?>