Build a timeline a class can read: dated events with photographs, places and sources, published as a read-only link or embedded straight into a course page.
A timeline on a slide is a picture of a timeline. This is the thing itself: students open it, switch it from a line to a map to a table, and read the events you wrote rather than the ones a textbook picked.
Build the chronology once — dates, places, images, a paragraph each, a source where it matters — and publish it as a read-only link. Nobody needs an account to read it, and every event added afterwards is there the next time they open it.
Advanced adds an iframe snippet, so the same timeline goes straight into a course page, a blog post or a wiki with no script and no key. You choose what the frame carries: the name, the description, the cover, and either all five styles or one you pin.
Switching styles in a classroom works because each one asks a different question. The line asks what came next. The map asks where. The table asks how many, and lets a student sort by date or category. The Spans view asks what overlapped, which is the question most history timelines are actually about.
Students can be collaborators on a timeline, adding events to a shared chronology — a class building one record between them rather than thirty copies of the same worksheet.
A free account is one timeline of up to 20 events, which is enough for a single lesson. Extra timeline slots are $2.99 each, bought outright, and hold 50 events. Sharing, embedding and the Log style are on Advanced at $12 for a month — which, for a course that runs a term, is usually the month it is being built.
Cards: A period at a glance, which is how a class first meets a chronology.
Spans: What overlapped what — the question most history timelines are really asking.
Map: The same events as places, in order, on one route.