Customizing > Property Editor #7687
Open
Conversation
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
Luuk1983
reviewed
Dec 3, 2025
Contributor
|
The order of the menu items is different than what's on your page: 
Consider streamlining this. I think both your document and the menu should be ordered by what is the most logical flow when you want to learn about Property Editors. |
leekelleher
approved these changes
Dec 15, 2025
Member
leekelleher
left a comment
leekelleher
left a comment
There was a problem hiding this comment.
I'm happy with the updates from a technical perspective. Excellent work! 🚀
Updated the README.md to improve clarity and consistency in the links and descriptions for Property Editors.
sofietoft
requested changes
Dec 17, 2025
Contributor
sofietoft
left a comment
sofietoft
left a comment
There was a problem hiding this comment.
Changes look great @busrasengul 👍
I've made a single comment - let me know what you think!
|
|
||
| {% hint style="info" %} | ||
| [This tutorial](../../tutorials/creating-a-property-editor/) contains step-by-step instructions for building a custom Property editor. | ||
| [This tutorial](../../tutorials/creating-a-property-editor/) contains step-by-step instructions for building a custom Property Editor. |
Contributor
There was a problem hiding this comment.
It was a little unclear as to what "This" what referring to, so I've rewritten this note a bit.
Let me know what you think!
Suggested change
| [This tutorial](../../tutorials/creating-a-property-editor/) contains step-by-step instructions for building a custom Property Editor. | |
| This article acts as an overview for all things related to Property Editors. See the [Creating a Property Editor](../../tutorials/creating-a-property-editor/) section for step-by-step instructions on building a custom Property Editor. |
| ## [Property Actions](property-actions.md) | ||
|
|
||
| Use Property Actions to add additional functionality to your custom property editors. | ||
| Use Property Actions to add additional functionality to your custom Property Editors, such as custom buttons or actions that appear alongside the editor in the backoffice. |
Contributor
There was a problem hiding this comment.
Fixing a too-long sentence:
Suggested change
| Use Property Actions to add additional functionality to your custom Property Editors, such as custom buttons or actions that appear alongside the editor in the backoffice. | |
| Use Property Actions to add additional functionality to your custom Property Editors. This could include custom buttons or actions that appear alongside the editor in the backoffice. |
sofietoft
reviewed
Dec 17, 2025
Contributor
sofietoft
left a comment
sofietoft
left a comment
There was a problem hiding this comment.
Couple more comments on too-long sentences.
| A Property Editor is composed of two key extensions: [Property Editor Schema](composition/property-editor-schema.md) and [Property Editor UI](composition/property-editor-ui.md). These components work together to define the data structure and user interface for content entry in the Umbraco backoffice. | ||
|
|
||
| Reference for the package.manifest JSON file format to register one or more property editors for Umbraco. | ||
| Optionally, you can use a [Property Editor Data Source](composition/property-editor-data-source.md) to provide data to your Property Editor UI, allowing the same UI to work with different data sources. |
Contributor
There was a problem hiding this comment.
Suggested change
| Optionally, you can use a [Property Editor Data Source](composition/property-editor-data-source.md) to provide data to your Property Editor UI, allowing the same UI to work with different data sources. | |
| Optionally, you can use a [Property Editor Data Source](composition/property-editor-data-source.md) to provide data to your Property Editor UI. This will allow the same UI to work with different data sources. |
| ## [Property Actions](property-actions.md) | ||
|
|
||
| Use Property Actions to add additional functionality to your custom property editors. | ||
| Use Property Actions to add additional functionality to your custom Property Editors, such as custom buttons or actions that appear alongside the editor in the backoffice. |
Contributor
There was a problem hiding this comment.
Suggested change
| Use Property Actions to add additional functionality to your custom Property Editors, such as custom buttons or actions that appear alongside the editor in the backoffice. | |
| Use Property Actions to add additional functionality to your custom Property Editors. This could include custom buttons or actions that appear alongside the editor in the backoffice. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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
Updating Customizing, Property Editor
📎 Related Issues (if applicable)
✅ Contributor Checklist
I've followed the Umbraco Documentation Style Guide and can confirm that:
Product & Version (if relevant)
v17, v16
Issue #7688