I think something along this lines would be nice.

Maybe even "The whole Nix Manual", ... ?

My point would be: When I look for documentation for a project I really want to understand what documents there are. Is it one wiki? one userguide and one reference? A loose collection of blog posts? Not knowing the overarching simple structure decreases discoverability and faith in finding information a lot.

So in this case we should really communicate "For the main docs there are exactly three manuals and those useful links we have collected for you all point to one of them.“

The links are great, but I would really love something to make clear that there are this three documents.

Maybe a small subtitle under the headding:

“Learn Nix
from the Nix manual"

where "Nix manual" is a link?

Maybe a small subtitle under the heading:

Personally, I mostly think of the manuals as reference manuals: great to look things up when you already know your way around the system, but a bit daunting if you're just getting started.

From that perspective I like having the links to more 'tutorial-like' resources first, and the manual as a (prominent) button at the bottom of each column. (I didn't notice those are links to the manual :D )

@raboof @maralorn Thank you for looking into this. I think you are right that there should be the manual in the name, but I would change the title - eg. Learn Nix -> Nix manual - and only change the bottom button from "More..." to "Read more...".

In general the Learn section of the page is going to receive a lot of changes, especially once the format for documentation is settled (RFC #72). But I agree that what you propose would help until then.

I would change the title - eg. Learn Nix -> Nix manual - and only change the bottom button from "More..." to "Read more..."

I suspect that would be confusing: that gives the impression that that section is the manual, rather than just linking to it...

@raboof I added the changes to this PR, I think it makes it makes it even more obvious now.

Great!

I hope that at the end of the whole process we have a solution for the very unfortunate situation that two of the links in the former "Learn nix" section actually point to the nixpkgs manual.