# Shaping the site tree

URL: https://kywi-docs-production.up.railway.app/authoring/shaping-the-site-tree
Type: docPage

Dragging a row only reorders siblings, Move to… only reparents, and Copy only duplicates in place — three gestures, three separate operations.

The Site Tree’s row menu and its drag handle look like one toolkit for rearranging pages, but they’re three separate operations underneath, each touching a different part of a page’s identity — its order among siblings, its parent, or its existence as a second copy. Reach for the one that actually does what you want rather than the one that happens to be closest.

## Dragging a row only reorders it among its siblings

A drag can only move a page up or down within its current parent — it never changes what that parent is. Dropping a page onto a different branch of the tree isn’t something dragging does; that’s **Move to…**, below.

## A drag can leave two rows tied for the same position

Dropping a row copies the order value of the row it lands next to rather than renumbering the whole list, so two siblings can end up sharing the same position. Which one then sorts first isn’t defined by the drag itself. If a reorder doesn’t seem to have “stuck,” dragging it again usually settles it — but if you keep dropping onto the same neighbor and the two rows just keep trading places, that recreates the same tie every time. Drop the row onto a different neighbor instead; that assigns it a different position and actually breaks the tie.

## “Move to…” is the only way to change a page’s parent

Picking a new location from the row menu’s **Move to…** is what actually reparents a page: it rewrites the page’s place in the tree and its URL to match the new parent, and carries every page beneath it along for the same change. What it never touches is the page’s own slug — a move changes where a page lives, not what it’s called. See [Slugs, paths, and moving a page](/authoring/slugs-paths-and-moving-a-page/) for what that means for the URL.

## Copy always lands next to the original

**Copy** duplicates a page as a sibling of the one you copied — never into a location you pick — and only the new top page’s slug changes, with `-copy` appended to keep it distinct from the original. Anything beneath it copies over with its slugs untouched, so the new subtree needs its own look before you publish it. A page at the very top level of the tree can’t be copied at all; give it a parent first.

## Delete moves a page to Trash

Deleting a row from the tree doesn’t remove it outright — it’s a soft delete, and the confirmation says so. See [Trash and recovering deleted work](/authoring/trash-and-recovering-deleted-work/) for getting it back.

## Version History, from here, does nothing yet

## The row menu’s Version History entry currently has no effect

The row menu offers a **Version History** item, but clicking it from the Site Tree doesn’t open anything — there’s no handler wired up for that entry point. Version history for a page is reached from inside the page itself, on its own Version History tab, not from the tree.
