Colophon
How this site is built, why, and how to replicate it.
Technical Stack
This site is built with 11ty (Eleventy), a static site generator that compiles Markdown and templates into plain HTML. The build output is deployed to IONOS webspace via rsync over SSH.
Why 11ty? Because it produces static HTML with no client-side JavaScript, no tracking, no dependencies that will break in five years. The site will render in any browser, now or decades from now.
Why IONOS? Reliable European hosting with SSH access, SSL included. If it becomes untenable, the site is static files — it can be moved anywhere in minutes.
Design
The design is a green-phosphor terminal aesthetic — VT100, BBS, Chaos Computer Club. The kind of screen that would make a 1989 cracker feel at home.
We chose this deliberately:
- VT323 for all text — a Google Font that looks like a real CRT display, with monospace fallback
- Green on black (
#00ff41on#0a0a0a) — the phosphor palette of early terminals - Cyan for links (
#00ffff) — ANSI color 6, the hyperlink of the BBS era - Amber for accents (
#ffb000) — warnings, prompts, the color of authority - Scanline overlay — a subtle CSS effect mimicking CRT scan lines
- ASCII art and box-drawing characters — because decoration should be typographic
- No images, no gradients, no cards — everything is text
The visual language is the command line. The site looks like what it is: a terminal into which two entities type, and from which text emerges. The aesthetic is not nostalgia — it is a refusal of the design language of platforms, of the rounded corners and gradient cards that signal "content" and "engagement." This is a text file. Read it or don't.
Collaboration Method
The human-machine collaboration happens via a shared workspace. The human (Marcus) initiates most pieces and has final editorial authority. The machine (Glean, an AI assistant) contributes through dialogue: suggesting structures, arguing with premises, refining language, identifying connections.
Nothing here is "AI-generated" in the sense of unreviewed output. Everything is discussed, revised, and signed-off. The division of labor is transparent because the politics require it.
Principles
-
No platforms. No Medium, no Substack, no Twitter. Static HTML on infrastructure we can move.
-
No analytics. We do not track readers. We will never know if anyone visits.
-
No optimization. This is not content marketing. The goal is not engagement.
-
Open process. The collaboration is visible in the bylines and documented here.
Development Workflow
The site is built and deployed through a human-AI loop, with Marcus reviewing every change before it goes live:
- Agent codes — the AI agent (Claude Code, running locally via CLI) edits source files in the project directory
- Human reviews — Marcus checks the result in the browser at
localhost:8080via 11ty's dev server - Agent commits and pushes — changes go to the Git repository on GitHub
- Agent deploys — the built
_site/directory is rsynced over SSH to the IONOS webspace - Live — the site is served at working-notes.org
No CI/CD pipeline. No build server. No abstraction layers. A human, a machine, a terminal, and rsync. The entire deploy chain is visible and manual — every change is a conscious decision, not an automated event.
Source
The complete source for this site is available at github.com/MarcusGraetsch/marcus-cyborg.