The End of Eleventy

Didn't read because of the fuckery with the mouse pointer. Why do sites have to do this crap.

I use Eleventy for nearly all of my static sites. Almost every project of mine has at least an 11ty internal docs site. I'm very happy that Eleventy has a home and Zach a job.

But my only thought on this is: Eleventy is an awesome name.

if the kickstarter campaign met its goals, but then their outgoing emails ended up in the spam folders, why does that say cancel? They cite "momentum", but doesn't the fundraising success sustain the momentum of the project and team? solve the email problem and mail the sponsors again, what's the big deal, since when do sponsors need momentum if the goal has been met?

The thing about SSGs is that you only need a small percentage of the functionality they offer and for what: so instead of some simple syntax for links you can remember in HTML

  description

there is something weird and irregular I always have to look up in the manual in Markdown and all sorts of other Markdown WTFs. Every time I tried to get started on a personal site with an SSG I would get depressed looking at hundreds of ugly themes, get depressed with the mysterious and crappy cloud-side build systems, get depressed with the prospect of customizing them, etc. So I'd start experimenting, never finish and come back six months to make another attempt that fails.

When I really needed a landing page that looked like it fell off a UFO I did it in Vite-React (such a joy to use semantic components, like write

   Earth Day Parade Ithaca Commons

and it is a simple python script that uploads the dist files to S3 (no "WTF went wrong with the github action") invalidates Cloudfront [1], extracts metadata, maintains the metadata database. There's a clear path to extending the system to do exactly what I want to do in the future unlike some SSG which I will have to relearn from scratch in six months when I want to make a big change... and had it up and running and in front of end users in a weekend.

That is, SSG has no commercial potential because any individual or organization which is capable of maintaining and customizing an SSG can create one from scratch that does exactly what they need with less cost and effort and success is only possible through hypnotizing people into thinking otherwise -- in many fields of software this happens every day but I think not SSG, like those people are going to stay asleep and dream of Drupal and Wordpress.

[1] ... and if I want to move to some similar platform I just implement it instead of struggle with "plugins" and "modules" and other overcomplicated extension mechanisms

> Who uses 11ty? NASA, CERN, the TC39 committee, W3C, Google, Microsoft, Mozilla, Apache, freeCodeCamp, to name a few.

> Imagine if Build Awesome actually reached out to people who regularly make static sites. You know, the userbases on NeoCities or MelonLand or 32-bit Cafe?

One minute you are saying large companies use the product, the next that it was always for hobbyists and shouldn't target corporate features?

> In truth, I myself have started a business that has a near identical concept to Build Awesome. Berry House is my independent web studio

> The difference is though that my model is pay-what-you-can, or pro bono. I developed Calgary Groups for a client and charged $5/hour for my dev work.

That is not a business -- no profit motive. (Working less than minimum wage, even.) Not a good benchmark for comparing what an actual business like Font Awesome should do.