withamplifier.com

The Bot Ships The Site

Session → Story → Site, on autopilot

The Showcase

Amplifier's work goes live at withamplifier.com — and almost nobody publishes it by hand

withamplifier.com is a real Next.js 14 web app (React 18, TypeScript, Tailwind, Three.js) and a living public showcase for Amplifier session output. It returns HTTP 200 today on its own custom domain.

The surprising part isn't the site. It's who does the publishing.

The Proof

A CI/CD bot authored the overwhelming majority of the repo

Across the whole withamplifier history, 764 of 911 commits — 83.9% — were authored by github-actions[bot], not people. The humans are the minority.

Why hand it to a bot at all? Because the work doesn't hand-scale.

764

of 911 commits by github-actions[bot]

83.9%

of all commits are automated

133

commits by Alex Lopez, the human lead

750

bot commits are one identical action

The Problem

Sessions produce decks faster than any human could publish them

The source repo already holds 212 HTML decks. Hand-copying, restyling, cross-linking and cataloguing 200+ artifacts on every change doesn't scale — and unpublished work is invisible work.

So the job was split across two repos.

212 HTML decks in the source docs/ directory to keep published

Every deck needs CSS injection, cross-links, and metadata regenerated

Invisible until shipped — without a surface layer, session output stays hidden

Two Repos, One Job

One repo makes the story; the other is the site that shows it

amplifier-stories turns Amplifier sessions into polished HTML decks (via its storyteller agent) into docs/. withamplifier is the Next.js site that consumes that repo's docs as its content source.

Between them runs the bot — every six hours.

Story

ramparte/amplifier-stories

Storyteller agent generates polished HTML decks into docs/ from Amplifier sessions.

Site

anderlpz/withamplifier

Next.js 14 app that syncs those decks and serves them at withamplifier.com.

The Loop

Every 6 hours the bot syncs, transforms, catalogs, and commits

sync-decks.yml runs on cron 0 */6 * * *. It pulls decks from amplifier-stories, transforms them, regenerates the metadata catalog, and auto-commits as github-actions[bot] — no human in the loop.

Committing isn't publishing, though. The next step ships it.

1

Pull — checks out ramparte/amplifier-stories docs (sparse)

2

Transform — injects CSS + "More Amplifier Stories" links into each deck

3

Catalog — runs generate-deck-metadata.js to rebuild the deck list

4

Commit & push — as github-actions[bot]: "sync and transform decks"

Commit → Deploy

A successful sync automatically chains into a live deploy

deploy.yml triggers on the sync workflow completing successfully. It builds the Next.js app, uploads a Pages artifact, and deploys via actions/deploy-pages@v4 to the custom domain in the CNAME — withamplifier.com.

Source to live domain, hands-free. So what does that buy?

Sync → Build → Deploy → Live

Triggered by workflow_run when the sync concludes success

Deploys to GitHub Pages on custom domain withamplifier.com

HTTP 200 live today at withamplifier.com

The Payoff

A self-maintaining showcase: the bot is the workforce, humans own the app

205 decks in the auto-generated catalog, maintained for 172 continuous days at 99% pipeline reliability. Human effort (led by Alex Lopez) moves up to brand, design, and the site app itself.

The lesson generalizes past this one site.

PIPELINE ACTIVE — RUNS EVERY 6H

205

decks in the auto-generated catalog

172

days of continuous automation

99/100

recent sync runs succeeded

6h

cadence — the bot never sleeps

The Pattern

Make publishing a pipeline, not a chore

When a bot does the routine work — the 750 identical sync-and-transform commits — human attention compounds on what only humans can do: brand, design, and the product itself.

Session → Story → Site. The bot ships the site.

Sources

Research Methodology

Data as of: July 21, 2026

Feature status: Site LIVE (HTTP 200); pipeline ACTIVE (runs every 6h).

Repos: anderlpz/withamplifier (Site, public) ← ramparte/amplifier-stories (Story).

Research performed:

Commit share: git rev-list --count HEAD (911) + git shortlog -sn --all (764 github-actions[bot])
Bot action breakdown: git log --author="github-actions" --format='%s' | sort | uniq -c | sort -rn (750 identical)
Pipeline: cat .github/workflows/sync-decks.yml (cron 0 */6 * * *) and cat .github/workflows/deploy.yml
Catalog size: ls public/stories/decks/*.html | wc -l (212) + grep -cE 'title:' lib/deck-data.ts (205)
Reliability: gh run list --repo anderlpz/withamplifier --workflow=sync-decks.yml --limit 100 (99 success / 1 failure)
Continuity: git log --author='github-actions' --format='%ci' (2026-01-30 to 2026-07-21 = 172 days)
Live check: curl -s -o /dev/null -w "%{http_code}" https://withamplifier.com (200); cat public/CNAME
Stack: cat package.json (Next.js 14, React 18, TypeScript, Tailwind, Three.js 0.182)

Gaps: Real-world page-view / traffic numbers are not verifiable from the repo and are not claimed. The 172-day figure spans first-to-latest bot commit and does not assert zero gaps.

Primary contributors: github-actions[bot] (764 commits, 83.9%); Alex Lopez (133, human lead); Samuel Lee (8); momuno (4); anderlpz (2).