Why Data, Not Pages

Why Data, Not Pages

Das Fido-Curriculum Klasse 1
Fido MetaCurriculum Structure

Why Fido writes its curriculum as structured data rather than as pages or an app's built-in content: each topic is a small file in a fixed form, its explanation a piece of a web page, its exercises a list. What this buys (shown anywhere, checked by a machine, reviewable line by line, open to publish) and its price, a stricter way of writing. Prepares the links between topics.

There are two familiar ways to hold a curriculum. One is pages: a textbook, a worksheet, a website. People can read them, but software cannot tell which page a child needs next. The other is content built into an app, where each lesson is programmed as a screen. Our first interactive articles were made that way. Only that one app could show them, and every new article needed a programmer.

We now write the curriculum as data. Each topic is a short text file in a fixed form that says what the topic is and what it builds on. Its explanation is a piece of a web page, and its exercises are a list. Nothing in these files belongs to one app. Together the topics form the knowledge graph: a network in which every topic knows what it builds on.

Writing it this way buys four things. The same piece appears on the tablet and on the public explorer without being written twice. A machine can check every piece before a child sees it. A reviewer can read each change line by line, as with program code. And the curriculum can be published under an open license for other schools. That is the plan; none of it is published yet.

The price is a stricter way of writing. An author works in files of a fixed form, not in a word processor, and a broken link stops the build. We accept this because thousands of topics stay correct only if a machine checks them on every change.

Keine Aufgaben fĂĽr dieses Thema.