Reusable content in WYSIWYG editor of (richt) text field of content type

2025/09/18 10:14 AM

Hello,

We are working on the migration of a K11 solution that allowed content editors to do the following:

Write text in a richtext field of a custom page type. Within this text they could place inline widgets that would let them pick from their stash of reusable content (our own defined type) items that would then get filled in when the page(s) got displayed by resolving the dynamic content.

n.b. we also resolved this dynamically in the API that exposed this to a mobile application, etc.

Now when working on the migration we can't figure out how this scenario is to be supported in XbyK. I see some mention of Page Builder and WYSIWIG but we're looking to support this on the content item itself. AI/gpt is coming up with a custom plugin for the Froala editor and a (custom?) content picker of sorts. Is this really the only route to go?

n.b. I'm not looking for a solution that involves 'add a page/content selector' field, that doesn't solve our issue here.

Looking forward to some insights.. thank you in advance.

Environment

  • Xperience by Kentico version: [30.9.0]

  • .NET version: [8|9]

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

  • Link to relevant Xperience by Kentico documentation

Answers

2025/09/18 11:04 AM

I’ve already had a couple of casual discussions with the Kentico team about this. Referencing content items inside the Froala editor isn’t supported, but it would be a great addition. Feel free to submit an idea through the roadmap: https://roadmap.kentico.com/tabs/4-planned/submit-idea

Also, check out this LinkedIn thread where we discuss it further and even suggest some solutions: https://www.linkedin.com/feed/update/urn:li:activity:7353755776940732416/

2025/09/18 12:53 PM

Thanks for confirming this a) is a real world use case, and b) isn't supported yet..

Considering our timeline we will probably end up rolling our own solution for this (similar to how it is outlined in the LinkedIn article). I will still submit the idea through the roadmap though, ideally this becomes supported out of the box so others don't need to roll their own solution(s).

To response this discussion, you have to login first.