Astro 2.0
astro.build
Astro 2.0
1–10 of 48 posts
Re: Astro 2.0
#2I recently tried Astro for the first time and really enjoyed it!
Guess it's time to learn how smooth the upgrade path is...
Re: Astro 2.0
#3[deleted]
Re: Astro 2.0
#4I like the idea of "performant, content-focused websites" but the website itself hosting Astro doesn't really feel performant. When I scroll down it struggles on my quite powerful desktop computer.
Re: Astro 2.0
#5I like the idea of "performant, content-focused websites" but the website itself hosting Astro doesn't really feel performant. When I scroll down it struggles on my quite powerful desktop computer.
[deleted]
Re: Astro 2.0
#6I read entire documentation yesterday, and I am very impressed. Looks fantastic, with some great conventions if you need it quick, but fully customizable if you change your mind later. I particularly like the fact that I can switch from SSG to SSR and back.
File system as db, markdown with templating and js expressions, nasting layouts, quick random endpoints, filtering of collections, named slots everything repo friendly - whats not to like. Also, great content and looking docs (particularly interactive tutorial).
Reminds me a lot of nanoc SSG framework (ruby).
Re: Astro 2.0
#7[deleted]
[deleted]
Re: Astro 2.0
#8How does Astro hybrid rendering compare to Qwik? https://qwik.builder.io/
Re: Astro 2.0
#9We switched to Astro a few months ago. Some team members were not super convinced since NextJs is better known but during our spike to test them both out Astro came on top on ease of use.
We have now been in production for a couple of months and could not be happier. It’s very straight forward for simple sites but we switched a couple of legacy react apps to SSR with it and it was super easy and developer experience is great and speed of rendering could not be better. Looking forward to switching our marketing site next with the help of this new collection API in v2
Re: Astro 2.0
#10Astro is nice but it misses the UX of instant page transitions via client side routing, so I switched back to NextJS.