This looks great!
I'm curious why it is only for Cloudflare/Vercel/etc.?
My understanding is that Astro.js generates a static site, so couldn't one SFTP its output to any web server?
Also, looking forward to following releases on GitHub, but nothing there yet.
Hey! Thanks for the kind words and for taking a look! Yes you can export the project as a zip and deploy it anywhere (tab bar → cog → download icon). I just was optimizing for a use case when a person wants to put their site online and they heard about Cloudflare or Netlify – hoping it would be easier for their mental model.
I’ll improve my GitHub game in the upcoming week. Thanks for pointing it out!
I'm getting 404 errors on almost all of the Assets.
They show (for example):
Path: /__sq_component_view/src/components/Hero3.astro
Under Dynamic > Pages > BlogPost I get a message in the lower right saying "Couldn't prepare the component for editing. BlogPost depends upon ../../layouts/Layout.astro which lives outside the component library."
This looks great! I'm curious why it is only for Cloudflare/Vercel/etc.? My understanding is that Astro.js generates a static site, so couldn't one SFTP its output to any web server? Also, looking forward to following releases on GitHub, but nothing there yet.
Hey! Thanks for the kind words and for taking a look! Yes you can export the project as a zip and deploy it anywhere (tab bar → cog → download icon). I just was optimizing for a use case when a person wants to put their site online and they heard about Cloudflare or Netlify – hoping it would be easier for their mental model.
I’ll improve my GitHub game in the upcoming week. Thanks for pointing it out!
I'm getting 404 errors on almost all of the Assets. They show (for example): Path: /__sq_component_view/src/components/Hero3.astro Under Dynamic > Pages > BlogPost I get a message in the lower right saying "Couldn't prepare the component for editing. BlogPost depends upon ../../layouts/Layout.astro which lives outside the component library."