DOC Document new move block functionality

Author: GuySartorelli

en/08_Changelogs/6.2.0.md

@@ -8,6 +8,8 @@ title: 6.2.0 (unreleased)
 
 - [Features and enhancements](#features-and-enhancements)
   - [Accessibility improvements](#accessibility-improvements)
+  - [Unsaved changes indicator](#unsaved-changes-indicator)
+  - [Move elemental blocks](#move-elemental-blocks)
   - [Pass arbitrary attributes with requirements API](#requirements-attributes)
   - [Filter archived records](#filter-archived-records)
   - [Filter campaigns](#filter-campaigns)
@@ -94,6 +96,16 @@ The indicator appears as a "notice" after a configurable initial period (default
 
 See [Unsaved changes indicator](/developer_guides/customising_the_admin_interface/unsaved-changes-indicator/) instructions on how to configure the indicator.
 
+### Move elemental blocks
+
+In the [dnadesign/silverstripe-elemental](/optional_features/elemental/) module, functionality has been added to move elemental blocks from one parent to another, including from one elemental area to another on the same parent record.
+
+![move block button](./_images/move-block-button.png)
+
+The move form provides a lot of flexibility for various configurations, and fields will be hidden if there's only one option to select from. For example, if there's only one elemental area relation on your selected parent record, no dropdown to select an elemental area will be displayed - but if there's multiple, a dropdown will be there for you.
+
+![move block form modal](./_images/move-block-modal.png)
+
 ### Pass arbitrary attributes with requirements API {#requirements-attributes}
 
 When using [`Requirements_Backend`](api:SilverStripe\View\Requirements_Backend) as your requirements API backend (which is the default), you can now pass arbitrary attributes for JavaScript and CSS (`<script>` and `<link>` tags) using the `$options` argument in various methods.