I use my own CMS. Basically I reads content from a parse-server (MongoDB), builds the html and uploads to AWS S3. All assets are also uploaded to S3. I also cod

I use my own CMS. Basically I reads content from a parse-server (MongoDB), builds the html and uploads to AWS S3. All assets are also uploaded to S3. I also coded the themes from scratch but if responsive nice-looking themes is what drags you to use WP, Joomla or Drupal, I have tested getting the html version of the theme and using it with my CMS. It does require some manual tweaking but it works. Keep in mind that I explicity said move a small box. I am sure there will always be a need for a dynamic CMS, for the sites that have tons of content and periodic updates (require workflow approval, multi-user, etc). But in reality, how many of these big sites exist vs a gazillion small websites that become targets of attacks b/c they are developed with a dynamic CMS and never again patched? I recently had a case of a WP site hacked for ransomware. This was a tiny 10-pages site (obviously a non-patched WP version). That particular server runs 20+ sites only one left published with WP, the hacked one. All other sites are static (in these cases I did not use AWS but just Bitbucket, git pull and the site is published). If I tell my clients (the ones that require the small boxes): hey, pay me x hours/month so I can keep things patched, they'll cry. If I tell them: I will just turn your site into good ol' static and whenever you need an update I'll quote and charge, they're happy. In any case, a quick google search will give you plenty of toolchains.