My internal and external customers have made it clear that they would prefer our search results to be listed in reverse chronological order as the default experience. All of our product updates will have the same 10-15 keywords, and the upvoting on older release notes negatively impact the placement of the most recent release notes in search results. I want to deliver an experience where the end-user sets their preference for their search results ordering, I think it's those little details that make a great support experience. 

I was unable to locate a recipe or example for customizing the search results page for this use case. I believe providing this example or recipe would help end-users and improve ticket deflection when the type of documentation being presented in the KB has a limited and required lexicon. IT Networking for example you will find TCP/IP, address, server, host, ethernet, switch, port, UDP, etc over and over again. The current implementation for weighted result ordering can be too easily "misaligned" when repeated industry words are required and the older article content has more upvotes than the more recent article for a new version of the product or a new feature that uses the same key terms.  

-Dave