Static HTML version of site

I have a friend that uses and very expensive commercial CMS. He says that one of the major reasons they went with that system is because "it isn't a "live" CMS, but one that deploys static content to a public webserver." Is this something that Matrix does also? Can it create static versions of the pages that can be served by apache, rather than Matrix dynamicly building each page as it is called? I swear I remember reading this somewhere, but I can't find it in the docu. or find how to do this.


Any help?

[quote]I have a friend that uses and very expensive commercial CMS. He says that one of the major reasons they went with that system is because “it isn’t a “live” CMS, but one that deploys static content to a public webserver.”  Is this something that Matrix does also?  Can it create static versions of the pages that can be served by apache, rather than Matrix dynamicly building each page as it is called?  I swear I remember reading this somewhere, but I can’t find it in the docu. or find how to do this.


Any help?

[right][post=“11187”]<{POST_SNAPBACK}>[/post][/right][/quote]



I don’t know if I can answer this correctly however MSM will allow you to save a link to a page with in its control. For example: http://mymatrix.com/mypage



When you have this it will bring up the page that this link is referencing. So in turn, this would satisfy a part of your question. However I do not remember reading anything stating the pages were stored in static HTML sorry I could not be more help to you.

Hmmm…not what I was looking for. Maybe this funtionality is through the caching system…someone correct me.

No, Matrix does not "pre-bake" a site to static HTML, as most of Matrix's core functionality is based on its dynamic nature.


However, you can use a tool like HTTrack to spider a Matrix site and create a pure HTML version.

[quote]However, you can use a tool like HTTrack to spider a Matrix site and create a pure HTML version.
[right][post=“11195”]<{POST_SNAPBACK}>[/post][/right][/quote]

… or put a Squid proxy in front so what you serve is cached or partially cached pages. That way calling a page will not necessarily mean you need to build dynamically that page. Not sure it is what you require though…

In addition to Avi's comments above, using this option also tends to prevent dynamic content like form submissions which require some level of dynamicy