[hazebooth]

I haven't used 'Next Content', but one big difference is that Astro is framework agnostic. I'm not a huge web dev so I wouldn't know how different these frameworks are, but not being locked in/being able to try another framework is cool

[baby]

It looks like it's another framework to me. The basic example looks exactly like Nuxt to me as well! (component, pages, and layout folder!)

To answer my previous question, they have a page talking about the similarities and differences here: https://docs.astro.build/en/guides/migrate-to-astro/from-nux...

They look really really similar to me (Nuxt content and Astro)

[eyelidlessness]

Astro is akin to other “meta-frameworks” with SSR/SSG like Next/Nuxt/etc, but it’s client-framework agnostic so its meta-ness is too. What primarily sets it apart is that it’s designed to ship just HTML/CSS by default, with any client side JS being opt-in where a client component is invoked (termed “islands”), and those components being authored in any client component library of your choosing (if an adapter for it exists, and many do). Or even vanilla JS, but then Astro is more akin to Jekyll or other similar SSGs.