diff --git a/docs/en/02_Developer_Guides/00_Model/10_Versioning.md b/docs/en/02_Developer_Guides/00_Model/10_Versioning.md
index fb3282891..f9b529102 100644
--- a/docs/en/02_Developer_Guides/00_Model/10_Versioning.md
+++ b/docs/en/02_Developer_Guides/00_Model/10_Versioning.md
@@ -11,6 +11,22 @@ from published content shown to your website visitors.
 
 Versioning in SilverStripe is handled through the [Versioned](api:SilverStripe\Versioned\Versioned) class. As a [DataExtension](api:SilverStripe\ORM\DataExtension) it is possible to be applied to any [DataObject](api:SilverStripe\ORM\DataObject) subclass. The extension class will automatically update read and write operations done via the ORM via the `augmentSQL` database hook.
 
+<div class="notice" markdown="1">
+There are two complementary modules that improve content editor experience around "owned" nested objects (e.g. elemental blocks).
+Those are in experimental status right now, but we would appreciate any feedback and contributions.
+
+You can check them out on github:
+  - https://github.com/silverstripe/silverstripe-versioned-snapshots
+  - https://github.com/silverstripe/silverstripe-versioned-snapshot-admin
+
+The first one adds extra metadata to versions about object parents at the moment of version creation.
+The second module extends CMS History UI adding control over nested objects.
+
+<img width="600" src="../../_images/snapshot-admin.png" width="600">
+
+*Example screenshot from versioned-snapshot-admin*
+</div>
+
 ## Understanding versioning concepts
 
 This section discuss how SilverStripe implements versioning and related high level concepts without digging into technical details.
diff --git a/docs/en/_images/snapshot-admin.png b/docs/en/_images/snapshot-admin.png
new file mode 100644
index 000000000..dd220746c
Binary files /dev/null and b/docs/en/_images/snapshot-admin.png differ