Unless you're just trying to get away with hosting your whole site as a GitHub page ;)
I don't understand why people use a database for content that (for the most part) doesn't need one.
You could easily replace his rsync with an s3cmd sync to ship the stuff straight to the S3 bucket.
Sure, S3 may cost more per byte shipped than serving it yourself, but probably not for a personal site (if you factor in the need to pay for a running server and the extra hassles and time cost involved with maintaining that server). You can pay for a lot of S3 bandwidth with what you pay for even a cheap VPS.
At the end of your day your content is already being stored in a database or in some custom format to be able to generate the static site aways. You have a lot more options if you go through a database first vs a custom static format.
Simplicity? If the content is not an application but a static publication I'm left wondering how making it dynamic would improve anything...