Moving something is an edit

Topic A in the Reading curriculum has grown too long, so Ben moves Lesson 3 into Topic B. In your tools you'd drag the row, or choose a new unit for it.

A move is an edit like any other. It saves a new version of the row, made by whoever moved it, and it changes what editors see. Readers keep the outline as it was last published, until the row is published again. Everything inside the row goes with it: Lesson 3's Teach Book is wherever Lesson 3 is.

Try it: select Lesson 3, and compare where it sits in each version.

Outline of Reading, as editors see it and as readers see it

Show as readers see itAs editors see it

As editors see it

Select a row in the outline to see what it holds, which language it comes from, and where it's placed.

As readers see it

Select a row in the outline to see what it holds, which language it comes from, and where it's placed.

Lesson 3 is in Topic B as editors see it, and in Topic A as readers see it. The move hasn't been published.

From the sample curriculum

content-sdk took 30 ms

Find the curriculum14 ms
Read the English outline of Reading16 ms

Timed on the site's server when this page loaded. Reload the page to time it again.

content-sdk took 39 ms

Find the curriculum14 ms
Read the English outline of Reading16 ms
Read the English outline of Reading, as readers see it9 ms

Timed on the site's server when this page loaded. Reload the page to time it again.

Loading the outline of Reading

Ben's move is saved, so every editor sees Lesson 3 at the top of Topic B, marked “Changes not published”. Readers still find it in Topic A, after Lesson 2. When Ben publishes Lesson 3, readers see the move. So you can rearrange an outline, check it, and publish when it's ready, and nothing moves for readers along the way.