Much prefer astro.

It's somewhat counterintuitive, but the added complexity leads to simpler projects that are easier to maintain long term. I have simple markdown files, and a separate, code-based conversion process that works well for me.

Also the documentation for eleventy was always confusing to me. I almost got the impression that "it's so simple, we don't have to explain it". Whereas astro's documentation is much more accesible; there were a handful of cases where there was something I wanted to do and astro had an example of exactly that. I didn't have to do guesswork, just follow the examples in the way the creators intended. Stuff like that is important.

▲

WickyNilliams 2 days ago | parent | next [-]

Astro is very nice, but I kinda feel like they are adding a lot of features I don't want and will never need. It's starting to feel too fancy for SSG. My first time using it I encountered 3 separate bugs with their compiler. The fanciness has a price.

	▲	mb2100 a day ago \| parent [-]
		That was exactly my experience as well, hence I created a "Minimal Astro": https://mastrojs.github.io

▲

adzm 2 days ago | parent | prev | next [-]

Astro is great, and easily extensible just by looking at the code and existing extensions too. Highly recommend it. Having the islands of actual react stuff is incredibly useful as well.

▲

deaux 2 days ago | parent [-]

> Having the islands of actual react stuff is incredibly useful as well.

I've tried multiple times to come up with usecases where they are worth it, but still haven't found any. The only theoretical examples are things where you wouldn't be using Astro in thr first place, like real-time document collaboration or something.

Curious what you've found them so useful for. Besides just preferring React syntax to HTML+TS I guess? But again that seems to go against the point of using Astro.

▲

adzm 21 hours ago | parent [-]

Well I have a static site generated with Astro that includes parts that still use dynamic react stuff, for example an interactive dashboard / slideshow kind of thing and interactive widgets. The data is baked into the static site but I still wanted the rich interactivity from react in certain places. It naturally grew from an Astro project that didn't need any react stuff, so it was a logical and simple step to add it in the few places it was needed.

	▲	deaux 17 hours ago \| parent [-]
		I've got slideshows and interactive calculators and things and it all works fine without the islands, that's the thing. LLMs will just incorrectly pattern match "interactivity = React".

▲

notpushkin 2 days ago | parent | prev | next [-]

Astro is great, and is what I prefer on new “static-y” projects (for more dynamic stuff, SvelteKit).

But 11ty really was so much simpler if all you need is to put together some templates, and don’t want to deal with component stuff. That said, the docs really are lacking in some parts.

	▲	2 days ago \| parent [-]
		[deleted]

▲

ymolodtsov 2 days ago | parent | prev [-]

Astro is fantastic. And with AI you don't have to deal with the piping much, just force it to have a reasonable opinionated framework at the base.