Framework & Blueprint
The framework is the structure. A blueprint is one unit written in it. Read →
Overview
Eidos is a way to define a product in markdown: an app, a book, a study, anything you set out to make. One file is the complete source of truth for one unit of it, as true of something planned as of something long shipped.
The files are plain .md in your repository. No lock-in, and no service you need. One command, eidos, does the mechanical work.
The CLI, the desktop app, the standard, every plugin, working offline, git, and your own agents are free, with no account. Eidos online adds sync and live editing; reading and commenting there are free and unlimited, and you pay only to edit online past the free plan or for extra storage. Plans → · Pricing →
Where to start
Section titled “Where to start”Quick StartInstall the CLI, create a project, write your first blueprint.
Why Eidos ExistsThe problem it solves, and when not to use it.
Use CasesA software team, a solo builder with agents, a studio, a book: who it is for and what it speeds up.
The CLIWhat eidos does, command by command.
The four ideas
Section titled “The four ideas”Collections & Blueprints
A collection is a folder of blueprints of one kind. A blueprint is one file: properties on top, a body below. Read →
Templates & Variants
A template is the body a collection’s blueprints follow. A variant is one of a collection’s templates. Start light, grow into full. Read →
Properties
The frontmatter contract: four standard properties, plus whatever your framework adds. Read →
This site and the standard
Section titled “This site and the standard”These pages teach Eidos. The standard is one file, EIDOS.md. Where the two disagree, the standard wins.