feat: merge the blog repo into this one, build content locally

Content now lives in content/, brought over with its full git history so
post dates survive — created_date comes from each file's first commit, and a
plain copy would have reset nine months of publication dates to today.
Verified: all 8 posts and 9 svgs regenerate with byte-identical dates and
ordering against the manifest the old pipeline produced.

What this removes:
- the cross-repo repository_dispatch and its PAT
- the jsDelivr purge step and the ~12h CDN staleness it worked around
- the daily cron, which only existed to catch content changes here
- uncachedUrl() in both build scripts

The build now reads everything off disk instead of over the network, so it
works offline and can't be broken by an upstream outage. Assets are served
from this repo by Pages; og:image is absolutised for unfurlers.

scripts/generate-manifest.mjs ports the blog repo's Python indexer, including
the hybrid history scan (fast global pass, --follow fallback for renamed
files) that makes those dates correct.

Also: 404.html no longer answers an unknown URL with a full post listing —
it renders a real not-found instead. .nojekyll stops Pages filtering
content/ through Jekyll now that raw .md and assets are served from there.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: jebin2

.github/workflows/sitemap.yml

@@ -1,19 +1,13 @@
 name: Build site
 
-# Posts live in the blog repo, so prerendered pages and the sitemap go stale
-# without anything changing here. Rebuild daily, on demand, and whenever the
-# build inputs change.
+# Content lives in this repo now, so a push is the only thing that can change
+# the built output. No cron, no cross-repo trigger.
 on:
-  schedule:
-    - cron: '0 3 * * *'
   workflow_dispatch:
-  # Sent by the blog repo right after it publishes, so a new post is
-  # prerendered in about a minute instead of waiting for the daily run.
-  repository_dispatch:
-    types: [content-updated]
   push:
     branches: [main]
     paths:
+      - 'content/**'
       - 'config.json'
       - 'js/utils.js'          # slug rule — changing it moves every post URL
       - 'scripts/**'
@@ -32,7 +26,7 @@ jobs:
     steps:
       - uses: actions/checkout@v4
         with:
-          # Full history so lastmod can come from each page's last commit
+          # Full history: post dates come from each file's commits
           fetch-depth: 0
 
       - uses: actions/setup-node@v4
@@ -43,6 +37,9 @@ jobs:
       # client-side rendering of the same markdown agree.
       - run: npm install --no-save marked@9.1.6
 
+      - name: Index posts
+        run: node scripts/generate-manifest.mjs
+
       - name: Prerender posts
         run: node scripts/prerender.mjs
 
@@ -51,12 +48,12 @@ jobs:
 
       - name: Commit if changed
         run: |
-          if git diff --quiet -- sitemap.xml writing/ && [ -z "$(git status --porcelain writing/)" ]; then
+          if [ -z "$(git status --porcelain content/manifest.json writing/ sitemap.xml)" ]; then
             echo "nothing changed"
             exit 0
           fi
           git config user.name  "github-actions[bot]"
           git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
-          git add -A sitemap.xml writing/
-          git commit -m "chore: rebuild prerendered posts and sitemap"
+          git add -A content/manifest.json writing/ sitemap.xml
+          git commit -m "chore: rebuild manifest, post pages and sitemap"
           git push

.nojekyll

@@ -3,57 +3,57 @@
 The website — **https://www.voidall.com**. Static, no framework, no bundler, no runtime
 dependencies. Plain HTML, one stylesheet, and native ES modules.
 
-The words live in a separate repo, [jebin2/blog](https://github.com/jebin2/blog). This repo
-holds everything that displays them, plus a small build that turns each post into a real
-static page.
+Posts live in `content/` in this same repo. Writing and publishing are one push.
 
 ---
 
-## How content gets here
+## Publishing a post
+
+Create a folder under `content/` and a `.md` file inside it with **the same name**:
 
-```mermaid
-flowchart LR
-    A[jebin2/blog<br/>push a post] -->|repository_dispatch| B[Build site workflow]
-    C[daily 03:00 UTC<br/>backup] -.-> B
-    B --> D[prerender.mjs<br/>writing/slug/index.html]
-    B --> E[generate-sitemap.mjs]
-    D --> F[commit]
-    E --> F
-    F --> G[GitHub Pages]
+```
+content/C/Bitfields/Bitfields.md   ✅ indexed as a post
+content/C/Bitfields/header.png     ✅ image, referenced as ![](header.png)
+content/C/Bitfields/notes.md       ❌ ignored — name doesn't match the folder
 ```
 
-`.github/workflows/sitemap.yml` (“Build site”) runs on four triggers:
+Push, and the build does the rest.
 
-| Trigger | When |
-|---|---|
-| `repository_dispatch` | the blog repo publishes — arrives in ~2s |
-| `schedule` | daily 03:00 UTC, so a missed dispatch still gets picked up |
-| `workflow_dispatch` | manual run |
-| `push` | `config.json`, `js/utils.js` or `scripts/**` changed |
+```mermaid
+flowchart LR
+    A[push content/] --> B[generate-manifest.mjs]
+    B --> C[prerender.mjs<br/>writing/slug/index.html]
+    C --> D[generate-sitemap.mjs]
+    D --> E[commit]
+    E --> F[GitHub Pages]
+```
 
-It installs `marked`, prerenders every post, rebuilds the sitemap, and commits only if
-something actually changed.
+`.github/workflows/sitemap.yml` (“Build site”) runs on a push touching `content/`,
+`config.json`, `js/utils.js` or `scripts/**` — or manually. It indexes the posts,
+prerenders them, rebuilds the sitemap, and commits only if something actually changed.
 
 ### Running the build locally
 
 ```bash
 npm install --no-save marked@9.1.6
-node scripts/prerender.mjs        # writes writing/<slug>/index.html
-node scripts/generate-sitemap.mjs # writes sitemap.xml
+node scripts/generate-manifest.mjs # writes content/manifest.json
+node scripts/prerender.mjs         # writes writing/<slug>/index.html
+node scripts/generate-sitemap.mjs  # writes sitemap.xml
 ```
 
-Both read post content from the origin (`raw.githubusercontent.com`) rather than the CDN, so
-a build always sees the newest Markdown. Output is deterministic — dates are formatted from
-the literal date in the manifest, not the machine's timezone, so CI and a laptop produce
-identical files.
+The build reads everything off disk — no network — so it works offline and can't be broken
+by an upstream outage. Output is deterministic: post dates come from git history, and the
+displayed date is formatted from the literal date in the manifest rather than the machine's
+timezone, so CI and a laptop produce identical files.
 
 ---
 
 ## Layout
 
 | Path | |
 |---|---|
-| `config.json` | **the one file that says where content lives** — manifest, projects, links, and the base URL for post assets |
+| `content/` | **the posts**, their images, `data/*.json`, and the generated `manifest.json` |
+| `config.json` | the one file that says where content lives — now local paths under `/content/` |
 | `index.html` | post listing (home) |
 | `writing/index.html` | the writing listing |
 | `writing/<slug>/` | **generated** — one prerendered page per post |
@@ -62,6 +62,7 @@ identical files.
 | `css/style.css` | the whole stylesheet |
 | `js/*.js` | one module per page, plus shared helpers |
 | `scripts/*.mjs` | build scripts (Node, run in CI) |
+| `.nojekyll` | stops Pages filtering `content/` through Jekyll |
 | `sitemap.xml` | **generated** |
 
 ### The JavaScript
@@ -89,8 +90,8 @@ Prerendered post pages arrive with the article already in the HTML — a preview
 crawler or a reader with JS disabled all get the real post. JavaScript afterwards only adds
 the nav and footer, syntax highlighting, a read count, and (for admins) the share buttons.
 
-The listing pages are still client-rendered: they fetch `manifest.json` through jsDelivr and
-two `get_stats` calls from Supabase — one for the all-time sort, one for the 24-hour counter
+The listing pages are still client-rendered: they fetch `/content/manifest.json` from this
+same origin and make two `get_stats` calls to Supabase — one for the all-time sort, one for the 24-hour counter
 shown next to each title.
 
 If a post exists in the manifest but hasn't been prerendered yet, `/writing/<slug>/` 404s,
@@ -116,8 +117,11 @@ it from a CDN with `integrity` attributes; a stale hash blocks the script and po
 rendering on the fallback paths. Keep the pinned version in the workflow matching the one in
 the HTML so build-time and client-side rendering agree.
 
-**Post URLs come from post titles.** Renaming a post in the blog repo moves its URL and
-prunes the old directory — the old link dies with no redirect.
+**Post URLs come from post titles.** Renaming a post moves its URL and prunes the old
+directory — the old link dies with no redirect.
+
+**Post dates come from git history**, so never rewrite history under `content/` and never
+copy posts in without it. A plain copy resets every `created_date` to the day of the copy.
 
 **`isAdmin()` is a localStorage flag**, trivially set by anyone. It only reveals share and
 export UI, nothing privileged. Don't let it grow into gating anything that matters.

README.md

@@ -2,8 +2,8 @@
     "name": "jebin2",
     "github": "https://github.com/jebin2",
     "sponsor": "https://github.com/sponsors/jebin2",
-    "projects": "https://cdn.jsdelivr.net/gh/jebin2/blog@main/data/projects.json",
-    "links": "https://cdn.jsdelivr.net/gh/jebin2/blog@main/data/links.json",
-    "blog_manifest": "https://cdn.jsdelivr.net/gh/jebin2/blog@main/manifest.json",
-    "blog_base_url": "https://cdn.jsdelivr.net/gh/jebin2/blog@main/"
+    "projects": "/content/data/projects.json",
+    "links": "/content/data/links.json",
+    "blog_manifest": "/content/manifest.json",
+    "blog_base_url": "/content/"
 }