3 ms·

I would add that nobody gives a shit about behemonth dynamic CMSs anymore. It never made sense to use an 18-wheeler to move a small box. Static site generators

I would add that nobody gives a shit about behemonth dynamic CMSs anymore. It never made sense to use an 18-wheeler to move a small box. Static site generators combined with APIs/SAAS that do the dynamic part (like user managment, blogs, comments, etc) are just much easier to setup and maintain. Every week one reads about a new security flaw found in one of the 3 big dynamic CMS. Now imagine a junior dev charged $500 for a small site that has zero or small chunks of dynamic content. Is it worth to use a big dynamic CMS knowing that your clients will not be paying you an SLA that justifies keeping the code patched and updated? Furthermore, plugins are now SAAS with an API while themes are decoupled from the CMS. Also, private hosting of a small/medium static site is almost free.

venomsnake 10y ago
Can you give example of such static site workchain?
- lightlyused 10y ago
  Along with multi-user editing and approval workflow?
  - venomsnake 10y ago
    I am fine with singe user. But if there is something that takes less effort than a wordpress - I could use it quite well.
- bikamonki 10y ago
  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.

venomsnake 10y ago

Can you give example of such static site workchain?

lightlyused 10y ago
Along with multi-user editing and approval workflow?
- venomsnake 10y ago
  I am fine with singe user. But if there is something that takes less effort than a wordpress - I could use it quite well.
bikamonki 10y ago
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.