Extend ContentItemCreate page

2025/10/23 12:21 PM

(Posting on behalf of a colleague; who somehow has hit a rate limiter for this forum)

My question is similar to How to extend a module.
We're trying to extend the ContentItemCreate page in the Admin UI of Xperience by Kentico, but we haven't found a way to do so. We've successfully customized other admin pages using PageExtender, but this particular page seems to be locked down or not exposed in the same way.
Is there a supported method to customize or extend the ContentItemCreate page?
Specifically, we want to restrict which content types are available or selected (based on the folder that the user has selected) when creating a new content item. We've looked into IContentTypesFilter, but it seems that it only works with components like ContentItemSelectorComponent, not with the built-in content type selector in the ContentItemCreate page.
Any guidance or examples would be greatly appreciated!Environment

  • Xperience by Kentico version: [30.10.0]

  • .NET version: [8|9]

  • Execution environment: [SaaS|Private cloud (Azure/AWS/Virtual machine)]

  • Link to relevant Xperience by Kentico documentation

Tags:
Content management Xperience Administration C#

Answers

2025/10/23 1:36 PM

We've figured a couple of things out since then; a couple of hurdles to take before it's fully usable still.

2025/11/10 8:15 PM

Unfortunately, No—there isn’t a supported way to extend the built-in ContentItemCreate page in Xperience by Kentico today.

Details

  • The ContentItemCreate UI and the ContentHubFolder object are part of Xperience’s internal admin interface. They are not exposed through the current UI extensibility points (e.g., PageExtender) or public APIs, so you can’t inject fields, swap the content-type picker, or modify its behavior in place.

  • Because of that, restricting content types inside the native ContentItemCreate flow (e.g., based on the selected folder) isn’t supported.

If you need folder-aware filtering or validation, you’ll have to implement it outside the built-in page.

To response this discussion, you have to login first.