Update release script and CI process for Pages deployment for new Astro site

Author: grega

.githooks/pre-commit

@@ -7,9 +7,9 @@ if git diff --cached --name-only | grep -q '^src/'; then
   git add hdi
 fi
 
-# Format staged site/ files with Prettier
-SITE_FILES=$(git diff --cached --name-only --diff-filter=ACMR | grep '^site/')
+# Format staged website/ files with Prettier
+SITE_FILES=$(git diff --cached --name-only --diff-filter=ACMR | grep '^website/')
 if [ -n "$SITE_FILES" ]; then
-  npx --prefix site prettier --write $SITE_FILES
+  npx --prefix website prettier --write $SITE_FILES
   echo "$SITE_FILES" | xargs git add
 fi

.github/workflows/ci.yml

@@ -65,22 +65,25 @@ jobs:
         with:
           node-version: 24
 
+      - name: Build hdi from source
+        run: ./build
+
       - name: Install dependencies
-        working-directory: site
+        working-directory: website
         run: npm ci
 
       - name: Install Playwright browsers
-        working-directory: site
+        working-directory: website
         run: npx playwright install chromium --with-deps
 
       - name: Run Playwright tests
-        working-directory: site
+        working-directory: website
         run: npx playwright test
 
       - name: Upload test report
         if: ${{ !cancelled() }}
         uses: actions/upload-artifact@v7
         with:
           name: playwright-report
-          path: site/playwright-report/
+          path: website/playwright-report/
           retention-days: 7

.github/workflows/pages.yml

@@ -21,9 +21,25 @@ jobs:
       url: ${{ steps.deployment.outputs.page_url }}
     steps:
       - uses: actions/checkout@v6
+
+      - uses: actions/setup-node@v6
+        with:
+          node-version: 24
+
+      - name: Build hdi from source
+        run: ./build
+
+      - name: Install website dependencies
+        working-directory: website
+        run: npm ci
+
+      - name: Build Astro site
+        working-directory: website
+        run: npm run build
+
       - uses: actions/configure-pages@v6
       - uses: actions/upload-pages-artifact@v4
         with:
-          path: site
+          path: website/dist
       - id: deployment
         uses: actions/deploy-pages@v5

.gitignore

@@ -26,6 +26,9 @@ playwright/.auth/
 # build output
 dist/
 
+# auto-generated website data (produced by website/generate-data.sh)
+website/src/data/data.js
+
 # generated types
 .astro/
 

.prettierignore

@@ -8,4 +8,4 @@ bench/results.csv
 bench/results.svg
 
 # Generated test files  
-site/playwright-temp/
+website/playwright-temp/

README.md

@@ -172,6 +172,10 @@ vhs ./demo/demo.tape
 
 This outputs `demo.gif` from the tape file.
 
+## Website
+
+See `website/README.md` for instructions on running the demo website at https://hdi.md
+
 ## Benchmarking
 
 Static benchmark READMEs in `bench/` (small, medium, large, stress) exercise parsing path at different scales. Run benchmarks with:
@@ -186,7 +190,7 @@ Benchmarks run automatically during `./release` and are recorded in `bench/resul
 
 ## Publishing a new release
 
-The `release` script bumps the version in `src/header.sh`, rebuilds `hdi`, regenerates `site/data.js`, commits, tags and pushes. The `release` Actions workflow will automatically build and publish a GitHub release when the tag is pushed, and the demo site is redeployed. The script then prints the `url` and `sha256` values to update in the [homebrew-tap](https://github.com/grega/homebrew-tap) repo (`Formula/hdi.rb`).
+The `release` script bumps the version in `src/header.sh`, rebuilds `hdi`, commits, tags and pushes. The `release` Actions workflow will automatically build and publish a GitHub release when the tag is pushed, and the demo site is built and deployed via the `pages` workflow. The script then prints the `url` and `sha256` values to update in the [homebrew-tap](https://github.com/grega/homebrew-tap) repo (`Formula/hdi.rb`).
 
 ```bash
 ./release patch          # 0.1.0 → 0.1.1

release

@@ -63,24 +63,17 @@ echo "Releasing: $current → $new ($tag)"
 
 sed -i.bak "s/^VERSION=\"$current\"/VERSION=\"$new\"/" "$SRC_HEADER" && rm -f "$SRC_HEADER.bak"
 
-# Update site version references
-sed -i.bak "s/v$current/v$new/" "$SCRIPT_DIR/site/index.html" && rm -f "$SCRIPT_DIR/site/index.html.bak"
-sed -i.bak "s/v$current/v$new/" "$SCRIPT_DIR/site/demo.html" && rm -f "$SCRIPT_DIR/site/demo.html.bak"
-
 # Rebuild hdi from source
 "$SCRIPT_DIR/build"
 
-# Regenerate site data from fixtures
-bash "$SCRIPT_DIR/website/generate-data.sh"
-
 # Run benchmarks against the new version
 if [[ -x "$SCRIPT_DIR/bench/run" ]]; then
   echo ""
   "$SCRIPT_DIR/bench/run" --log
   "$SCRIPT_DIR/bench/chart"
 fi
 
-git add src/header.sh hdi bench/results.csv bench/results.svg site/index.html site/data.js
+git add src/header.sh hdi bench/results.csv bench/results.svg
 git commit -m "Bump version to $new"
 git tag "$tag"
 git push origin HEAD --tags

website/README.md

@@ -2,6 +2,16 @@
 
 Information page and interactive demo of the `hdi` CLI, built with [Astro](https://astro.build).
 
+## Prerequisites
+
+The website depends on demo data generated from the `hdi` CLI. Before running the dev server or building, make sure `hdi` is built from the project root:
+
+```bash
+./build
+```
+
+Data generation happens automatically via `predev` and `prebuild` npm scripts, so you don't need to run `generate-data.sh` manually.
+
 ## Local development
 
 Install Node via [asdf](https://asdf-vm.com/) (see `.tool-versions`):
@@ -86,7 +96,7 @@ npm run astro -- --help
 
 ## Regenerating data
 
-`src/data/data.js` is auto-generated from the fixture READMEs using `hdi --json`. To regenerate after changing fixtures or the parser locally, run from the `website/` directory:
+`src/data/data.js` is auto-generated from the fixture READMEs using `hdi --json` and is not committed to git. It is regenerated automatically when running `npm run dev` or `npm run build`. To regenerate manually, run from the `website/` directory:
 
 ```bash
 ./generate-data.sh

website/generate-data.sh

@@ -1,5 +1,5 @@
 #!/usr/bin/env bash
-# generate-data.sh - Generate site/data.js from fixture READMEs using `hdi --json`
+# generate-data.sh - Generate src/data/data.js from fixture READMEs using `hdi --json`
 set -euo pipefail
 
 SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
@@ -21,7 +21,7 @@ VERSION=$("$HDI" --version | awk '{print $2}')
 
 # Start output
 {
-  printf '// Auto-generated by site/generate-data.sh - do not edit manually\n\n'
+  printf '// Auto-generated by website/generate-data.sh - do not edit manually\n\n'
   printf 'export const PROJECTS = [\n'
 
   first_project=true

website/package.json

@@ -6,7 +6,9 @@
     "node": ">=22.12.0"
   },
   "scripts": {
+    "predev": "bash ./generate-data.sh",
     "dev": "astro dev",
+    "prebuild": "bash ./generate-data.sh",
     "build": "astro build",
     "preview": "astro preview",
     "astro": "astro",