Academy pipeline
How a curriculum becomes thousands of static pages. One content tree per curriculum — Cambridge, American, IB — chapters written as MDX, everything pre-rendered at build time. No database, no server, nothing to break.
The problem
A learning platform serving three curricula has a content problem. Cambridge, American, and IB each slice subjects differently — different levels, different orders, different names for the same ideas. Write every chapter three times and the copies drift apart; write them once with no map and nobody can find anything.
The solution
One chapter library, three curriculum maps. Every chapter is written once as an MDX file. Each curriculum — Cambridge, American, IB — keeps its own map of how subjects and levels point at those chapters. The site pre-renders everything at build time: no database, no server, nothing to break.
Core capabilities
Single-source chapters
Each chapter is one MDX file — prose plus interactive components where they earn their place. Written once, it appears in every curriculum that maps to it. Fix a mistake in one place.
Curriculum maps
One directory per curriculum — Cambridge, American, IB — each defining its own subject and level structure over the shared chapter library. Curricula change; the chapters don't have to.
Static export
Next.js pre-renders every page at build time. No per-request rendering, no database queries, no backend to keep awake. The files are the site.
Nearly-free hosting
Static files on a CDN load fast on weak connections and cost next to nothing to serve. For a free learning platform, boring infrastructure is a feature.
Why this matters
It lets one person maintain a library for three curricula without the content rotting. Add a file, rebuild, done — the pipeline turns writing into pages with no ops work in between.