No. (Unless something has changed or an enhancement is released)

In my POV is Knowledge Base module is designed around a more static documentation use case where the content (and hierarchy of the articles) doesn’t change that frequently. 

You can see proof of this in how Gainsight manages their own KB; posting articles about updates and changes as a work around for users to subscribe to (just that post) and get an update. 

You could do something similar in your Product Updates blog. I did for awhile; it was kind of a “Release Notes for Documentation” update post. 

This is a core reason that I’ve moved both communities I’ve hosted on CC to Product Updates for my (non-documentation) uses cases. IMO Product Updates is your blog module and can be used for use cases where you want: 

• The ability for users to subscribe
• Reverse chronological feed display
• More blog-like display

I’ve just renamed ours “Updates” and regularly post announcements about any of the following: 

• Product (release notes / release marketing)
• Community (monthly leaderboard overviews, new features, etc)
• Academy 
• Documentation 

Hey ​@DannyPancratz, I like your recommended approach of using the Updates blog format for product and more. Currently, our Product Updates consist mainly of release notes and downtime notifications.

The reason this came up is that we started hosting our RCAs in the Community. We store them by month in a KB structure, but we wanted to alert customers about new posts. However, we’re hesitant to do a standalone Product Update post since the KB style organizes them so neatly.

Appreciate your insights!