A row can be moved, copied, or deleted within its allowed zone. These actions affect both the structure and the modules inside, so it is best to proceed one step at a time and check history.
What you will learn
- Move a row only within its allowed group.
- Duplicate a row including its state and modules.
- Safely delete an empty or occupied section.
- Recognize protected rows that cannot be modified by these actions.
Ordering is limited by zone
Top and bottom rows can be reordered within their page area. Inner rows move within the physical group of the mainbox, and sidebars have their own structural rules. Mainbox, leftbox, and rightbox are locked against standard moving.
This limitation is not a drag-and-drop bug. It protects the componentbox and Bootstrap structure from combinations that would not make sense on the final website. You can use up/down controls, canvas drag-and-drop, or the Layers tree to move a row, provided the target is valid.
Moving, copying, and deleting
- Select the row before acting. Verify its ID, zone, position count, and present modules in the right inspector and Grid.
- Move one step at a time. Use the arrow or drag-and-drop. If the editor does not offer a drop target, the row does not belong to that group.
- Duplicate only the necessary foundation. A copy inherits positions, modules, and appearance settings.
- Check the copy immediately. Rename or edit the content so that two identical sections do not remain on the page.
- Read the confirmation when deleting. If the row contains modules, the dialog lists them and warns of their loss.
- Verify Grid, Layers, and Preview after the action. Then wait for autosave. If you selected the wrong row, use the visible Undo.
The mainbox cannot be duplicated or deleted. Its positions also cannot be edited like a regular section. System sidebars can be disabled or duplicated in supported cases, but their original structural rows cannot normally be moved.
Every copy counts toward the limit of custom rows and modules. Do not copy a long section just as a backup; use template duplication in your account for a safe project-wide variant.
A row copy is not a project backup
Duplication is useful for repeating a similar section within the same template. It copies its layout, modules, and styling, allowing you to quickly create another content band. However, it also increases the total count of rows and modules and can create two very similar parts that need to be differentiated.
To experiment with a different header, palette, or entire structure, prefer template duplication in your account. You will get an independent concept with its own code and history. A copy of a single row remains part of the same configuration, and autosave saves both together.
Deletion is a structural operation
Deleting a row also removes its positions and inserted modules.