Documentation team

Nix rewards those who already know it. We're changing that.
Finding answers in Nix often means reading source code, asking the right person, or stumbling across a forum post from three years ago. Your donation funds the tooling, review processes, and standards that make that unnecessary.

Read the detailed vision

Budget for paid documentation housekeeping.

- Write new content
 - Test & keep existing content up-to-date
- Handle day to day documentation tasks, review PRs, collect frequently asked questions and turn them into content.
 

Before committing to a rendering approach, we need to choose a path and validate it. The two candidate strategies are:

Hybrid: render ~5k pages statically, with the remaining 150k+ records produced via server-side generation (on demand).
Fully static: render all 155k+ pages statically.

The evaluation will compare these against build time, dev-cycle time, and the docs-writing experience (DX).
This goal comes first because its outcome determines everything else: whether it's worth extending the existing Sphinx setup, or whether nix.dev needs a different rendering framework altogether.

See Documentation-page-count-estimate

nixos-render-docs (nrd) will be extended so that the nix.dev tooling can consume sources directly. This is what brings the existing manual content (Nix, Nixpkgs, NixOS) onto the new portal at https://docs.nixos.org as first-class pages. 

We build up the new portal in parallel while keeping the current manuals and bring it to content parity with what's served today. 

Note: Redirects from the old URLs come deliberately last (as go-live). We prepare everything we can in the earlier goals.

Improve the infrastructure so that documentation changes deploy automatically: every documentation-changing PR gains a preview, and the master branch and PRs deploy without manual intervention.

Problem today: every deployment is blocked by three gates, the channel must pick up the change, the channel itself must be non-broken, and a flake-input bump PR must land in the separate nixos-homepage repository

Once docs.nixos.org is serving stable URLs visitors to old URLs should be redirected to their new equivalents. For example:

https://nixos.org/manual/nixpkgs/stable/#part-builders → https://docs.nixos.org/nixpkgs/stable/build-helpers