Add Value Summary and Value Type Documentation#8047
Open
madsrasmussen wants to merge 52 commits into
Open
Conversation
…e/value-summary-and-value-type
…e/value-summary-and-value-type
AndyButland
approved these changes
May 13, 2026
Contributor
AndyButland
left a comment
There was a problem hiding this comment.
Looks great @madsrasmussen from my perspective. I just left one suggestion that I think makes it clearer as you read through, that you can go to the server for more information for presentation if you need to.
| ``` | ||
| {% endcode %} | ||
|
|
||
| A value type can represent any data structure, including complex objects. If your data has shape, define it accordingly and access its properties directly in `render()`. A color value with a hex code and a label, for example, lets you render a swatch alongside the name. The whole representation comes from the stored value — no server call needed: |
Contributor
There was a problem hiding this comment.
Suggested change
| A value type can represent any data structure, including complex objects. If your data has shape, define it accordingly and access its properties directly in `render()`. A color value with a hex code and a label, for example, lets you render a swatch alongside the name. The whole representation comes from the stored value — no server call needed: | |
| A value type can represent any data structure, including complex objects. If your data has shape, define it accordingly and access its properties directly in `render()`. A color value with a hex code and a label, for example, lets you render a swatch alongside the name. In this example, the representation comes from information already in the stored value — no server call is needed: |
Contributor
|
Do the changes made here also apply to version 18? Also, are the new articles in this PR generated by (or with the assistance of) AI? |
Corrected punctuation and improved clarity in the explanation of value types.
sofietoft
approved these changes
Jun 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📋 Description
Includes changes from #8043 . Please review and merge first.
Adds documentation for the new Value Summary and Value Type extension points/concepts
✅ Contributor Checklist
I've followed the Umbraco Documentation Style Guide and can confirm that:
Product & Version (if relevant)
CMS 17.5
Deadline (if relevant)