I'd also say that a condition to split anything into multiple pages is that

• There will still be a single-page rendering as an alternative
• All anchors are redirected at the client

We can't do better than partially relying on client-side redirects, but it works okay for the Nix manual. In fact, I'm not even sure why it even works, but an anchor like in https://nixos.org/manual/nix#chap-tuning-cores-and-jobs will correctly propagate from the server-side redirect to https://nixos.org/manual/nix/stable/ to the client-side redirect script.

Changing where the manuals are hosted should therefore not be an issue if done carefully.

In reply to @johannes.kirschbauer:scs.ems.host
In my opinion, the root of our current issues stems from the overuse of anchor tags. This overreliance has led to regressions and breakages that we're now struggling to address. The longer we delay taking action, the more severe and complex these problems become, exacerbating the situation further.

In reply to @johannes.kirschbauer:scs.ems.host
Yes we could build a client side redirect. This would solve the migration issue. But this means the client side redirect handler has to be installed into the potentially new root page of manual/nixpkgs/stable/

In reply to @efx:matrix.org
I'd like to improve the documentation for buildNpmPackage. To me, this is the story of how do you package node.js applications or libraries in nix. I'm running into a number of pitfalls and would like to have the languages section note these.
Before I go submitting changes, are there maintainers I should check in with? Or a particular guide to follow?

In reply to @efx:matrix.org
I just created a GitHub account and seem to be unable to fork NixOS/nixpkgs. I'll work on the patch separately and may need some assistance getting the bytes into NixOS/nixpkgs.