That GitHub HTML-bundle pain is real, especially when whatever exported the pages dragged in half the surrounding site CSS and sidebar widgets along with the article. You spent the time writing the originals; the file-wrangling shouldn't be what costs you another evening.
If it's useful, I'm up for taking the cleanup off your hands. Concretely:
pull the HTML you saved from the repo (or a zip / branch you point me at)
strip out the noise: scripts, sidebars, navigation, anything that isn't the article body and its images
convert to markdown, one file per article, images kept alongside
open a PR against tobiaskreidl/Citrix-Tobias-Kreidl-Collection (https://github.com/tobiaskreidl/Citrix-Tobias-Kreidl-Collection) so you stay the owner and only have to review and merge
If the saved bundles are too far gone, I'd fall back to the Citrix URLs @john.c surfaced and pull clean copies via the Wayback Machine. Same end result on your repo.
Separately, and only if that lands cleanly, I'd love to talk to Thomas Moraine and the docs team at Vates about whether parts of this could find a home on docs.xcp-ng.org, linked back to your repo with full credit. The NUMA-affinity page I pointed at earlier is shallow next to what you wrote, and the BIOS / GPU-scheduler material has no current equivalent at all. Whether the 2019 specifics still map cleanly onto current XCP-ng versions and hardware is a separate conversation; even as an archived reference, it's more than what's there today.
No pressure, no obligation. If you'd rather keep iterating on the repo yourself, that's fine too. But if a clean-the-HTML-and-PR-it pass would save you a week of GitHub-tool frustration, I'm genuinely up for it. Just point me at the bundle.
