> Can a static personal website get fucked over badly? A pure static website (i.e., only a webserver and files on a filesystem) avoids all exploits that involv

> Can a static personal website get fucked over badly? A pure static website (i.e., only a webserver and files on a filesystem) avoids all exploits that involve "hack into the CMS". It is vulnerable to "hack into the server itself" -- but you must secure the sever no matter whether you host static files or install something like wordpress. Re. bandwidth -- unless you become popular you will not need to worry about bandwidth. And even if you do, a webserver and static files can withstand a rather significant size traffic burst without breaking a sweat at all. So you can put off worrying about traffic until after you may have become popular enough to justify worrying about bandwidth. > To be more specific: I've got a cheap droplet and $1 domain-name from Google and would like to put a personal blog on there. Can it run a webserver? If yes, then it is very likely more than capable of handling a static website for a surprising amount of traffic. > I am worried that by doing so I'm making myself a target in ways I would never expect. Part of that depends upon what you reveal. If you give all your personal info out on the site, you are making yourself a bigger target than if no one knows your name (or any of your other details). > or using a specific static site generator A static website needs nothing more than a working webserver and a text editor (vi/emacs/etc.). The value add for "static site generators" is they remove a lot of the manual work involved in using a text editor to write html.