Xoops is intended as a stand alone Content management system. There is no point in wrapping a whole website, as much of the connectivity features of xoops would be lost.
There is a module called Auth(e) see below that can include web-pages into your xoops site.
For more details on using wrapper modules this see this FAQ here on
HTML pagesSite content can also be wrapped in an I-frame and there are likewise modules available for this, or simply by creating a custom block with an iframe in it.
Latest info... Following noisia's comment below there is an interesting thread
Here about Auth-Search This may be of use to some users.
Here is a snippet from the readme file:
Quote:
What is Auth module?
There are already HTML file wrapping modules for Xoops, like
TinyContent or iContent.
The problem with these modules, is that it is quite troublesome
to put the content in the xoops menu and additionally it requires
quite a lot of editing of the original html files.
There is most likely a need to have a xoops module that can easily
put html contents under separate xoops menus, so this is why I have
developed the "Auth module"
Additionally the Auth module will allow .php and .CGI files to be included instantly into Xoops, without the need to do any modifications. There are probably people that have some knowledge about using .php or .cgi, but would not be able to create a complete module.
All you need to do is put the .html, .php, .cgi and even image files into the designated "Auth module" folder and they will be automatically wrapped with the xoops header and footer and display properly in xoops.
I have not tried the Auth module and would be grateful if users could add details on this.
Cross links within html pages
Quote:
How do you preserve the links between the different html pages when importing them into wf-section?