I've done that and it works well, with the limitations you noted - it is static, so there can be no dynamic content (e.g. no comments - a Good Thing^TM - random

I've done that and it works well, with the limitations you noted - it is static, so there can be no dynamic content (e.g. no comments - a Good Thing^TM - random user's comments are nothing but trouble). Blogs are not a problem, but you have to (manually) refresh the static site after each blog entry. For a business site (what I set up) with essentially static content, that is fine. I no longer have access to the site, so I'm writing this from memory... I used a standard plugin that generated a static site out of the dynamic content. The plugin was for supporting static site serving on the local server, not a separate server. Being the more paranoid type, I used a Wordpress "authoring" server that was not publically accessible and a separate publically accessible "static" site server. I either had the plugin suboptimally/mis-configured or it had limitations, so I had to run a sed script on the output to change the web server host name from the internal authoring host to the static publically accessible host name (the link paths were fixed up properly). I then rsync'ed the result to the public host (with --delete to clean up obsolete files) using ssh keys for authentication, not passwords. I put this in a shell script, which made it simple and convenient for a sysadmin (me) to use but it was not user friendly for the Wordpress (not really computer literate) users. Not a problem, perhaps even a Good Thing^TM.