this looks like a large change, but it simplifies a few things:
- separate page for documentation resources, with overall less text
- updated information on the official NixOS Wiki
- communication channels are now subsumed under "how to get help"
- a few wording corrections while at it
* docs: improve shell command copy experience
Prevent the inclusion of the dollar sign and preceding characters when copying shell commands from the documentation
Co-authored-by: Silvan Mosberger <github@infinisil.com>
The statistic in
https://discourse.nixos.org/t/nix-community-survey-2023-results/33124
does also include N/A responses in the percentage, so the 58% is a bit
misleading as the conclusion would be that 42% are still not using
flakes. I dropped the 1/3 statement for now, because I couldn't find any
information about that, but I can re-add it if this percentage is
actually correct. I also dropped the 2022 results as it didn't seem to
have the explicit question in it.
- Use separate JSON files to track sources for Nixpkgs and Nix releases
This greatly simplifies the code, because we can directly encode
versions as keys without ambiguity
- Avoid an instance of IFD for the redirect generation
- Use pkgs.substitute instead of builtins.replaceStrings
- Turn off the single-page feature for now. It was added by Valentin in
a previous commit, but I think we should discuss this a bit more
- Simplify a lot of the code and add comments
- Fix the mutable redirects, they were broken by a parent commit
- Remove pieces of Nix code that weren't used, like the import of the
Nixpkgs manual. This can be added in the future when necessary
- Make sure that Nix versions are cached by building from the store path
this will accumulate releases over time. it's not great, but this is the
price of persistent URLs. otherwise, when people link to supposedly stable
URLs, and we garbage-collect old manuals, those links will rot away.
it's also slightly simpler algorithmically, and therefore easier to
reason about.
this can be incrementally improved in the future, by automatically
adding redirects to e.g. the closest following release for which the
manual is still served. for example, if we currently serve
23.11
23.05
22.11
22.05
but in the future decide to cut that list to the first two, the script
would drop the excess pins and add redirects like these:
/manual/nixpkgs/22.05/* /manual/nixpkgs/23.05/:splat 301
/manual/nixpkgs/22.11/* /manual/nixpkgs/23.05/:splat 301
the condition for that would be that we are reasonably sure that the
manuals will manage their own internal redirects as pages and anchors
move around between releases.
