Well, to be honest the old matrix got a bit too complex for me in the end. A compatibility matrix for just Search and ORM seems like a good idea. I even think we can automate this and use the same mechanism for WEBSITE-112.

My plan is to access the deployed POM during building of the release metadata, extract the defined dependencies and add some to a map for access within the page. Not only would that give us the matrix we are after, but it would also allow us to use variables for version other than the main artifacts. Right now we get version of the latter from the release file, but version of e.g. Lucene in the Search case is still hard coded.