Added details of read-only partial views for field types.

Author: AndyButland

13/umbraco-forms/developer/extending/adding-a-fieldtype.md

@@ -106,6 +106,16 @@ If working with Umbraco 9 or earlier versions, you'll find the `Views\Partials\F
 
 For Umbraco 10 and above, we've moved to [distributing the theme as part of a Razor Class Library](../../upgrading/version-specific.md#views-and-client-side-files) so the folder won't exist. However, you can create it for your custom field type. If you would like to reference the partial views of the default theme, you can download them as mentioned in the [Themes](../themes.md) article.
 
+### Read-only partial view
+
+When rendering a multi-page form, editors have the option to display a summary page where the entries can be viewed before submitting.
+
+To support this, a read-only view of the field is necessary.
+
+For most fields, nothing is required here, as the default read-only display defined in the built-in `ReadOnly.cshtml` file suffices.
+
+However, if you want to provide a custom read-only display for your field, you can do so by creating a second partial view named with a `.ReadOnly` suffix. For this example, we would create `FieldType.Slider.ReadOnly.cshtml`.
+
 ## Umbraco backoffice view
 
 The final step involves building the HTML view which will be rendered in Umbraco as an example of how our end result will look:

14/umbraco-forms/developer/extending/adding-a-fieldtype.md

@@ -125,6 +125,16 @@ If working with Umbraco 9 or earlier versions, you'll find the `Views\Partials\F
 
 For Umbraco 10 and above, we've moved to [distributing the theme as part of a Razor Class Library](../../upgrading/version-specific.md#views-and-client-side-files) so the folder won't exist. However, you can create it for your custom field type. If you would like to reference the partial views of the default theme, you can download them as mentioned in the [Themes](../themes.md) article.
 
+### Read-only partial view
+
+When rendering a multi-page form, editors have the option to display a summary page where the entries can be viewed before submitting.
+
+To support this, a read-only view of the field is necessary.
+
+For most fields, nothing is required here, as the default read-only display defined in the built-in `ReadOnly.cshtml` file suffices.
+
+However, if you want to provide a custom read-only display for your field, you can do so by creating a second partial view named with a `.ReadOnly` suffix. For this example, we would create `FieldType.Slider.ReadOnly.cshtml`.
+
 ## Field Settings
 
 Field settings will be managed in the backoffice by editors who will create forms using the custom field type. These settings can be added to the C# class as properties with a `Setting` attribute:

15/umbraco-forms/developer/extending/adding-a-fieldtype.md

@@ -125,6 +125,16 @@ If working with Umbraco 9 or earlier versions, you'll find the `Views\Partials\F
 
 For Umbraco 10 and above, we've moved to [distributing the theme as part of a Razor Class Library](../../upgrading/version-specific/#views-and-client-side-files) so the folder won't exist. However, you can create it for your custom field type. If you would like to reference the partial views of the default theme, you can download them as mentioned in the [Themes](../themes.md) article.
 
+### Read-only partial view
+
+When rendering a multi-page form, editors have the option to display a summary page where the entries can be viewed before submitting.
+
+To support this, a read-only view of the field is necessary.
+
+For most fields, nothing is required here, as the default read-only display defined in the built-in `ReadOnly.cshtml` file suffices.
+
+However, if you want to provide a custom read-only display for your field, you can do so by creating a second partial view named with a `.ReadOnly` suffix. For this example, we would create `FieldType.Slider.ReadOnly.cshtml`.
+
 ## Field Settings
 
 Field settings will be managed in the backoffice by editors who will create forms using the custom field type. These settings can be added to the C# class as properties with a `Setting` attribute: