Feature Request - Extend Page Configuration for ContentItemEdit

+1

Submit that as a new idea on the roadmap. This is the right place, where feature requests compete to make it into the product.

https://roadmap.kentico.com/tabs/5-released

Thanks Milan, I've submitted the feature request as suggested. However, I have some concerns about roadmap.kentico.com as a feedback platform. The current system feels opaque because:

• Community members can't vote on feature requests
• There's no visibility into whether others share the same need
• The prioritization process and timeline remain unclear

Having more transparency around feature requests would help the community understand what's being considered and allow us to collectively signal which features matter most to our projects.

I will keep this post here open and share some status in the future.

Yep, totally agreed. From my own experience, I’ve submitted a couple of requests and got zero feedback. So we’re in the same boat.

My point is that if something isn’t submitted to the roadmap, it might not even be considered, as product managers might not be scanning the community portal for feature requests.

I suspect the product management team receives a lot of requests and feedback from various sources. Not only from the community through the roadmap but also from direct conversations with partners who don’t participate in the community yet are still valuable to Kentico.

So it might actually be counterproductive to let only the community vote on features, since that’s just a subset of all XbyK users and customers.

Product management needs to put all the sources together, identify the most impactful ones at the time, and have them built into the product in a way that complements it well. So I kind of understand why they handle it in that “secret” way.

Generally speaking, when I submit a request, I have no expectations. I just hope that maybe one day it’ll be added if enough customers care about it. And in some cases, I actually got what I requested after a while, like the scaled image variants or support for automatic Lucene index rebuilds after deployment.

This is something we've also raised (albeit in the Slack). All of what Sean says makes sense, but it doesn't address the issue you mention. It's still opaque, you still don't know if your idea was scrapped and you should either a) suck it up, b) roll your own solution, c) look for a different product altogether.. or if it's been put on the roadmap and will be added to XbyK.

I really feel that there needs to be some form of feedback whereby you can determine your own course of action. If the 'Submit an idea' is a 'fire and forget and you should have 0 expectations' type of deal.. yeah.

Some context;

We have submitted at least one issue that's a show stopper for us. We can't migrate our K11 to XbyK if this isn't addressed. And if it isn't addressed by Kentico we will need to investigate rolling our own solution and check the feasibility of this actually working. If it turns out it's absolutely not possible; we may have to revisit our migrate to XbyK plans.

But I suppose we may already have our answer; (as Milan said) .. no expectations. Start to see if you can build it yourself.

Thanks a lot for the detailed explanation @Sean — it helps to understand how the feedback process works internally.

I’ve been thinking about a small idea that might help both the community and the product team. What if, before submitting a suggestion on the roadmap.kentico.com, we first create a post here in the Q&A section using a specific tag (like roadmap-proposal)? Then, when submitting the idea to the roadmap, we could include the forum link to that post, and then the idea submission ID can be shared via email to who submitted the idea and update the post with it.

That way, each roadmap request could have an optional discussion thread where the community can share opinions, ideas, or use cases — while your team can also see how people are reacting or expanding on the idea.

It wouldn’t need to be mandatory, just a simple, optional way to connect the community discussions with roadmap submissions. I think it could bring a bit more transparency for us and provide more context for your team when evaluating feedback.

@sdbkwilla,

It's still opaque, you still don't know if your idea was scrapped and you should either a) suck it up, b) roll your own solution, c) look for a different product altogether.. or if it's been put on the roadmap and will be added to XbyK.

It's less opaque than any other product you would consider moving too. None of them have any kind of public roadmap like ours. They have even less public commitment and sharing of their plans.

Back when we had the UserVoice, people had even less of an idea of what we were going to deliver, not more. Additionally, the UserVoice/forum based approach led to many people trying to solve the problem in the comments rather than focusing on the challenge and the scenarios. It was not productive for anyone even if it allowed you to see your comment in a public forum vs submitting it to us and not seeing it on a web page somewhere.

Your timelines and requirements are unique to you and we have thousands of customers with different timelines and priorities. We try and provide as much visibility as we can without committing to features that we end up having to pivot away from. If you don't see something on the roadmap that you need right now, submit your feedback and then proceed to build it yourself. The product is intentionally adaptable to help partners and customers in this way.

@victor,

What if, before submitting a suggestion on the roadmap.kentico.com, we first create a post here in the Q&A section using a specific tag (like roadmap-proposal)? Then, when submitting the idea to the roadmap, we could include the forum link to that post, and then the idea submission ID can be shared via email to who submitted the idea and update the post with it.

The product team does not use the Kentico Community Portal to identify requested updates to Xperience, so I don't recommend this approach. Submit your scenario on the roadmap. If other people have the same scenario they will also submit it. If enough people have the same kind of challenge and we think we have a good way to solve it then we will prioritize it and add an item to the public roadmap.

As I mentioned in my LinkedIn post (and above in this comment), the forum-style approach to product feedback was not productive 10-15 years ago and we're not planning to go that direction today. We absolutely appreciate feedback submitted on the roadmap. The current approach is the one we're going to continue with.