Eidos

Knowledge / Course

@The-Virtual-Panda/academy

A school of courses, learner first; The School (mission, how we teach, market, production), learner personas, courses grouped by track, paths, and a catalog.

0installs in the last 30 days0installs in total

Install

The whole root

npx eidosmd install @The-Virtual-Panda/academy

One collection, or one variant into a collection you already have

npx eidosmd install @The-Virtual-Panda/academy --collection The School
npx eidosmd install @The-Virtual-Panda/academy --variant The School.teaching
Source
The-Virtual-Panda/Eidos-Examples on GitHub
Tag
academy/v0.3.0
Path
academy
Eidos version
5.4.0
Naming
Title Case
Keywords
coursescurriculumlearnersinstructor
Published
September 20, 2026

What it contains

Collections

The Schoolframe

The school itself, four pages: what it teaches and why, how it teaches, where it sells, and what it costs to make. Every learner, course, and path gets checked against these.

Variants

missiondefaultwhat the school teaches and why, and what it is not

Template: templates/frame.mission.md

# {{title}}

_What the school teaches and why. This page and Production decide what gets made: a course that serves no learner here, or teaches something the mission does not claim, is one to question._

## What We Teach

_A few sentences: the subject, the level, and the change it makes in a learner. If it takes a list, it is not a mission yet._

## Why It Has to Exist

_What is wrong, missing, or badly taught in the world without this school. The problem a learner has that the courses out there do not solve._

## What a Graduate Can Do

_The promise every path keeps in some form: what a learner can do at the end of the longest path that they could not at the start. Said so it could be checked._

## Not This School

_The school next door that you are deliberately not running: the bootcamp, the certificate mill, the free channel. Writing it down here is what keeps the catalog from sprawling._
teachinghow it teaches: the format, the length, how learners prove it, the rules every course keeps

Template: templates/frame.teaching.md

# {{title}}

_How the school teaches: the format, the length, how learners prove it, and the rules every course keeps. The Editor reads a course against this page._

## The Format

_What a course is made of: video, text, live sessions, exercises, projects. How long a lesson, a module, a course usually runs. What a learner does, not just watches._

## How Learners Prove It

_How a learner knows they have learned it, and how you know: quizzes, projects, a review, nothing. Which courses give a certificate, and what that means._

## Rules Every Course Keeps

_How a lesson opens, how it closes, how an exercise is set, what a course never assumes. The rules that make the courses feel like one school._

## Support

_What a learner gets beyond the material: a community, office hours, feedback, nothing. What it costs to provide and where the line is._
marketwhere the courses sell, what they cost, and what they are up against

Template: templates/frame.market.md

# {{title}}

_Where the courses sell, what they cost, and what they are up against. The page a course's price and a track's existence get read against._

## Where It Sells

_Where the courses live and are bought: your own site, a marketplace, a company's internal system. What the platform allows and what it takes._

## What It Costs a Learner

_Per course, per path, a subscription, a cohort fee. What each costs and why, and what is free._

## What It Is Up Against

_The courses a learner would also consider, and what each does that yours does not. Name the difference, not just the course._

## How Learners Find It

_How a learner finds the school, and what turns them into one. The channel, the free thing that leads to the paid thing, the referral._
productionwhat a course costs to make, how often one ships, and what the platform requires

Template: templates/frame.production.md

# {{title}}

_What a course costs to make, how often one ships, and what the platform requires. The page a course's plan gets read against._

## What a Course Costs to Make

_In money and in hours, and what the school can spend in a year. The limit every outline lives inside._

## How Often One Ships

_How often a course ships or gets refreshed, and the path from outline to published. The number the Producer holds the school to._

## What the Platform Requires

_Lengths, formats, file limits, accessibility, review. The rules a course cannot break._

## What Matters Most

_The two or three things money and attention go to first, in order, and what you would give up to protect them. This settles the argument when the budget says no._

Learnerslearner

Who it is for: one page per kind of learner, flat. Where they start, what they need, what done looks like for them. Courses and paths point at these.

Variants

personadefaultone kind of learner: where they start, what they need, what done looks like

Template: templates/learner.persona.md

# {{title}}

## Who They Are

_One kind of learner, in a paragraph: who they are, why they are here, and what they are trying to become. Only give a kind its own page when they learn in a way the others do not._

## Where They Start

_What they already know and can do, and what they believe that is wrong. What a course for them may assume, and what it may not._

## What They Need

_How they learn best, how much time they have, what they will skip, what makes them quit. The limits a course for them has to respect._

## What Done Looks Like

_What they can do at the end that they could not at the start, said so it could be checked. The outcome a path for them aims at._

## Notes and Decisions

_Notes: the interviews, the survey, the real person this is drawn from. Decisions: one line each, dated, never deleted._

Coursescourse

The catalog: one page per course, grouped by track. What learners will be able to do, the modules, how they prove it, the format.

Grouped by Tracks

Variants

fulldefaultthe full page for a course

Template: templates/course.full.md

# {{title}}

## Who This Is For

_Which learners, what it teaches them, and why this school should be the one to teach it. A short paragraph. If this changes a lot, it is a different course._

### Taking for Granted

_What you are assuming about the learner arriving here: what they know, what they have taken, what they believe. Write it down so a guess does not become a lesson that loses them._

## Still to Decide

_What you do not know yet. Kept near the top so nothing gets buried; when something is settled it becomes an outcome below, or a decision._

## What They Will Be Able to Do

_At the end, as numbered statements someone could check. If it is not written here, the course is not promising it. Every module below serves at least one._

1. <!-- the first thing a learner can do afterward -->

## The Modules

_The outline: modules in order, and the lessons in each, one line per lesson with the outcome it serves. Not the material; the shape of it. Put the syllabus in Files and link it._

### Module

_What it covers, and which outcomes it serves._

## How They Prove It

_How a learner shows each outcome, and how the school checks: the project, the quiz, the review. Held up against How We Teach._

## Format and Length

_What the course is made of and how long it takes, against The Format on the How We Teach page. `duration` at the top is the number; this is the shape._

## Not This Course

_What this course deliberately does not teach, and which course does. This is the section that keeps a catalog in shape; a course without it grows into the one next to it._

## Before and After

_Courses a learner has to finish first, and courses this one leads to. Link them rather than naming them._

## Notes and Decisions

_Notes: the references, the reviewer, the platform's notes. Decisions: one line each, dated, never deleted._

<!-- 2026-04-08: Moved the setup lesson into Module 1; learners quit before reaching it. (Editor) -->
outlinean outline: who it is for, what they will be able to do, the modules; grow into full

Template: templates/course.outline.md

# {{title}}

## Who This Is For

_Which learners, and what it teaches them, in a short paragraph. Grow it into the full page once it is in production._

## What They Will Be Able to Do

_At the end, numbered._

1. <!-- the first thing a learner can do afterward -->

## Still to Decide

_What you do not know yet._

## The Modules

_The modules in order, one line each, with the outcomes each serves._

## Not This Course

_What this course does not teach, and which course does. Write this first, not last._

Pathspath

One page per path, flat: a sequence of courses, in order, for one kind of learner, toward one outcome. The pages that tie learners to courses.

Variants

fulldefaultwho it is for, where it goes, and the courses in order

Template: templates/path.full.md

# {{title}}

## Who It Is For and Where It Goes

_The learner it is for (linked in `for` at the top) and what they can do at the end. A short paragraph._

## Still to Decide

_A course that does not exist yet, a gap between two that do. Kept near the top so it does not get buried._

## The Path

_The courses in order, each a link with one line on why it is here and what it hands to the next. The order is the point; a path you could shuffle is a list, not a path._

## What They Leave With

_What a learner can do at the end of the whole path, matched to What Done Looks Like on their page. If it is not written here, the path is not promising it._

## Not This Path

_What this path does not cover, and which path does. Where a learner goes next._

## Notes and Decisions

_Notes: completion numbers, the learner who tested it, the reminder. Decisions: one line each, dated, never deleted._

<!-- 2026-04-08: Dropped the theory course from the path; nobody who finished it needed it. (Instructor) -->

Other folders

  • Files Slides, worksheets, recordings, and syllabi the pages link to.

Roles

Editorroles/editor.md
# Editor

## Who they are

The instructional designer. Reads for structure before material: do the modules deliver the outcomes, does the course keep the rules on How We Teach, and where are two courses teaching the same thing.

## How to respond

- **Vocabulary & depth:** teaching craft: outcome, scaffold, assessment, cognitive load, sequence. Skip production unless asked.
- **Decisions:** name the structural problem and the options; the cut, the merge, and the reorder are the instructor's. Inside a module they were handed, the lesson order is theirs to propose.
- **Surface / hide:** lead with What They Will Be Able to Do against The Modules, How They Prove It against How We Teach, Not This Course across neighbors, and each learner's Where They Start against a course's Taking for Granted. Keep the Market and the budget out of the way.
- **Focus:** what the outcomes promise versus what the modules deliver; overlap between courses in a track; a course whose Who This Is For no longer matches its outline.

## Calibration

Usually plenty of **experience with the scope**; **technical capacity** rarely matters here. Talk teaching, not tooling.
Expertroles/expert.md
# Expert

## Who they are

Knows the subject. A reviewer, a practitioner, another instructor. Reads for whether it is right and current; cares about nothing else in this folder.

## How to respond

- **Vocabulary & depth:** the subject's own words, at full depth. No teaching craft, no production, no market.
- **Decisions:** none. They say what is wrong, out of date, or missing in the subject; what to do about it is the instructor's, with the Editor.
- **Surface / hide:** lead with What They Will Be Able to Do, The Modules, and anything in Taking for Granted about the subject. Keep the Market, Production, the mechanics of How They Prove It, and the Decisions out of it.
- **Focus:** is what the course claims to teach true, current, and complete enough for what it promises.

## Calibration

High **technical capacity** in the subject and no **experience with the scope**: recap the course's outcomes and nothing else.
Framework Ownerroles/framework-owner.md
# Framework Owner

## Who they are

The instructor whose school this is. They decide what is taught, to whom, how, and what the school will never teach. Everyone else in this folder is here to help them think clearly.

## How to respond

- **Vocabulary & depth:** talk about the school the way they do: learners, outcomes, tracks, paths. Put the decision in front of them, not the production behind it, unless they ask. Plenty of instructors are their own editor and producer; if they want the craft, give them the craft.
- **Decisions:** all theirs. Lay out the options and what each one costs; never settle something in Still to Decide, retire a course, or cut an outcome for them. Push hardest on Not This School in the Mission and on Not This Course on every course.
- **Surface / hide:** lead with who a course is for, what it promises, and what a choice does to the production schedule; keep the module detail and the platform rules behind a link.
- **Focus:** the Mission, the Learners, what has been left out on purpose, and whether each course still says what they meant.

## Calibration

**Experience with the scope** sets how much of the school to recap. **Technical capacity** here means how comfortable they are with production and the platform; meet them where they are.
Learnerroles/learner.md
# Learner

## Who they are

Someone who might take a course. Not making the school; a test of it. Reads a course's Who This Is For and What They Will Be Able to Do to react: would they sign up, would they finish, where would they get lost.

## How to respond

- **Vocabulary & depth:** plain language about what the course teaches and what they will be able to do. No teaching jargon, no production status.
- **Decisions:** none. Ask what they want to learn and what put them off; do not invite them to redesign the course.
- **Surface / hide:** lead with Who This Is For, What They Will Be Able to Do, Format and Length, Before and After, and each path's What They Leave With, in the school's own voice. Keep Still to Decide, the mechanics of How They Prove It, the Decisions, the budget, and anything marked `Retired` out of it.
- **Focus:** are the outcomes ones they want, do they meet the prerequisites, and is the length one they would finish.

## Calibration

**Technical capacity** in the subject is whatever the matching learner page says; set it from the page, not the person. **Experience with the scope** is none: recap the course before answering.
Producerroles/producer.md
# Producer

## Who they are

Holds the pipeline. Reads every course for where it stands, what it is waiting on, and whether the school will ship on schedule. Owns the schedule as a document, never the decisions inside it.

## How to respond

- **Vocabulary & depth:** status, dates, hours, deliverables, and platform rules, in plain words. Skip the teaching unless it changes the schedule.
- **Decisions:** none of the school's are theirs. They spot a course that will miss its date, an outline with no track, a platform rule an outline breaks, and bring each one to the instructor.
- **Surface / hide:** lead with `status`, `duration`, How Often One Ships and What the Platform Requires on the Production page, each course's Format and Length, and anything in Still to Decide that blocks recording. Keep the outcomes and the mission out of the way.
- **Focus:** the pipeline as a whole: what is Outlined, In Production, Published, and whether the year's budget fits.

This folder holds what the school is, not the to-do list: no tasks, no assignees, on purpose. Read progress from `status` and the dated Decisions; keep the production board in whatever tool the school uses and link it.

## Calibration

Usually plenty of **experience with the scope** and moderate **technical capacity**. Work from the properties; The School pages are context.

Top-level documents

  • Start Here Start Here.md where to start: what this is, and where things are
  • Catalog Catalog.md every course on one page, as a learner sees it
  • Lesson Style Guide Lesson Style Guide.md how a lesson is written and recorded

Custom properties

statusTextevery collectionWhere this stands: Idea, Outlined, In Production, Published, or Retired. (Idea | Outlined | In Production | Published | Retired)
date_createdDateevery collectionYYYY-MM-DD. Set once.
date_modifiedDateevery collectionYYYY-MM-DD. The last change.
tagsListevery collectionFree tags.
trackrequiredTextCoursesWhich track (subject area) the course belongs to. Matches its sub-folder.
prerequisitesListCourses, PathsCourses a learner has to finish first, as links.
forListCourses, PathsThe learners this is for, as links to their pages.
levelTextCoursesWhere a learner should be before starting: intro, intermediate, or advanced. (intro | intermediate | advanced)
durationNumberCoursesHow many hours it takes a learner, start to finish.

Start Here

The first top-level document, as the author wrote it at this tag, placeholders included. Links open the source.

{{Product}}

Start here. This folder is the one place that says what the school teaches, learner by learner and course by course: who each course is for, what they will be able to do, and how it is built. It stays true whether or not a lesson has been recorded.

{{One line: what the school teaches, to whom, and what a graduate can do.}}

Where things are

  • The School: four pages: what it teaches and why, how it teaches, where it sells, and what it costs to make. Everything else gets checked against them.
  • Learners: one page per kind of learner: where they start, what they need, what done looks like.
  • Courses: one page per course, grouped by track: what they will be able to do, the modules, how they prove it, the format.
  • Paths: one page per sequence of courses, for one kind of learner, toward one outcome.
  • Files: slides, worksheets, recordings, and syllabi the pages link to.

The one-page docs

How to use it

A course’s page says what the course is: who it is for, what they will be able to do afterward, the shape of its modules, and what it does not teach. It is not the material and not a task. Learners come first: a course points at the learners it serves with for, and a path strings courses together for one of them. Write the page before the recording, and keep it true after: a course you retire stays here, marked Retired, so the reasoning survives.

Built on Eidos. The page types, the properties each page carries, and the roles live in .eidos/; eidos check keeps it honest.