Hello @DannyPancratz . Thank you for your idea. Can I ask you to share a bit more context on how having content helpfulness would be helpful for Product updates?

@Marion Frecaut For the standard use case, I think it’d be a good option to include for customers who want to measure the helpfulness or effectiveness of how they communicate updates or road map info. Sure there’s a chance users will use it to rate their satisfaction with the update/roadmap, rather than the actual intended helpfulness, but it’d be good to have the feature as an option to compare/contrast that content type against articles and other content in the community. A baseline of helpfulness/satisfaction allows you to build towards improvement. Likes and subscribes on the post aren’t a strong enough signal. 

More specifically, we’re going to be using the Product Updates module for an atypical use case, as the content publishing UX better fits our high-volume approach in a way that the Knowledge Base does not. The blog-like UX with the latest post at the top, as well as cross-filtering by product area is a better fit for our content; the KB format of publishing to only one category and drag-drop lists is good for documentation, but not our use case. So we’re moving our KB content over into the Product Updates module. The main thing we lose in this transition is the content helpfulness capability, which is what inspired the idea. But, even for traditional use cases, I would want to be able to measure that.