Update hardware recommendations to include qubes-certified list

[zenmonkeykstop]

Draft mode for now - it needs:

• up-to-date sections on FPF-tested laptops, basically the most modern 3 testing laptops in use across the dev team.
• A blurb about the Qubes HCL with pros and cons of it as a resource
• Validation that we're ok with this approach to recommendations.

Fixes #211

Updates hardware reccos:

• recommends qubes-certified, FPF-tested, and HCL options, in that order
• moves config instructions for Thinkpad BIOS updates out of hardware reccos page, to make the point of the page clearer.

[nathandyer]

Was the decision to remove the section on USB-C ports because this information is no longer applicable, or because it's too in-the-weeds?

[zenmonkeykstop]

Bit of both - it references 8th-gen T480s so n/a, and if it is caused by bios settings in install section it can probably be a note there.

[nathandyer]

For the sake of consistency, we should probably either have a small guide for Framework BIOS updates as well, or at least link out to their knowledgebase article on the topic: https://knowledgebase.frame.work/framework-laptop-bios-releases-S1dMQt6F

[nathandyer]

Er, that link was for the 11th gen Intel board specifically. Looks like each product has its own BIOS update page. We'd either need to point to https://knowledgebase.frame.work/categories/products_en-r1aUmxtrd, or consider linking to each individual page in the aforementioned small guide.

[zenmonkeykstop]

My pref would be to link wherever possible - if that's an option I'd link from the section in the hardware reccos. Where there's a long or involved process that we have to document locally, I'd prefer to have it in a separate page.

[nathandyer]

Thanks @zenmonkeykstop, even in early drafts this is looking really great. I think this is the correct approach, and I like the way you have explained everything. I left a couple small in-line comments just to jot down some thoughts.

I'm a bit iffy on whether or not it makes sense to include the note about Heads, but it is worthwhile for folks to know it's available, so it's probably reasonable to include it where you did.

Overall, I think this is a huge improvement! Would it be helpful if I tacked on a commit to fill some of the missing sections?

[zenmonkeykstop]

Thanks @zenmonkeykstop, even in early drafts this is looking really great. I think this is the correct approach, and I like the way you have explained everything. I left a couple small in-line comments just to jot down some thoughts.

I'm a bit iffy on whether or not it makes sense to include the note about Heads, but it is worthwhile for folks to know it's available, so it's probably reasonable to include it where you did.

Yup that part in particular is worth debating. IMO it's worth mentioning because certified machines often have it as an option, but we could go either way.

Overall, I think this is a huge improvement! Would it be helpful if I tacked on a commit to fill some of the missing sections?

But of course!

[nathandyer]

Thanks again! I just tacked on a commit which expands the Framework 13 section with a short explanation, and links out to the BIOS upgrade guide for the 13-gen CPUs. It also describes the Qubes HCL, and lists some of the benefits and downsides. I'm sure there are some that I missed, so we can add/remove to those as we see fit.

I also added a tiny commit that we can remove if we want to drop it, which just takes out the AMD processor recommendation since I know there has been some iffyness in how well they work in Qubes.

I left the X1 and T14 sections as-is for now; I think they're roughly still in an OK position, but we can tweak those as needed.

[eloquence]

Draft looks good from my POV, left a couple comments.

[nathandyer]

@zenmonkeykstop This can probably be flipped out of draft mode now, unless there are any other preliminary items you think we need to address first.

[deeplow]

Took a look to the recent changes and the PR overall. The recommendations look sensible and I like the wording.

I have one suggestion, though. Historically there have been no links to the hardware products, it seems. However, for frameworks, since it's a lesser known brand and has a non-standard domain (frame[.]work) shall we add a no-referrer link at the very least tot he home page? (if that's a possibility with Read The Docs)

[nathandyer]

@deeplow It's definitely possible to add a link like that with Sphinx/RST/RTD. Historically I believe we have intentionally avoided doing so, as to not recommend a particular source for purchase in hopes of diversifying where orgs are getting their hardware. It might be good to continue that precedent here (Frameworks are available directly from the manufacturer, but if there are any resellers or other vendors, it may be good for said diversity). But I have no strong feelings, and am happy to go whichever direction the team prefers.