In reply to @johannes.kirschbauer:scs.ems.host
Maybe we can raise a pot of Money for all the Framework and infra refactoring Tasks.

Yes, we can put up a funding goal on https://opencollective.com/nixos/projects/nix-documentation

Just need to define concrete, achievable deliverables.

It seems that I need to study the documentation more before, I can contribute.

I will donate to the Nix Documentation team as a first step.

Also, I have been reading through the dev.nix and of the parts that I have read I think does a really good job!

I may have visited nix.dev before, if I had it was not clear to me that nix.dev serves as an entrypoint for all the other documentation sources.

Also, the fact that when you go to nixos.org and from the main page are not 100% certain where the main documentation site is, seems to me a pressing point (what do you guys think?). Ideally we should be directing as much trafic through nix.dev as possible when people are looking for documentation?ronef

In reply to @ronef:matrix.org
Hey, every NixCon I do a collaborative "State of the Union" where folks from various efforts/teams come share a slide for two minutes and a call to action. Thought to check if someone from the docs team might be interested and is coming to NixCon!

In reply to @brunbjerg:matrix.org
It seems that I need to study the documentation more before, I can contribute.
I will donate to the Nix Documentation team as a first step.
Also, I have been reading through the dev.nix and of the parts that I have read I think does a really good job!
I may have visited nix.dev before, if I had it was not clear to me that nix.dev serves as an entrypoint for all the other documentation sources.
Also, the fact that when you go to nixos.org and from the main page are not 100% certain where the main documentation site is, seems to me a pressing point (what do you guys think?). Ideally we should be directing as much trafic through nix.dev as possible when people are looking for documentation?

Thanks a lot for the financial support!!

And adding clearer pointers to documentation from nixos.org would certainly help

In reply to @ronef:matrix.org
Johannes Kirschbauer @hsjobeki: see if there's anything you'd want to add here about it
Are you going to be around at NixCon?
https://docs.google.com/presentation/d/1G9Rc6cxWKgMM1q0DtgwyWUauBZ0vBLhAiV3M5ZuvEyo/edit#slide=id.g23efee59dda_0_212

In reply to @johannes.kirschbauer:scs.ems.host
@fricklerhandwerk:matrix.org: do we want to add nix-documentation team Slide? There was quite some stuff Happening this year. Stuff for reference documentation - Jan noogle 2024 released - doc-comments now implemented in nix-repl (roberth ported from lix i think) - Infra / Domain Changed (you did this i think with roberth) - multi Version nix Manual - nix.dev (i dont know what Majors happened there) ... Maybe we should sit down and Filter Out the important stuff?

Just a quick question about the lib type signatures - is it an active decision we have made not to note subtypes for attrsets? Or has it just become this way?

# Current state for lists
map :: (a -> b) -> [a] -> [b]

# Current state for attrs
mapAttrs :: (String -> Any -> Any) -> AttrSet -> AttrSet

# I'd like something like this
mapAttrs :: (String -> a -> b) -> { * :: a } -> { * :: b }

# Or alternatively just
mapAttrs :: (String -> a -> b) -> { a } -> { b }