HN user

blaisco

59 karma

scott at scott blaine dot com

[ my public key: https://keybase.io/blaisco; my proof: https://keybase.io/blaisco/sigs/tQrZFLYioWuvYxCemFvfNCBQKfwvmXDViTiUImGWWYg ]

Posts6
Comments5
View on HN

I was looking for the same thing, so I built it. It's a WordPress plugin that outputs a static copy of your site to a ZIP or a directory of your choice. The thought being that you put WordPress on a subdomain (e.g. wp.example.com) and have the main site (www.example.com) served by the static copy.

https://wordpress.org/plugins/simply-static/

It's still a work in progress (it launched a little over a month ago) but the feedback so far has been positive.

That being said, it wouldn't hurt to start off with a simple sentence that reminds/reaffirms the value of their product to everyone.

I think most newsletters could benefit from this, particularly if they're going out ~once a month or less. patio11 does a good job of this with a quick two sentence introduction: (1) who is it and (2) why am I getting this.

Autoscaling Heroku workers is definitely a problem that people would like solved, but I see a few issues with trying to offer the solution as a SaaS. One, you're targeting developers. There are several github repos that do this kind of thing for free, and developers would know how to find and implement those. Two, those github repo's are going to do a better job of scaling because they can turn dynos/workers on and off instantly (e.g. as soon as a delayed job is done); much more cost effective than waiting up to 5 minutes to turn dynos/workers on/off. Three, you're targeting people that are trying to save money and _don't_ want to spend money.

As an aside, perhaps I (a cheap developer) am not in your target demographic, and you're really targeting folks with lots of Heroku apps and lots of money to spend. In which case you should be charging bundles more than $20/month.