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

61–70 of 256 posts

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

#61

Post by root_axis »

game-of-throws wrote: post #45
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.

> Use any SSG not written in javascript and you'll be fine.

Commonly stated but not actually true. For example:

https://github.com/getzola/zola/blob/master/Cargo.lock

https://github.com/gohugoio/hugo (scroll to the bottom of the README)

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

#62

Post by ksbrooksjr »

itcrowd wrote: post #47

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.

As long as you have npm installed it'll work. Npm create is an alias for the npm init command [1], which will look for a package with the prefix 'create-', install it, and run its bin file. It looks like this is the file that ends up being run: https://github.com/withastro/astro/blob/main/packages/create....

[1] https://docs.npmjs.com/cli/v8/commands/npm-init

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

#63

Post by zoover2020 »

eins1234 wrote: post #17
foofoobar wrote: post #9

Earlier quoted context omitted.

Netlify recently changed their pricing structure, so if you are using Netlify CMS (or just Netlify Identity) with a private repo, every contributor to the repository (committer) will be charged as full pro seat. This can get really expensive if you have a few users working with the CMS (and thus committing content to the repository). We will move a few pages from Netlify now because of this change.

Also, found out the hard way that "Enterprise" pricing (i.e. call us and we'll charge you an opaque amount based on whatever we think you can afford pricing) starts at 7 users. Vercel is not much better at 10 users, and they hide it deep within their pricing table behind a tooltip so you're not likely to realize this until it's too late. Cloudflare Pages doesn't charge per user but limits concurrent builds which can…

+1, looking for answers too.

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

#64

Post by notpushkin »

cjlm wrote: post #54
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…

Check out Eleventy[0] - written in JavaScript but largely no-nonsense with (relatively) few dependencies. [0] https://www.11ty.dev/

We've used Eleventy on a project a year ago and it was super easy to get running. It is not tied to any frontend framework (but if you want an interactive part on the page, you will have to set it up yourself, in contrast to Astro's Islands [1]).

My overall impression is: use 11ty for a first version, use Astro when you have more moving parts on the frontend.

Little bonus for those coming from Python background (like me): 11ty uses Nunjucks, which is a JavaScript port of Jinja, so the templating system feels right at home.

[1]: https://docs.astro.build/en/concepts/islands/

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

#65

Post by weego »

root_axis wrote: post #61
game-of-throws wrote: post #45

Earlier quoted context omitted.

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.

> Use any SSG not written in javascript and you'll be fine. Commonly stated but not actually true. For example: https://github.com/getzola/zola/blob/master/Cargo.lock https://github.com/gohugoio/hugo (scroll to the bottom of the README)

To be fair in every day use Hugo is a single very portable binary

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

#66

Post by skrtskrt »

root_axis wrote: post #61
game-of-throws wrote: post #45

Earlier quoted context omitted.

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.

> Use any SSG not written in javascript and you'll be fine. Commonly stated but not actually true. For example: https://github.com/getzola/zola/blob/master/Cargo.lock https://github.com/gohugoio/hugo (scroll to the bottom of the README)

Yeah Hugo has the advantage that dep management for Go is 10000x simpler than JS, Ruby, Python, etc., particularly when you are someone who doesn't work in that language regularly.

Plus as sibling comment says you usually don't do anything but install hugo, `hugo [command]`

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

#67

Post by ASalazarMX »

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…

Hugo (https://gohugo.io) maybe? I tried it for a small static site about internal documentation, and I'm very glad I did. The hardest part was reading the documentation, the installation, content generation and rebuilds were painless.

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

#68

Post by skrtskrt »

ASalazarMX wrote: post #67
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…

Hugo ( https://gohugo.io ) maybe? I tried it for a small static site about internal documentation, and I'm very glad I did. The hardest part was reading the documentation, the installation, content generation and rebuilds were painless.

The hardest part of Hugo for me was creating my theme from scratch (docs are eh on this but I found some good 3rd party tutorials) but after that it's been an absolute breeze.

After spending a little time understanding Go templating it is really beautiful

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

#69

Post by lucideer »

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…

Repeating the Hugo recommendation.

1. I've not yet had issues building old sites

2. Just in case you anticipate such issues you can just check the binary into your repo

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

#70

Post by swyx »

foofoobar wrote: post #9
jackconsidine wrote: post #3

I've used Astro my company's landing page for the past year or so [0]. We write blog posts in Notion and port them right to the site and the experience has been fantastic. There are a few understanding quirks with regard to using React etc within Astro (it's SSR'd unless you add the "client" attribute, and counter-intuitively the Component Lifecycle doesn't run the same). For client landing pages, we'll use Astro too…

Netlify recently changed their pricing structure, so if you are using Netlify CMS (or just Netlify Identity) with a private repo, every contributor to the repository (committer) will be charged as full pro seat. This can get really expensive if you have a few users working with the CMS (and thus committing content to the repository). We will move a few pages from Netlify now because of this change.

netlify pricing changes for those who want the source https://www.netlify.com/blog/announcing-changes-to-netlify-p...

and for private orgs https://www.netlify.com/pricing/private-org-repo-faq/

Post reply on HN