@Hixie I am opening this issue as you suggested.

Use case

#18281 raised the issue that the existing license page could be improved upon. Especially as the list of licenses has many versions of the same license repeated. In fact, the package boringssl has some 76 licenses referenced in the framework. This issue can make the license page hard to navigate to view licenses for other packages. The current design may also appear broken to end users.

Proposal

Change to a package first navigation of the registered licenses. I suggest implementing this using a Master Detail Flow.

I have written and hosted an example to show roughly how the new UI would look and behave. The screenshots below are from that example application.

I welcome feedback and I am happy to put in the work to see this through. If you will have me.

Screenshot of page showing licensed packages (small to medium displays)

Screenshot of page showing licenses for selected package (small to medium displays)

Screenshot of master detail page showing licensed packages and licenses for selected package (large displays)