and me moving from Next.js does not mean I think it's a terrible tool!
Taking on the migration from Next.js to 11ty was likely - significant.
Given the predominant values among those who already have adopted Next.js (e.g. for their blog) I suspect having to trade component centric development for templating (including JavaScript templates) would be a hard sell (***).
Astro could be seen as an alternative, capable of producing similar results without having to sacrifice the amenities of their chosen component framework.
(*** Though 11ty is an excellent choice for developers learning HTML/CSS/JS; allowing them to create static web sites with build-time JavaScript rather than immediately diving into a JavaScript heavy tool for client-side rendering.)
Taking on the migration from Next.js to 11ty was likely - significant.
Given the predominant values among those who already have adopted Next.js (e.g. for their blog) I suspect having to trade component centric development for templating (including JavaScript templates) would be a hard sell (***).
Astro could be seen as an alternative, capable of producing similar results without having to sacrifice the amenities of their chosen component framework.
(*** Though 11ty is an excellent choice for developers learning HTML/CSS/JS; allowing them to create static web sites with build-time JavaScript rather than immediately diving into a JavaScript heavy tool for client-side rendering.)
You're not wrong! I've got a blog post in the works that will explain my process... kind of an "Eleventy for Next.js developers" approach.
Astro is next on my list to look at for a project I'm working on!