chore: remove redundant demo build (dist-demo) (#3)

Each public repo's main dist now serves as its own demo, so the separate demo build is gone: drop the build:demo script, the CI 'Build (demo)' step, and the IS_DEMO/--mode demo machinery in codex.ts. The demo:true content flag is kept — the private repo (contracodex) uses it to hide the shared demo campaigns; getCampaigns now simply filters !demo. No behavior change (contracodex still builds only its non-demo campaigns).

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: flippelt

.github/workflows/ci.yml

@@ -21,8 +21,6 @@ jobs:
         run: npm run check
       - name: Build (main)
         run: npm run build
-      - name: Build (demo)
-        run: npm run build:demo
       - name: Smoke — assert key files generated
         run: |
           test -f dist/index.html || (echo "missing dist/index.html"; exit 1)

package.json

@@ -6,7 +6,6 @@
   "scripts": {
     "dev": "astro dev",
     "build": "astro build",
-    "build:demo": "astro build --mode demo --outDir dist-demo",
     "check": "astro check",
     "preview": "astro preview",
     "astro": "astro",

src/content.config.ts

@@ -21,8 +21,10 @@ const campaigns = defineCollection({
       cover: z.string().optional(),
       coverArt: image().optional(),
       order: z.number().default(0),
-      // Include this campaign in the public demo build (GitHub Pages). Your
-      // private campaigns stay off the demo unless you opt them in.
+      // Marks a campaign as a shared demo/showcase campaign. demo:true hides it
+      // from the build — used by the private repo (contracodex) to keep the
+      // demo campaigns off its site. This public repo leaves its own campaigns
+      // unflagged, so its main build IS the public demo.
       demo: z.boolean().default(false)
     })
 })

src/lib/codex.ts

@@ -52,16 +52,15 @@ export function entryHref(entry: Entry) {
 
 const visible = (e: Entry) => import.meta.env.DEV || !e.data.draft
 
-// The Pages build runs with `--mode demo`: it publishes ONLY the campaigns
-// opted in with `demo: true`. The main build (Netlify) is the inverse — it
-// publishes everything EXCEPT the demo campaigns, so the two deploys show
-// disjoint sets and the demo campaigns never appear on the main site.
-export const IS_DEMO = import.meta.env.MODE === 'demo'
-
+// Campaigns flagged `demo: true` are hidden from the build. This repo's own
+// build IS the public showcase (its campaigns aren't flagged, so they show);
+// the private repo (contracodex) flags the shared demo campaigns so only its
+// real content appears. There's no separate demo build anymore — the main
+// dist of each public repo serves as its demo.
 export async function getCampaigns(): Promise<Campaign[]> {
   const all = await getCollection('campaigns')
   return all
-    .filter((c) => (IS_DEMO ? c.data.demo : !c.data.demo))
+    .filter((c) => !c.data.demo)
     .sort((a, b) => a.data.order - b.data.order || a.data.name.localeCompare(b.data.name))
 }