However you really should look into static website generators such as Jekyll, Octopress or Hyde. They provide a much cleaner interface for that kind of stuff.
I'm a big fan of Mynt (http://mynt.mirroredwhite.com/) - it's very simple and easy to understand, but is powerful enough to do just about anything you need.
Holy cow, $60/month for one VPS strictly used for educational projects? You can find and build 10 VPS's (US based) on http://www.lowendbox.com for less than that, granted you wont be on Amazon's network, but for small projects and testing distributed services they are great.
Hm, the search should be 'fixed' too. That, along with getting rid of most plugins, and the comments, means that WordPress is only retained for its moderate flexibility and admin interface.
As people say, static generators along with a small toolkit of your own will probably produce better results. But what is proposed is a compromise between an already started job and a good cost-scalability ratio, though…
Why not host it on a mini-vps with the wordpress install but use supercache and force it to always use the "logged out" copy (and don't allow registered users).
Then it bypasses wordpress and php entirely via htaccess and becomes entirely static.
11 comments
[ 3.2 ms ] story [ 38.9 ms ] threadHowever you really should look into static website generators such as Jekyll, Octopress or Hyde. They provide a much cleaner interface for that kind of stuff.
On the other hand, hosting a blog on S3 means that it can scale to handle any conceivable amount of traffic.
As people say, static generators along with a small toolkit of your own will probably produce better results. But what is proposed is a compromise between an already started job and a good cost-scalability ratio, though…
Then it bypasses wordpress and php entirely via htaccess and becomes entirely static.
http://www.allthingsdistributed.com/2011/08/Jekyll-amazon-s3...