From 682e8de5823ad1432312ed3ab96b8e45216ae146 Mon Sep 17 00:00:00 2001
From: Guy Sartorelli <36352093+GuySartorelli@users.noreply.github.com>
Date: Mon, 13 Mar 2023 17:37:49 +1300
Subject: [PATCH] DOC Document setting summary by default (#93)

---
 en/04_Changelogs/5.0.0.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/en/04_Changelogs/5.0.0.md b/en/04_Changelogs/5.0.0.md
index 90f7a1220..5440bb658 100644
--- a/en/04_Changelogs/5.0.0.md
+++ b/en/04_Changelogs/5.0.0.md
@@ -455,6 +455,7 @@ This empowers advanced `Extension` functionality such as [Versioned::canPublish(
 ### Other new features {#other-features}
 
 - [`DataObject::get_one()`](api:SilverStripe\ORM\DataObject::get_one()) can now be called directly from subclasses of `DataObject` without passing in a class as the first argument (e.g. `SiteTree::get_one(filter: ['Title:startsWith' => 'About'])`).
+- Strings returned from the [getSummary()](api:DNADesign\Elemental\Models\BaseElement::getSummary()) method in elemental blocks will automatically be displayed as the summary for the element in the [ElementalArea](api:DNADesign\Elemental\Models\ElementalArea) - this no longer needs to be manually added in [provideBlockSchema()](api:DNADesign\Elemental\Models\BaseElement::provideBlockSchema()).
 - The elemental [TopPage DataExtension](api:DNADesign\Elemental\TopPage\DataExtension) is applied to [`BaseElement`](api:DNADesign\Elemental\Models\BaseElement) and [`ElementalArea`](api:DNADesign\Elemental\Models\ElementalArea) by default, and the corresponding [`SiteTreeExtension`](api:DNADesign\Elemental\TopPage\SiteTreeExtension) is applied to [`SiteTree`](api:SilverStripe\CMS\Model\SiteTree) by default. This allows you to use `$TopPage` in your elemental block templates as a more performant alternative to `$Page` when referring to the page the element belongs to.
 - Void HTML elements such as `<img>` are no longer rendered as self-closing tags e.g. `<img src="foo" alt="bar">` is now rendered, previously `<img src="foo" alt="bar" />` was rendered.
 - It’s now possible to hook into FormField validation via the `updateValidationResult` extension hook. Module authors releasing form fields should opt-in to this functionality by calling the new `extendValidationResult` method to enable developers to extend and customise validation. See the [form validation documentation](/developer_guides/forms/validation/#extensions) for more information.