The Atlas
A live map of this blog. Every page is a node, coloured by the part it plays; every internal link is a thread between them. It is built from the writing itself, so it cannot drift out of date.
For the curated, hand-written tour of the ideas, see Maps. For the thinking behind a map like this, The Language of Sound and the dev-log I Built a Live Map of My Own Blog.
How to read it
The map opens already settled (its layout is computed when the site is built), framed to your screen. Then it is yours: hover any node to light up everything it links to, click a node to inspect it (its role, its date, what it links out to in gold, and what links back to it in teal), and click Open page to read it. Drag to pan, scroll or pinch to zoom, use the buttons to zoom and refit, and the ♪ toggles a little synthesized sound.
The bright, labelled anchors carry the structure. Pillars (3) are cornerstone ideas promoted to their own clean URL. Cornerstones (16) anchor a cluster from a dated post. Hubs (7) are curated landing pages that point out to a cluster. Categories (6) are the archives. Everything else is the field of ordinary posts, coloured by kind.
Questions this map answers
- Which page is the most connected?
Four Films From Code: Stick Figures, Chiptunes, and the AI Director's Chair, with 22 other posts linking to it. That is the gravitational centre of the site. - Which cornerstone is best supported?
Antifragile: Things That Gain from Disorder by Nassim Nicholas Taleb, with 14 inbound links holding it up. - What is orphaned?
Nothing: every cornerstone has at least one post linking to it. - Where does a new reader start?
The busiest hub is AI Development, which points out to 29 pages. Follow its threads outward.
How it works
A build step reads every published page, tags each with the one role it plays, and walks the posts for the links between them. Pages become 248 nodes; links become 838 edges; the whole thing is written to one file this page reads. No database, no server: the site already contains the graph, and the script just makes it look at itself, every time the site is rebuilt. The full reasoning is in the dev-log.