← Back to context

Comment by xp84

13 hours ago

SSGs versus Wordpress is surprisingly still a battle… I’m genuinely shocked at the number of sites on the Net that use Wordpress, dynamically assembling markup with PHP for every page view, risking constant hacking and stuff, when they have a total of like 7 or 100 pages, which could all be pre-rendered to HTML files in roughly 8 seconds on even a junky laptop or X-small ec2 instance. It really is okay.

For those who post regular updates on those sites, there are great and cheap WP plugins that export the whole site as static to something like FTP or S3, so you can just firewall the actual WP behind an IP restriction and host the actual public-facing site from S3/whatever.

Is there a tenable workflow for the marketing department to use a SSG over Wordpress?

- WYSIWYG editor is table stakes. The lovely folks at marketing once thought I was hacking when I `ps -eaf`-ed in an unresponsive Macbook.

- They "put" images in their post. They don't "upload the image and position it with CSS".

- It's the marketing department so they have to have all sorts of bells and whistles. At the very least tracking, at most some obscure integration plug-in that as an engineer I have no kind words for. Social integrations and "You may also like..." sections also come to mind.

> cheap WP plugins that export the whole site as static to something like FTP or S3, so you can just firewall the actual WP behind an IP restriction and host the actual public-facing site from S3/whatever.

Not that I have extensive WP experience but unless you can name me an actual plugin that has good street cred for being used in the wild wild west, I'm gonna say this is not as easy as you make it sound. For one you just described a very rudimentary data pipeline which someone has to support and maintain even infrequently. Also, speaking from experience, plugins don't always play nice with other plugins. I once tried to export my very basic personal site out of WP to find the footnotes all messed up (I don't know now but back then I handled footnotes with a plugin).

  • I think that's exactly the point where the article falls flat. There is potentially a big oppurtunity in building a SSG + CMS solution despite the past failed attempts.

    Every few years I go looking for something that's not Wordpress that you could hand to a marketing department, but there is no viable alternative (that's not Drupal).

    • There's a number of headless CMS solutions for commercial websites. Hosted, multi-user, paid. It's just a different category.

Ironically, one of the original major reasons WordPress became popular was its dynamic nature. It dethroned Movable Type, which was an extremely powerful and extensible static site generator.

It's wild to me that this post's timeline makes no mention whatsoever of Movable Type, and at one point it links to another author's post titled "A Complete History of Static: The Beginning to WordPress Headless" which also makes no mention whatsoever of Movable Type. Now I feel old :/

  • To my surprise, Movable Type is still being developed even today. Wonder if there's some companies still using it out inertia. I know many moved off of it back when they restricted their free tier

    • I haven't kept up with it in recent years, but I know it remained popular in Japan for many years longer than elsewhere. AFAIK since 2011 it has been developed by a Japanese company, who acquired Six Apart's former subsidiary there, as well as the brand name.

      It's also interesting that so many people in this thread are saying "What I really need is a SSG that also works as a CMS with a GUI" -- that's literally what Movable Type excelled at. Especially versions 4 and 5, which had a FOSS edition. A number of major US media sites were powered by it for years. However because it was written in Perl, that became a huge negative point as Perl fell out of use in the industry.

> I’m genuinely shocked at the number of sites on the Net that use Wordpress, dynamically assembling markup with PHP for every page view,

What puzzles me about static sites (and I do build them) is how everything gets to be regenerated, even though you update only one file.

Now, imagine that your writing patten is small notes, like on twitter, mastodon, or bluesky. Over time, with this pattern, you will end up with thousands of notes. Is each one deserving of a page? Ideally, yes; because they should be linkable. Does it make sense to regenerate thousands of pages every time you add a note? Dunno.

Then, consider all the aggregation pages. For example, a paginated list of all my notes. Or a paginated list of notes distributed by different categories / tags. How many more pages does this create?

And the static assets that all get to be copied from source to output directory at every build.

And of course, comments. Static sites don't have comments.

I don't know. I think someone who invested into building their own site engines, like Jeremy Keith (https://adactio.com/) have it the best.

I started my client's site on Hugo, withing 2 days I was editing something for them every 30 mins (slight exaggeration). They wanted something they could edit, they don't do Markdown, they don't manually write URLs they want to drag images into their posts and pages.

So bye bye Hugo.

  • Check out TinaCMS. Works for editing Hugo sites. Not as nice as WordPress admin, but it's good enough for simple editing tasks.

  • This is generally solvable unless they wanted radical layout changes. There are headless CMS solutions, just ensure that no texts are hardcoded and instead put in a config. Such configs can be made editable in the CMS.

  • Normal people refuse to learn markdown - they want RTF editor.

    I could understand someone might refuse learning LaTex but markdown is so simple.

    RTF editing sucks badly if you have to include it in your project. No one wants to specifically pay for implementing it but they also expect it to be there.

I recently moved all my website from WordPress. In last few year couple of them had got hacked via plugin exploits as well. I had to use "security" plugins after that i didn't have any issue but still...

I crawled own website and downloaded each, and converted to markdown then used static site generator (custom in javascript)

runs on cloudflare pages for free with no downtimes or "fee".

if you want to see result: https://aretecodex.pages.dev/guides/recomposition

Couple of problems:

To edit content i've to use "image paste" plugin and configure its base directory, image path in project setting in .vscode

I lost the comment/upvote feature.

I lost "search"

Wordpress has:

* the ability to schedule posts

* a ton of plugins

* a lot of people who know how to use it

* a reasonable WYSIWYG interface

As far as I know, most SSGs fall down on one or more of those dimensions.

  • 3rd bullet. I do a ton of WordPress at work. Clients asked for it because they know how to use it.

  • * live preview

    • I can live preview my website from my local server / computer / laptop, while writing content from basically anything. Even a cheap and underpowered writing deck with 400 MHz CPU. The options are limitless.

      3 replies →

Switching from word press to static site generator caused disruption to my autoflow habit of posting. WordPress (I didn't have to maintain) had a gui I didn't have to think to use. I still made the switch though.

To me, the thing wordpress installs offer is the GUI. I help a few people with wordpress installs, and I've ended up setting up a private wordpress install, and then I run a script which mirrors the website statically -- this is moderately hacky, and I'm sure could be done better, but as long as I hide the private wordpress install, it means I don't need to worry about keeping it up to date.

I haven't found a static generator which has as nice a WYSIWYG interface as wordpress.

have you ever heard of caching? because it can do the exact same thing as what you just described, yet WP can also be dynamic, have visual page and post builders, etc...

The WordPress hacking/plugin security issue has been a solved problem for well over 10 years now if you're even basically competent. Especially if you're using something like WP Engine or Pantheon for hosting.