What this site shows

Your team's content tools are being built on content-sdk, the software that stores your curricula and keeps track of every change to them. This site shows what those tools will do with your work, so nothing surprises you when you use them: what a save keeps, what readers see, what happens when a Spanish version is missing, and what a new edition starts from.

Each step starts from a moment in your work and shows it with an example taken from sample curricula. Nothing you do here changes the sample. The site reads it as a user whose role lets it read and nothing else, so everyone sees the same thing.

Every example ends with a line saying where it comes from. When content-sdk gave the example what it shows, the same line ends with how long that took: “content-sdk took 14 ms”. That's how long it took for this site, with a small sample. Your own tools, with full curricula and many editors, will take a different time.

Try it: find which kind of example you'll see when a step is about something the tools won't let you do.

Where an example comes from

Source line	What it means
From the sample curriculum	Content taken from the sample through content-sdk, and checked against it
If you tried this	What the tools would tell you. The site doesn't make the change; it shows the reason in plain words
If you saved this	A save that changes nothing, which leaves nothing behind to show
Illustration	Written or drawn by hand, for something the sample can't hold
From your account	What content-sdk knows about you, read when you sign in

Five source lines. Only “From the sample curriculum” shows content read from the sample.

Illustration

Most examples are taken from the sample, so what you see is what content-sdk does. Where an example couldn't be, because it's a change the tools refuse or a save that leaves no trace, its last line says so.