It would be helpful to make it easy to distinguish in the knowledge base internal list which articles are ready to have their next version's updates published and which aren't. Currently, when we have reworked current features in our product, their related knowledge base articles have to be updated with this next version in mind. However, since we ideally would want to update them right before the product version (that contains the reworked features) becomes available to our clients, we would have multiple ready-to-publish articles that we have to identify across the other articles that were updated within other scopes. This makes it so that the other practical option is to publish the updates right after they are made so that we can just focus on reflecting the updates in to the article content, and not have to worry about which articles need updating right before the product version becomes available. This option isn't the best as that would mean there is a period before the product version availability that end users are viewing information of new reworks that they don't have access, potentially causing confusion in their understanding of our product.
... Mehr anzeigen