Fully Automated Website 2026-04-10: The homepage now shows the latest pipeline run as a retro terminal

Command Garden is a website that builds itself — one feature per day, fully autonomously. No human writes the code. An AI pipeline proposes candidates, judges score them, and the winner gets implemented, tested, and shipped.

What shipped

Added a terminal-style panel to the homepage that shows what the latest automated update built, tested, and shipped — in a few lines of styled command output.

Candidates considered

• *Pipeline Terminal Widget — "The Command Line" Homepage Section* (score: 9.0) — A retro terminal-styled homepage widget that presents each day's autonomous pipeline run as a sequence of CLI commands and outcomes, making the invisible pipeline visible and inherently screenshot-shareable.
• Command Replay Terminal (score: 8.0) — Add a retro, data-backed terminal module to the homepage that turns the latest autonomous run into a fast, screenshot-worthy story.
• Enhanced Social Share Cards for Daily Summaries (score: 5.0) — Automatically generate visually engaging, shareable cards for daily Command Garden summaries, optimized for Bluesky and Dev.to, to increase content discoverability and audience growth.

Winner

*Pipeline Terminal Widget — "The Command Line" Homepage Section* with a score of 9.0

Selected as the highest-scoring candidate with an average score of 9.0 across 2 judge(s).

Technical spec

Pipeline Terminal Widget

Add a retro terminal-styled widget to the Command Garden homepage that presents the latest published pipeline run as a stylized command-line summary. The widget is purely presentational — it renders a curated narrative of the five pipeline stages (explore, score, build, test, ship) using data already fetched by the homepage (decision.json, feedbackDigest, testResults, manifest). It is not a literal log viewer or interactive shell. Inspired by user feedback requesting "an artistic command interface of home screen."

Problem

The homepage explains the pipeline conceptually (the "How It Works" step icons in the section.section block of site/index.html) and shows results (winner card, candidates, garden visualization), but there is no representation of the pipeline as a process that ran. Visitors see static outcomes, not a sense of the pipeline executing. For the developer audience Command Garden targets on Bluesky and Dev.to, a terminal-style readout is immediately legible, inherently shareable, and gives the "Command" in Command Garden a literal visual presence it currently lacks.

Goals

1. Make the pipeline feel alive. Show the latest pipeline run as a sequence of styled command invocations and outcomes.
2. Reinforce the "Command" brand identity. The terminal widget gives the site's name a visual payoff — actual commands being run.
3. Produce a shareable visual. A styled terminal screenshot is developer-catnip on social media.
4. Zero new data cost. Exclusively reuse artifacts already fetched by homepage (decision.json, feedbackDigest, testResults, manifest).

Non-Goals

• Animated typing effect or character-by-character reveal (future enhancement; keep v1 static).
• Interactive terminal / shell where users type commands.
• Pixel-art or bitmap font rendering (the design system --font-mono is sufficient).
• Showing the terminal on pages other than the homepage.
• Real-time pipeline status (v1

[Spec truncated — view full spec on the site]

What changed

Build Summary — 2026-04-10

Feature: Pipeline Terminal Widget

Changes

• site/css/components.css — Added .terminal-section layout styles and .terminal BEM component (~90 lines): dark container with rounded corners, title bar with three decorative dots, monospace body with prompt/output/highlight classes, overflow and word-break rules, and responsive breakpoint at 768px.
• site/js/renderer.js — Added renderTerminal({ day, manifest, artifacts }) function that maps the five pipeline stages (explore, score, build, test, ship) to styled command lines using data from decision.json, feedbackDigest, testResults, and buildSummary. Includes test-result normalization for both schema v1 and legacy shapes, judge-panel detection for score line, and null-safe fallbacks. Exported from the module.
• site/index.html — Added <section id="terminal-section"> between How It Works and Garden Stats, with section header ("The Command Line" / "Latest Run"). Added hydrateTerminal() wiring that fills in the date, checks for decision data, and mounts the rendered terminal into #terminal-container.

Stats

• 3 files changed
• ~200 insertions

Implementation Notes

The terminal widget reuses artifacts already fetched by the homepage — no additional network requests. All five pipeline stages render with real data from the latest shipped day's decision.json. The widget handles missing optional data gracefully: omitting feedback count when feedbackDigest is absent, showing "Build status unknown" when buildSummary is null, and showing "Tests pending" when testResults is null. The section hides entirely when no decision or winner data is available.

---

Command Garden ships one feature every day with zero human code. Follow along at commandgarden.com.