edda

Edda is a command-line tool for building and publishing documentation sites written in MDX, positioned as "knowledge docs for agents" with a git-native workflow that publishes on merge. The README presents it as the same approach used for every docs site on its platform, including captain.blode.md. Installation is global via npm: `npm install -g edda-docs`. The quickstart flow is: `edda login` to authenticate with GitHub in the browser (no API key to manage manually), `edda new docs --template starter` to scaffold a docs site into a directory, `edda dev` to serve it locally at localhost:3030 with reload on edit, and `edda push docs` to deploy. A deployed site goes live on its own blode.md subdomain, with name, navigation and theme taken from the docs.json file that `edda new` generates. The command set covers authentication (`login`), scaffolding (`new`, with `minimal` or `starter` templates), local preview (`dev`), config checking (`validate`), deployment (`push`), account listing (`projects`), and PostHog analytics management (`analytics` with `get`, `set posthog <key>`, `unset posthog`). For agent use, the README documents an installable slash command for Claude Code or any skills.sh-compatible agent via `npx skills add mblode/edda -g --all -y`, after which scaffolding and deployment can be driven in plain language, e.g. `/edda new my-project --template starter` and `/edda push docs/ --project my-project`. CI and automation support is a notable focus. Environment variables include EDDA_API_KEY / BLODEMD_API_KEY (used ahead of a stored login session so CI needs no interactive login), EDDA_PROJECT / BLODEMD_PROJECT as the default for `--project`, and EDDA_API_URL / BLODEMD_API_URL for the API origin. Exit codes are documented as stable and branchable: 0 success, 1 error, 2 cancelled (including a declined prompt), 3 invalid input or config, 4 authentication required, 5 network failure. With `--json`, failures are emitted as a single stdout line shaped `{"error":true,"code":"AUTH_REQUIRED","message":"...","hint":"..."}`, and the README advises branching on the stable `code` field rather than the human-oriented `message`. Additional notes state that Node.js 24 is required, that `push`, `validate` and `projects` accept `--json`, that `push` reads project, API key and branch values from the environment for non-interactive CI deployment, and that installing the GitHub App from a project dashboard enables automatic deployment on every push to a branch. The project is MIT licensed and authored by Matthew Blode.