[rednafi]

This pattern of:

1. polling for external changes somewhere

2. updating some pages on a static site (by incorporating the changes from step 1) and rebuilding it

is incredibly powerful. It allows us to make a static site behave almost like a read-only dynamic one. There needs to be a name for this—it’s hard to discuss it without one.

[ggpsv]

A bit like PESOS (Publish elsewhere, syndicate own site). I do this when archiving my Mastodon posts in my own static site [0].

[0]: https://garrido.io/notes/archiving-and-syndicating-mastodon-...

[rednafi]

PESOS is pretty good. I was aware of POSSE but not PESOS.

[rmnclmnt]

This pattern is used all over the place, and for good reason (especially when people get their minds on combining CI/CD and static deployments).

Simon Willison groked the name « Baked Data »: even though it was in the context of Datasette (which requires a backend to run but the SQLite db is embedded and read-only), it is pretty safe the term can be applied for static websites also!

[Macha]

Hasn't it already had a name for years? A headless CMS

[dgl]

One name for it is PESOS[1] ("Publish Elsewhere, Syndicate (to your) Own Site"), although that doesn't necessitate it be static, but requiring it be static is mixing the implementation with the user experience anyway.

[1]: https://indieweb.org/PESOS

[gwern]

Why is that not just 'transclusion' https://en.wikipedia.org/wiki/Transclusion ?

Except a special-case of transclusion: high latency and compile-time only. As opposed to doing it with JS dynamically; if Pinboard had an API, or even simply doesn't block frames with HTTP headers, you could simply dynamically call from the static site page to the other site, load the relevant HTML, and present it transcluded into the static site page. (This is how Gwern.net does a lot of stuff: everything from the Wikipedia/Github popups to transcluding other pages.)

[syndicatedjelly]

Fetch?