Yeah I like it

. That is exactly how it should work, from an interface point of view. But, I also think the matter is a bit more complex than how you state it. And I'll tell you why. This is done over and over. But what you'll end up with is a tuned down version of
this.
And
this is what I mean with not being able to see the forest through the trees. Don't get me wrong, I respect the huge effort that went into such a project. And all those make/model specific howto's can be a great help for all the people with the same make/model. So the effort isn't wasted, oh no! Far from it. But it's a help for someone who already has the make/model listed. It's not really helping someone deciding upon which make/model to buy. In the fast pace of computer technology, a setup like that is always behind on the facts.
--- Consider this ---
If you'll come with me to the corner electro store. This is where most people buy their hardware. As you can see, every electro store has the same brands, only slightly different models. What do we have?
Of course, two or three HP's to choose from. Also two or three Acers, three PB's, a Compac or two. Probably some home brand (cheap). And the mandatory Toshiba.
Now how do I know which one of these will work? I have a fair chance that all of them will work just fine. But, if I'll find out after installing Linux, that the Wireless/TV-tuner/Graphics/Whatever doesn't work, I cannot return the machine. I'm really disappointed and out of a lot of money. So I don't depend on my fair chance, instead I proceed with caution.
---/Consider this---
This situation is faced daily by a lot of people. And, as we are *nix people, we probably think these issues should not be faced by humans, but rather by an online engine of some sort.
I'm at high risk of exposing my limited knowledge on the subject here, but I think a database should be able to break down a make/model into it's components and view their 'support-status'.
A database (I'm typing faster as I'm pressed for time) can store an almost infinitely large number of components. When a new make/model gets feeded into the database, the database can reference this make/models components against what is already in it. If for example all the components have been proved to work, there is no need to actually test this new make/model.
For example: if we all know the new Toplap UberGamer 3000XX has the NviaVi 384993 card and the LinkRa 9090 wireless card, and we all know these components are well supported, then it's safe to say the new Toplap UberGamer 3000XX is supported.
A database like that can also deal with questions like: 'are all DVD-RW's supported?', for example, I have come to understand that each and every Bluetooth device works under Linux.
----
So, if you're still with me... I have two questions. First, is breaking down a make/model into it's components a safe approach to estimate the workability of a particular model under Linux?
And second, how will all this wisdom get feeded into a database?
(At first human effort I'm afraid, although with the manufacturers support this can be 99,9% automated in the end) Then we'll need a way to tell the manufacturer something to the extend of "If you want your new Ubergamer 3000XX in our database, you'll have to email us the specs in this-and-this format. Then the computer can handle the rest. And we have ourselves some innovation.
*Looks at the clock* Think about that. I'm off to work

Feedback and suggestions will receive a warm welcome
EDIT: Great initiative minthaka!