Thread

Hi everyone,

My apologies for just jumping right in here, hope my question is not stupid.  We’re building a new site that could, in theory, be entirely HTML as far as the user’s concerned.  No blogs, forums, any of that.  Just good old fashioned brochure-ware.  My designer got us involved with EE because the marketing team needs a solution that will enable them to publish their content without having to worry about all the HTML nastiness.  A standard story, I’m sure. 

Here’s what I’m wondering, though.  Does EE offer a way to export out an entire site as a file structure (complete with HTML, CSS, images, etc….) that I could just throw out on a web server and call it a day?  My authors and editors would still get all the functionality they want out of EE, we’d just add a final publish phase that moves the content out to the production web server.  Imagine if I pointed a spider at a running EE hosted site and said “Get everything.”  And then pointed a web server at the results.

The reason for my question is one of operations - it’s far, far easier for us to roll with something that makes use of one of the webserver machines in existence, rather than having to setup a whole new PHP/MySQL environment (our prod instance is Oracle, for example).  I can have PHP/MySQL internally all I want.  So I’m trying to figure a compromise between the two.  If this works, everybody wins - marketing manages the site they want using the tools that are best, and operations does not introduce new technologies they are not ready or equipped for.

Thanks!

There isn’t a built in way. The most common way is to use wget or some program that will download an entire site to a static format. Some have used this method to produce site CDs.
There are several threads with different methods. Sorry, don’t have any bookmarked but I’d start by searching “wget” as it’s mentioned in most threads as I recall.