Valentin Gagarin

another argument for having a Nix-package-manager-specific web site is to manage the web rendering of Nix manuals in the [Nix repo](https://github.com/NixOS/nix). Right now the [path-level redirects are on `nixos-homepage`](https://github.com/NixOS/nixos-homepage/blob/8e6a0d831113bfd7f1c36788eae871201d09fc18/netlify.toml#L109-L149) while...

@edolstra this is for the board to answer, could you please transfer it to NixOS/nixos-foundation?

We could even consider [renaming the GitHub organization](https://docs.github.com/en/organizations/managing-organization-settings/renaming-an-organization) to _Nix_ to match the [hopefully-soon-to-be authoritative terminology](https://github.com/NixOS/nix.dev/pull/263) and better support the (technically and morally correct) narrative that Nix is at the...

Yes, there should absolutely be an overview on all supported languages. The `nixpkgs` manual has a fair amount of information, but only for supported builders.

Is it about the `/latest` part? Where do you find such links?

> Why do you think we should remove glossary? Because it only contains TODOs. You said you would prefer not to present skeletons, and I agree in part: have a...

> where questions regarding content organization can be asked It's a good question, and we should answer it prominently in multiple locations: - on NixOS Wiki itself - in this...

@mightyiam I think this should be a straightforward first step to continue with the markdown migration.

Is there anything speaking against using any strict subset of markdown that is already in Nixpkgs? As long as there are no diverging features, people can use common things such...

> Could it be possible to add details about type casting? Out of scope for this one, it's just a migration from NixOS manual, with basic fixups and additions.