Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The End of Eleventy

brennan.day

Post reply on HN
Print view View original

191–195 of 195 posts

Re: The End of Eleventy

#191

Post by busterarm »

xp84 wrote: post #189
busterarm wrote: post #31

Earlier quoted context omitted.

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.

WP Engine etc. cost a fortune - tens of thousands per year when you get a lot of traffic - for something that could be served statically for pennies.

Read my other comment. You can very easily use WordPress as just the CMS and still serve static content built from it.

So $30/mo for a secure, globally accessible backend for all of your content editors and pennies to serve it.

Re: The End of Eleventy

#192

Post by notpushkin »

ozim wrote: post #160
notpushkin wrote: post #70

Earlier quoted context omitted.

> RTF editor Is that what they call WYSIWYG? :eyes:

RTF editor may be part of WYSIWYG solution but it also might be used to edit text that on publication will be looking entirely differently or will be used in various places.

Ohh, I think I get it now – is this about literally using RTF as an intermediate format? I really don’t think I’ve heard about it being used in the context of static sites, but I see how it might make sense as a way of storing, well, rich text.

Pandoc is your best friend in such cases: https://pandoc.org/

Re: The End of Eleventy

#193

Post by 9dev »

wltr wrote: post #188
9dev wrote: post #90

Earlier quoted context omitted.

You're absolutely underestimating the complexity of proper live preview of changes. This is essentially "hot reload" mode, but on the public internet, because it has to run on a public domain. Getting that right is a challenge, and if you don't know why, you haven't attempted to solve it yet.

I would appreciate getting into more details. As it sounds like a made-up problem to me. Perhaps you don’t understand how simple it is to have a static website as compared to a dynamic one. Especially to some simple project.

You can always reduce complexity by moving the goal posts. In context of the original proposition—that one of the core values WordPress provides is live preview—we have to assume a reasonably complex website authored by multiple people.

Live Preview means, then, that you need to:

  - have a web-based editor behind secure auth,
  - create an environment resembling CI to rebuild the site on demand,
  - trigger rebuilds when a user modifies the content stored on the server,
  - make the new build available in a draft environment
    - …where it doesn't affect the live site,
    - …only grant access to collaborators,
    - …without breaking assets, links in the pages, CORS, or CSP.
There are more constraints and pitfalls that I'm not going to enumerate here. My point is, this stops being simple as soon as you stop being hand wavy about it.

Re: The End of Eleventy

#194

Post by wltr »

9dev wrote: post #193
wltr wrote: post #188

Earlier quoted context omitted.

I would appreciate getting into more details. As it sounds like a made-up problem to me. Perhaps you don’t understand how simple it is to have a static website as compared to a dynamic one. Especially to some simple project.

You can always reduce complexity by moving the goal posts. In context of the original proposition—that one of the core values WordPress provides is live preview—we have to assume a reasonably complex website authored by multiple people. Live Preview means, then, that you need to: - have a web-based editor behind secure auth, - create an environment resembling CI to rebuild the site on demand, - trigger rebuilds when…

The solution of this problem could be many, depending on the situation. I have my blog and other static sites synced to all my devices, and the server rebuilds them nightly. In most cases it makes no difference whether I’d deploy it right away, or it would be deployed within a day. Testing the website can be done completely offline, all you need is to sync your changes before the night. Triggering the rebuild on the server (which is deploy) can be done via a Shortcut from an iPhone. No way you can make it as easy with a Wordpress website.

Re: The End of Eleventy

#195

Post by xp84 »

busterarm wrote: post #191
xp84 wrote: post #189

Earlier quoted context omitted.

WP Engine etc. cost a fortune - tens of thousands per year when you get a lot of traffic - for something that could be served statically for pennies.

Read my other comment. You can very easily use WordPress as just the CMS and still serve static content built from it. So $30/mo for a secure, globally accessible backend for all of your content editors and pennies to serve it.

That's exactly what I advocate for as well. Static site export plugin for WP, and firewall WP behind an IP restriction. When Marketing updates the site every 3 weeks they can go click the big "Export" button to "publish it to the main site."
Post reply on HN