[raminf]

I'm a little confused. The baked-data model is so you DON'T have to generate a thousand static pages. But this solution does exactly that.

Not complaining, mind you. My kid is trying to learn HTML/CSS/JS and wants to put together a read-only website with a database backend. I'll be pointing him this way as an ootion once he's far enough.

But it's still puzzling to link it to baked-data. Maybe I'm missing something.

[captn3m0]

> bundling a read-only copy of your data alongside the code for your application, as part of the same deployment

You can see https://github.com/captn3m0/northwind for example, which bundles the entire database alongside the code in the _db/northwind.db file. While Simon considers it primarily for dynamic apps, you have the ability to build PWAs and other interesting apps with the baked data pattern.

I'm building blr.today for example using this.

[groby_b]

But it's still not baked data, no? The whole point of baked data is that you don't generate static pages for every item in the data set.

Mind you, it's great to have a Jekyll plugin to do that from sqlite, it's just confusing when you call it baked data.