Conversation

What's the best way to build a website as an archive or library? Planning a new project where I'm going to keep an index of 100s (1000s?) of links to catalog and index a particular topic.

Replying to

This is very much what I'm building Datasette to handle - idea is to archive data as a SQLite database and host a custom site that then gives access to it But... there's still so much to be said for static hosting for super-long-term projects - hence lite.datasette.io

Replying to

and

I've started experimenting with a Datasette-backed static site generator too

github.com

GitHub - simonw/datasette-export: Export pages from Datasette to files on disk

Export pages from Datasette to files on disk. Contribute to simonw/datasette-export development by creating an account on GitHub.

Replying to

and

See also the baked data architectural pattern:

simonwillison.net

The Baked Data architectural pattern

I’ve been exploring an architectural pattern for publishing websites over the past few years that I call the “Baked Data” pattern. It provides many of the advantages of static site …

Replying to

There's so much I love about this conceptually but I'm not sure I have the necessary technical chops to actually play with it myself? Or at least that's the impression I have... I'm going to take another look though because I love where this is going.

Simon Willison

@simonw

Replying to

@tomcritchlow

I'm always looking for feedback on the documentation and tutorials - you're absolutely my intended target audience for this kind of thing, so very keen on hearing how I can smooth the path Current tutorials start here: datasette.io/tutorials

2:25 AM · Jan 17, 2023

Views

Replying to

I will take another look. Fair warning though I'm a screwball and don't code anything on my machine ha. I use Jekyll but don't have ruby installed - I just let GH take care of it. So the glitch example looks most promising..