Was looking for the OpenSUSE HCL, specifically for tablets. Aside from no specific category for the Tablet hardware platform, I’ve found only relatively old content, broken links and un-ported content (from the old Wiki).
I found the new page but at least laptop links link to empty content. My guess is a decision hasn’t yet been made whether to port old content or change the format.
Various pages including this HCL page point to dead links to “Wiki Discussion” pages to post suggestions for improvement with the new design including the following
Assuming that it’s possible to post suggestions here,
I’ve visited the issue displaying this kind of data a few times over the past 10 years. In all cases I was managing ASP.NET projects, but the issue(s) and approach is the same no matter what technology you use, but the options will be different.
IMO the most flexible and User-friendly way to display tables of information like this based on User configurable parameters is typically called the Pivot Table, most commonly seen as a feature in Microsoft Excel. The problem is that displaying hierarchical data in a web spreadsheet is deceptively difficult. Until relatively recently, it was commonly done by embedding code generators, but because of the complex calculations required can cause extreme loads (typical server-side but can be client-side).
Much better is if you can do these calculations in the middleware or even better the database levels, and MS SQL introduced a native functionality only a couple years ago. I don’t know if other database engines can do this, I’d guess it’s still relatively rare. The next best try likely is to implement as middleware or server-side compiled code (not interpreted code), which is also rare but exist.
I recommend that for whatever code the Wiki Discussions might use, to start looking at available Pivot Table options prioritized as I’ve described… First database engine, then compiled code running in middleware or at the Presentation layer, and lastly as on the fly scripted HTML code.
Once the Pivot Table engine is selected, then the GUI itself can be modified to data bind the various hardware and manufacturer options either to a spreadsheet field or as input boxes of your choice (typically dropdown or scrolling).
My guess also is that if Pivot Tables are implemented, both input (contributors) and output (browsing) forms would need to be designed to shield Users from database complexities and limit potential errors.
Naturally, AJAX lends itself nicely to displaying this kind of data.