You don't need to run and build the site every time. Jekyll crawls to a halt on my website if I build it locally when I write. So, I just write in Obsidian, iAWriter, or Sublime Text. The articles are sometimes un-finished, to-be-edited. I push them and Github does the magic.

Now, replace Jekyll with any SSG and let a tool handle the build (Netlify, Vercel, CloudFlare Pages).

For your specific tweet/comment like post, I remember deploying quite a few instances of something called "P2" from WordPress for internal department updates, team updates etc.

WordPress P2: https://wordpress.org/themes/p2/

I do the same with Jekyll. I have tweaked my theme so that it looks great even on very short posts without title or image, and it works fine.

Got the same issue. Found those static site generators somewhat unwieldy to handle, especially for non-tech people. I worked on two different approaches:

* A desktop app for creating static blogs, local preview, generates assets, optional deploy directly to Vercel. [1]

* A cron job which reads the paragraphs of a Notion page. Currently only generates an Atom/RSS feed from each paragraph. Inspired by [2], currently no source available.

[1] https://www.project-daily.com

[2] https://brandur.org/atoms

Not sure it's that bad. Small, static text with minimal includes might be 300 bytes of overhead. What's the harm in having a few thousand of these?

I have a single HTML file with notes like this on my site. it's not the prettiest but literally no one else is going to read it anyways.

> So how well is a static site generator suited for this? Do I want to build thousands of pages every time I start the site locally?

Take a look at Astro[1]. Astro comes with a development server and it will not build a thing unless you want it to.

Also, in contrast to classic static site generators Astro relies on components instead of templates which reduces cognitive complexity dramatically (to me anyway).

[1]: https://astro.build/

Yeah, I've been eyeing Astro, and wondering whether I like it or Eleventy more. What worries me about Astro is that its internals must be very complex, since it's trying to support all the component frameworks and libraries out there. As a result, I heard some complaints about unaccountable problems with my favorite component library, Lit. I am also very surprised that the choice between SSG and SSR mode in Astro seems to be all-or-nothing, rather than a configuration that would allow SSG-ing some pages and SSR-ing others.

But yeah, its syntax, with an out-of-the-box support of typescript, looks more enticing than Eleventy's nunjucks or webc, or its serverless plugin. Good to know that Astro doesn't prerender all pages in dev mode either.

They now have an experimental flag that allows some pages to be SSR and others SSG. So this is now possible

The way I've done it for my own notes (in a custom-made static-blog generator) is to have a template dedicated to "notes" and some over-engineered pipeline for similarly small datasets [1].

[1] https://lucasdicioccio.github.io/dhall-section-demo.html