Regions, sections, columns and modules
A page is regions of sections made of columns of modules; variants nest at section or module level, never inside each other, and ambiguous drags are refused.
A page's layout is four levels deep. A region is a named slot in the page template — header, main, footer. A region holds sections, stacked top to bottom. A section holds one or more columns, side by side. A column holds the modules — the actual content pieces you drag in from the palette.
Where personalization and testing fit
A variant container can wrap either a whole section or a single module, and those are the only two places one goes — there's no wrapping a column, and no wrapping a region. Whichever level it wraps, a variant container never nests inside another one: you can't put a personalized module inside a personalized section's arm, or a split-tested section inside another section's arm. The editor enforces this at the moment you drop something, not just as a rule you're expected to follow.
Why some drags do nothing
Dropping something on empty space between sections, rather than on a section or a drop zone, does nothing — it used to snap to the nearest zone and move things you didn't mean to move, and that's been deliberately turned off. The same silent refusal covers dropping a whole variant container onto an existing arm, and dragging a module straight from one arm onto another arm: both read as ambiguous about what should happen, so neither does anything rather than guessing.
The full set of drag gestures — resizing a column, removing a module from an arm, what Copy and Move actually do — is covered in Rearranging sections and modules in place; this page is about the shape of the document those gestures move things around in.