Eidos

Every course tied to what the learner will be able to do.

One page per course: who it is for, what they will be able to do, the modules and the outcome each one serves, how learners prove it, and what the course does not teach. Learner pages and paths tie the catalog together, and the reasons a course changed stay with it.

Free for macOS, Windows, and Linux. No account, no subscription.

A course page for a fictional online school: who it is for, what is still to decide, three numbered outcomes, and modules that each name the outcome they serve, with the decisions made about the course listed beside it, one waiting to be confirmed.
A course page: the outcomes first, each module tied to one, and the calls made about the course beside it.

Sound familiar?

The course map was right the week you made it.

  1. The map lives somewhere else

    Outcomes in one file, the outline in another, the assessments in a third, and the alignment spreadsheet out of date by the second revision.

  2. Courses overlap

    Two courses teach the same lesson, a third assumes one nobody teaches, and a learner finds out halfway through.

  3. Nobody remembers why

    A module moved, a lesson was cut, the final project changed. A term later someone asks why, and the answer left with the person who made the call.

How it fits

Learners first, then courses, then paths.

Start from the Academy framework and the school gets a shape. Each course links the learners it is for and the courses that come first, with its level and its length, and moves from Idea to Outlined, In Production, Published, or Retired.

The School
Four pages: what you teach and why, how you teach, where the courses sell, and what one costs to make.
Learners
One page per kind of learner: where they start, what they need, and what done looks like for them.
Courses
Grouped by track: numbered outcomes, the modules and the outcome each serves, how learners prove it, and what it does not teach. An outline grows into the full page.
Paths
Courses in order, for one kind of learner, toward one outcome.
Catalog and Style Guide
Every course the way a learner sees it, and how a lesson is written and recorded.
The courses of a fictional school as a table grouped by track, Spreadsheets and Data Basics, with each course’s summary, status, the learners it is for, its level, and its length in hours.

What you will use most

The tools that keep a catalog in shape.

  • Blueprints

    Gaps, flagged

    The health check lists every course missing a section its template asks for, so a course with no How They Prove It or no Not This Course never hides.

  • Decisions

    Why a course changed

    Cut a lesson, change the final project: log the call on the course, hand it to whoever decides, and it stays beside the course once they confirm it.

  • Comments

    Review on the exact outcome

    A subject expert leaves a note on the outcome line it is about, a co-instructor answers in the thread, and you close it once the page is right.

  • Canvas

    The curriculum on one page

    Draw who each path is for and its courses in order, and keep the courses not on a path yet in sight. Every card opens its page.

  • Backlog

    Production on a board

    Recording, captions, answer sheets, learner interviews: tasks on a board, each pointing at the course or learner page it serves.

  • AI Agent

    A reviewer, only if you want one

    Nothing happens unless you connect your own Claude Code or Codex and ask. If you do, it can tell you which module serves no outcome, or which lessons two courses share.

Learners

Start from who it is for

A learner page says where they start, what they believe that is wrong, how much time they have, and what done looks like. Courses and paths link to it, so “who is this for?” has one answer.

A learner page for The Office Generalist: who they are, where they start, what they need, and what done looks like.

Paths

Draw the curriculum, course by course

Put a path on a canvas: the learner it is for, then each course in order, joined by arrows, with the course that is not on a path yet beside it and a sticky note for the open question. Each card shows its status.

A canvas for a learning path: two learner cards, then three courses in order joined by arrows labelled starts here and then, a course not on the path yet, and a sticky note asking whether charts belong on the path.

Decisions

Keep the reasons a course changed

Each call is a short record of its own: what was decided, why, who logged it, and who confirmed it. One still waiting sits in an inbox until the person it was handed to confirms it or sets it aside.

  • A retired course stays, marked Retired, with the reason.
  • Any page exports to PDF from its menu, for a reviewer who wants paper.
The decisions of a fictional school: one proposed and handed to the lead instructor, two confirmed, each with the course it was made for and who logged it.

Start here

Start from Academy.

Academy holds the school, learner first: The School (mission, teaching, market, and production), learner pages, courses grouped by track, paths, a catalog, and a lesson style guide. Pick it when you start a new project in the app.

A school of courses

Academy@The-Virtual-Panda/academy

Learner personas, courses by track, learning paths, and a catalog.

  • The School
  • Learners
  • Courses
  • Paths

In the app: New Root, then pick it from the list.

See it in the Registry
A production board for a fictional school: recording a module, an answer sheet, captions, and an outline review, each pointing at the course or learner page it serves.

Write your next course outcomes first.

Download Eidos MD, pick the Academy framework, and write one learner page and one course page. It is free, and your pages stay on your computer.

Free for macOS, Windows, and Linux. Your files stay plain text in a folder you own.