Still unsure why this is fundamentally an issue to help the user to quickly find the wiki, that is just another official source of informationā¦ but anyway.
Sure, git is theoretically great, and fits nicely with content that must be carefully checked like code. But it is, in my experience, way too slow for anything where many minor changes are made like in a documentation (at least given the man (and woman 
) power of NixOs). For instance, I once sent a ~3 line PR to simply document the <nixpkgs> syntax nixos/doc: documentation angle bracket syntax by tobiasBora Ā· Pull Request #63033 Ā· NixOS/nixpkgs Ā· GitHub and that was quite a journey. First just to send the changes, you need to understand the heavy xml syntax and compile some stuff (that must be part of the PR, which makes it horrible to review). Then, you need to know git & PR, then you need to wait for review: the first review I got was 4 months later! (Not blaming anyone but the process) And of course, as Nix reviewers care a lot about details (a bit too much I think but itās another topic), they say āLGTM, but can you change this minor detailā. This adds another round of getting again used to the compilation process (I slept a few night in 4 monthsā¦ and my focus had changed as well) and waiting for reviews, that will again pin minor detailsā¦ and it creates so much time, efforts, and frustrations for so few changesā¦ and at the end the PR never got merged as someone else fixed it elsewhere. At least in wiki we donāt have this barrier as anyone can fix the details straight when they see them (often it takes more time to ask someone to apply the fix that fixing it directly), and I think itās fair to give it a chance 