Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Astro 1.0 – a web framework for building fast, content-focused websites

astro.build

Post reply on HN
Print view View original

41–50 of 256 posts

Re: Astro 1.0 – a web framework for building fast, content-focused websites

#41

Post by malfist »

pembrook wrote: post #26

Is there a static site generator out there that doesn't require a ridiculous build process every time I do an update? Inevitably, when a new "hot" SSG comes on the scene, I try it, and then go back to compare it to the old "hot" SSG from 2 years ago. Yet, I can never get the old test site I set up running again without massive annoyances. This has happened multiple times. As far as I'm concerned, there's zero reason…

Have you checked out Hugo? It's builds are pretty fast, and it has a watch function for rapid dev work.

Not sure how you'd get away from a build on updates though, it is called a static site __generator_. If you want to skip the build entirely, just write .html files and call it a day.

Re: Astro 1.0 – a web framework for building fast, content-focused websites

#42

Post by ggregoire »

CharlesW wrote: post #10

I'm looking at https://docs.astro.build/en/concepts/why-astro/ and I still can't tell what's interesting and unique about this as compared to other options in this space. I acknowledge that this might be a PEBKAC situation, but I'd love to hear thoughts from people who used Next.js, Remix, or whatever and found Astro to be a revelation. It seems like Astro's creators believe "content-focused" is a differentiator, but…

The core concept and main difference is described here I think: https://docs.astro.build/en/concepts/islands

There is also this page comparing it with other tools: https://docs.astro.build/en/comparing-astro-vs-other-tools

Re: Astro 1.0 – a web framework for building fast, content-focused websites

#43

Post by fareesh »

I used a static site generator for all of these benefits in the past, but the rebuilding process is a total nightmare.

The site has about 20 categories, and each category has about 100 images. Every time the team adds a new image or category, the deployment/building task clones the repo and then the build process generates all the optimally sized images again and then re-uploads multiple gigabytes to the host. Is there a way around this type of problem with static site generators?

Re: Astro 1.0 – a web framework for building fast, content-focused websites

#45

Post by game-of-throws »

pembrook wrote: post #26

Is there a static site generator out there that doesn't require a ridiculous build process every time I do an update? Inevitably, when a new "hot" SSG comes on the scene, I try it, and then go back to compare it to the old "hot" SSG from 2 years ago. Yet, I can never get the old test site I set up running again without massive annoyances. This has happened multiple times. As far as I'm concerned, there's zero reason…

Use any SSG not written in javascript and you'll be fine. Hugo, Zola, Jekyll, etc. Though if I was starting from scratch I might avoid Jekyll just because of the Ruby dependency.

Re: Astro 1.0 – a web framework for building fast, content-focused websites

#46

Post by reilly3000 »

GrahamL wrote: post #20
CharlesW wrote: post #10

I'm looking at https://docs.astro.build/en/concepts/why-astro/ and I still can't tell what's interesting and unique about this as compared to other options in this space. I acknowledge that this might be a PEBKAC situation, but I'd love to hear thoughts from people who used Next.js, Remix, or whatever and found Astro to be a revelation. It seems like Astro's creators believe "content-focused" is a differentiator, but…

It's interesting their blog post doesn't mention some of the benefits. Neither does the doc page you linked—at least it doesn't do it succinctly. Essentially Astro lets you build sites using a JS framework like React or Vue without requiring that framework to be loaded on the frontend. By default, components are just HTML content. Super nice for building very fast static sites using a technology you may already be fl…

Their homepage https://astro.build has a nice summary of its approach and benefits.

Re: Astro 1.0 – a web framework for building fast, content-focused websites

#47

Post by itcrowd »

It always annoys me when I read something like:

   To try Astro on your local machine, run npm create astro@latest in any terminal.
because it doesn't make it clear to me what to do before this command will actually do anything. No, running this command will not work in any terminal.

Re: Astro 1.0 – a web framework for building fast, content-focused websites

#48

Post by gavinray »

MatthewPhillips wrote: post #38
gavinray wrote: post #19

Serious question: Why does Astro need a custom file format? The format looks identical to MDX

It uses it to know what JS is needed for the client. If it sees that means that no-JS is needed. But if it sees it knows to build + bundle the Counter component and attach its JS to the page.

That's just a property on an element tag, you can access "client:load" under the ".properties" key of the element

Open your browser devtools, pick a random tag on the page, add "client:load" to it, and then "console.log(yourEl.properties)"

I dunno why you need an entire custom filetype for behavior and semantics that are MDX with a few extra preprocessor rules

Re: Astro 1.0 – a web framework for building fast, content-focused websites

#49

Post by e_i_pi_2 »

pembrook wrote: post #26

Is there a static site generator out there that doesn't require a ridiculous build process every time I do an update? Inevitably, when a new "hot" SSG comes on the scene, I try it, and then go back to compare it to the old "hot" SSG from 2 years ago. Yet, I can never get the old test site I set up running again without massive annoyances. This has happened multiple times. As far as I'm concerned, there's zero reason…

As a counterpoint - the big benefit I see from Astro isn't that it has minimal dependencies, it's mainly that it seems like a very flexible foundation to build from. So I'd agree a landing page doesn't need this, but "the best tool" for a landing page is probably too specialized for general use in larger applications.

Re: Astro 1.0 – a web framework for building fast, content-focused websites

#50

Post by butz »

fareesh wrote: post #43

I used a static site generator for all of these benefits in the past, but the rebuilding process is a total nightmare. The site has about 20 categories, and each category has about 100 images. Every time the team adds a new image or category, the deployment/building task clones the repo and then the build process generates all the optimally sized images again and then re-uploads multiple gigabytes to the host. Is the…

Offload image optimization to separate service?
Post reply on HN