I'm not too concerned with automating this. While I think it would be awesome for many reasons to have the kind of metadata needed to do the automation available for each project, I just am not sure of the benefit for this use case. My concern is the fact that the breadth of documentation varies for each release. E.g. for 5.0 and moving forward I hope to have a few different documentations as discussed at https://github.com/hibernate/hibernate-orm/wiki/Documentation-proposal and email. One option is to allow a multi-valued set of "documentation links" for that particular version. Anyway, again, my concern is not to automate this; I plan on hand writing each version-centric doc page.

Not sure what you mean about "recent versions of that family". We only keep docs per-family. At least for ORM. So the "versions" I am interested in are all release families, if you look at my specific examples.

Well I think that FAQs are naturally versioned, we personally have not put any effort into the ORM one so far since the migration. So for me thats a non-starter. But yes I do mean getting-started-guides, tutorials as well as the manuals and "topical guides". For ORM at least these are all versioned already. I am really just talking about making the hibernate.org pages for this (1) prettier and (2) easier